Client API Keys — Applanta

⚠️

Never ask a client to text or email a secret key. Use team member access or restricted keys. Publishable keys are safe to share any way — secret/restricted keys are not.

Payment Platform

💳

Stripe

stripe.com · Payments & Checkout

›

Required for any app with a cart, food ordering, service deposits, or subscription billing. Covers full account setup, team member access (safest — no sensitive financial data shared), restricted key creation, and how to apply both keys to the app.

Shareable with client Client creates account You apply the keys

Location & Maps

📍

Google Places API

Google Cloud Console · Address Autocomplete & Maps

›

Required for apps with address search, location autocomplete, or Google Maps integration. You create this key yourself under applanta.dev@gmail.com — no client involvement needed. $200/mo free credit covers all standard usage.

Internal — you handle this Free tier sufficient

Infrastructure — Premium Clients Only

🔥

Firebase

Google Firebase · Push Notifications, Realtime DB, Auth

›

Required for Premium ($1,200+) apps that need push notifications, real-time database, or user authentication. Each client gets their own isolated Firebase project. Covers project creation, Blaze plan upgrade, VAPID key generation, service account setup, and wiring into the app.

Internal — you handle this Premium tier only

Security Rules

🔒

Secure Key Sharing Rules

How to receive keys from clients without risk

›

What methods are safe, what methods are not, and the exact steps to take after receiving any API key from a client.

Internal policy