Privacy Policy

What we collect today

Right now, this marketing site collects one thing: the email address you give us to join the early-access list. Nothing else is gathered here — no analytics, no tracking cookies, no third-party ad pixels. Your browser stores your light/dark theme preference locally (local storage, not a cookie); it never leaves your device.

What the app collects, once you're in

This section describes the product Tempio is building, so you know what to expect before you're using it. When your account opens:

• Account & workspace data — your name, email, and authentication details; the organization (workspace) you belong to and your role in it.
• Ad platform connections — when you connect Meta, Google Ads or TikTok, we store the access credentials for that connection securely and use them only to read and, on your approval, write to your ad accounts. We never see or store your platform password.
• Ad account data — campaigns, ad groups, ads and performance metrics (spend, impressions, clicks, conversions) synced from the accounts you connect, so the dashboard can show them blended and normalized.
• Drafts and the ledger — every proposed change (from you, your team, or an agent) and its approval history: who asked, what changed, when it applied.
• Agent and MCP activity — chat messages you exchange with the built-in agent, and metadata for any MCP keys you issue to connect your own AI tools (the key itself is stored as a hash, never in plain text — we can't recover it, and neither can anyone else).

We don't store or fabricate numbers we don't have — a metric with no data behind it is shown as absent, not invented.

Connected ad platforms

Each platform grants Tempio access through its own sign-in: Google's OAuth consent screen, Facebook Login for Business, or TikTok for Business. You pick the accounts to share on that screen. Tempio asks for read access to those accounts and, for the changes you approve later, write access to the same accounts and nothing wider.

• Google Ads — with the Google Ads API scope, we read the structure of the accounts you chose (campaigns, ad groups, ads) and their daily performance reports (spend, impressions, clicks, conversions). Tempio's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
• Meta — through Facebook Login for Business, we read the ad accounts you share from your business portfolio (campaigns, ad sets, ads and their performance, including reach), the list of your Pages so you can choose the one your ads run from, and that Page's name.
• TikTok — through TikTok for Business, we read the advertiser accounts you authorise (campaigns, ad groups, ads and their performance reports).

We use this data for one purpose: showing you your own accounts, and applying the changes you approve to those same accounts. We don't combine it across customers, use it for Tempio's own advertising, or sell it. It reaches nobody except the processors listed below, and only to run the service.

The access token a platform issues is encrypted before it is stored and decrypted only to call that platform for you. Synced campaigns and metrics stay in our database while the connection is active.

To withdraw access, remove Tempio from the platform's own settings (Google Account → Security → Third-party apps; Meta → Business settings → Integrations → Business apps, or the app list in your Facebook settings; your TikTok for Business settings). Syncing stops as soon as the platform tells us the access is gone. If you also ask Meta to delete your data, Meta sends us a deletion request: we destroy the stored credentials for that account and give you a confirmation code and a status page showing the result. To have synced campaign and metric data deleted on any platform, email hello@tempio.ai.

Who we share it with

We don't sell your data. A small set of processors handle infrastructure on our behalf, each scoped to what they need to do their job:

• Vercel — hosting, and the AI Gateway that routes model calls (see below).
• Resend — transactional email: waitlist confirmations, and, once the app is live, account and notification email.
• Supabase — our Postgres database, where account, workspace and ads-domain data is stored.
• Upstash — rate limiting and caching infrastructure.
• AI providers, via Vercel AI Gateway — when you use the built-in agent, your prompts and the relevant account context are routed through Vercel's AI Gateway to a frontier model provider to generate a response or draft. We don't hold direct API keys to those providers; the Gateway brokers the call.

If you connect your own AI tool (Claude, ChatGPT, Cursor, or anything else that speaks MCP) using a scoped key, that tool becomes its own data controller for whatever you choose to send it — Tempio's role there is limited to what the key is scoped to read or draft.

How long we keep it

Waitlist emails are kept until early access opens for you or you ask to be removed, whichever comes first. Once you have an account, your data is kept for as long as your workspace is active; if you close your account, we delete what we can and retain only what we're required to for legal, security or fraud purposes.

Your choices

Ask to see, correct, export or delete your data, or to come off the waitlist, any time — email hello@tempio.ai and we'll handle it by hand while the product is in early access.

Legal entity

Tempio is operated by Tempio AI Pty Ltd, an Australian proprietary company — ACN 664 611 125, ABN 68 664 611 125.

Contact

Questions about this policy or your data: hello@tempio.ai.