Privacy Policy

1. Who is responsible

TerraGPT is the data controller for the personal data described in this policy. For any privacy question or request, contact [email protected]. That inbox reaches the people who can actually act on it.

2. What we collect

• Account data. When you sign in with an identity provider we receive a stable account identifier and, where you permit it, your email address. We do not receive your password.
• Conversations and content. The messages you send, the responses generated for you, files and images you upload, documents generated for you, memories the assistant keeps at your direction, and conversations you explicitly share.
• Subscription data. Your plan, trial and renewal state, and, for web purchases, billing metadata handled by our payment processor. We never see or store full card numbers.
• Device and technical data. Device and browser type, operating system, app version, language, time zone, IP address, and crash or error diagnostics.
• Usage analytics. Which screens and features are used, when, and roughly from where (a coarse location derived from your IP address: country or city level, never precise GPS). Analytics events are collected first-party.
• Voice data. When you use dictation, read-aloud, or a voice conversation, the audio you record and the text being read are sent to our speech provider to be transcribed or spoken. We do not keep recordings of your microphone audio.
• Support correspondence. Emails you send to [email protected].
• Newsletter data. Your email address and subscription state, if you choose to subscribe. Creating an account does not subscribe you.

3. Why we use it

• To provide the Service: generating responses, keeping your history in sync across devices, honouring your settings and memories, counting messages toward tree milestones. (Performance of our contract with you.)
• To process payments and manage subscriptions. (Performance of contract; legal obligations.)
• To keep the Service safe: preventing abuse, enforcing rate limits, detecting fraud, securing accounts. (Legitimate interest in a secure service.)
• To improve the Service: first-party analytics about how features are used, aggregated and reviewed at feature level, not to build advertising profiles. (Legitimate interest; consent where required.)
• To communicate with you: service messages about your account, and, if you subscribed, the newsletter (until you unsubscribe). (Contract; legitimate interest; consent where required.)
• To comply with law: responding to lawful requests and meeting accounting or tax obligations. (Legal obligation.)

We do not sell personal data, and we do not use your conversations for third-party advertising.

4. Who processes it for us

We share personal data only with service providers who process it on our instructions, under contracts that hold them to confidentiality and data-protection obligations. By category, they are:

• Trusted infrastructure and model providers: the computing platforms that host the Service and process conversation content to generate responses.
• Speech provider (ElevenLabs): receives the audio you record when you dictate or hold a voice conversation, and the message text you ask to have read aloud, in order to transcribe or speak it.
• Web search providers (Exa and Parallel): receive the search query derived from your message when an answer needs current information from the web. They receive the query, not your conversation.
• Identity providers: the sign-in services you choose to authenticate with.
• Payment processors: for web billing, and the app-store operator for in-app purchases; a subscription-management provider reconciles entitlement state across platforms.
• Analytics infrastructure: our first-party analytics pipeline.
• Email delivery providers: for service emails and the newsletter.
• Reforestation partners: they receive aggregate planting pledges only; they never receive your personal data.

Where a provider processes data outside the EU/EEA, we rely on appropriate safeguards such as adequacy decisions or standard contractual clauses.

5. How long we keep it

• Conversations, files, and memories: kept while your account exists so your history works; deleted when you delete them or your account.
• Shared conversation snapshots: a share link freezes a copy of the conversation at the moment you share it. Revoking the link deletes that copy and the images it published; only the fact that a link existed, and when, is kept.
• Read-aloud audio: spoken versions of message text are cached on our servers, addressed by a hash of the text, so the same passage is never re-synthesized and re-billed. The cache holds audio and no account identifier, and it is periodically cleared.
• Account data: kept while your account exists and deleted with it, except records we must keep longer by law.
• Billing records: kept for the period required by tax and accounting law.
• Analytics events: retained in identifiable form for up to 24 months, then deleted or aggregated.
• Security logs: typically retained for up to 12 months.

Deleting your account from settings removes your conversations, memories, files, and shared links from production systems promptly, with residual copies clearing from backups on their rotation schedule.

6. Your rights

If you are in the EU/EEA or UK (and in many other places), you have the right to access your personal data, correct it, delete it, obtain it in a portable form, restrict or object to certain processing, and withdraw consent at any time where processing is based on consent. You also have the right to lodge a complaint with your local supervisory authority.

The fastest path for most of these is built in: settings let you delete conversations, memories, shared links, or your entire account, and every newsletter email contains an unsubscribe link. Access and portability are built in too: “Download my data” under Data controls on the web, and under Privacy in the iOS app, gives you a JSON file with your profile, your conversations and their messages, your memories, your impact totals, and the names of the files you uploaded. If you would rather ask, or you need something the export does not cover, email [email protected] from the address linked to your account. Use the same address for anything else, and we will respond within the statutory deadline (one month, extendable where the law allows).

7. Cookies and local storage

We use a small set of first-party cookies and local-storage entries, all functional: keeping you signed in (an httpOnly session cookie), remembering your language and theme, remembering that you dismissed notices, and a random identifier for first-party analytics. We do not use third-party advertising cookies or cross-site trackers. Because everything is first-party and either strictly necessary or low-impact analytics, we show a brief notice rather than a blocking consent wall; you can clear cookies and local storage in your browser at any time.

8. Children

The Service is not directed to children under 13, and we do not knowingly collect personal data from them. If you believe a child under 13 has created an account, tell us at [email protected] and we will delete it.

9. Security

We protect personal data with encryption in transit, access controls, isolation between customers, rate limiting, and monitoring. No online service can promise perfect security, but we design for the assumption that security failures are expensive and privacy failures are unacceptable.

10. Changes to this policy

We may update this Privacy Policy at any time, without individual notice. The current version is always published here with its "Last updated" date, and material changes may additionally be announced in the Service. Your continued use of the Service after a change takes effect constitutes acceptance of the updated policy.

11. Contact

Privacy questions, requests, or concerns: [email protected]. We read everything.