Tarrasmart AI Code

Privacy Policy

Draft for review. Last updated 22 November 2026.

1. Who we are

Tarrasmart AI Code (the "app") is made by Tarrasmart (PT Tarrasmart Teknologi Indonesia, "we", "us"). We decide how the personal data described here is used: we are its controller. Contact: code@tarrasmart.com.

Tarrasmart AI Code has its own account system, servers, purchases and policies. It shares no data with Tarra, Agent+ or any other Tarrasmart app.

2. In short

3. What stays on your device

We do not receive this data. It stays in the app's private storage on your phone, or where you choose.

DataWhereWhen it leaves your phone
Projects and files, save pointsThe app's Linux workspaceOnly when you sync, deploy, back up, share or send it to an agent
Terminal and agent outputThe app's memory and session historyOnly over Link, end-to-end encrypted, to your devices and people you share with
Prompts, composer history, saved promptsOn your phoneWhen you send a prompt, to the agent you chose and its provider
Agent sign-ins (provider tokens, API keys typed into an agent)Inside each agent's own filesOnly from the agent to its provider. The app never reads, copies or backs them up
Project secrets, SSH keys, git and deploy tokensAn encrypted vault on your phoneSecrets: into the sessions you use them in, never into agent sessions when marked "Hide from agents"; tokens only to that git host or deploy target after your tap; inside a backup only if you protect it with a passphrase
Hosts and pinned host keys, device names, share and security logsOn your phoneInside a settings backup if you make one; logs are kept 90 days
BackupsWhere you choose (a folder, your own cloud drive)When you make one
Diagnostics report draftOn your phoneOnly when you send it

Uninstalling the app or clearing its data deletes this data, unless you keep app data when Android offers it. Keys in the vault cannot be recovered after a reinstall; keep a settings backup.

4. What our servers hold

Our servers run on our own Cloudflare account and our own Firebase project. They are control only: they help your devices find each other and confirm your plan.

DataWhyKept until
With an account: a random account ID, a one-way hash of your Firebase user ID (to find your account), your Firebase user ID sealed so only our server can open it (needed to delete your sign-in), the day the account was created and the day you were last seen (dates only, no time)To run your account, Link and sharesYou delete your account
With Link: random device IDs, each device's public keys and key signature, device kind (phone, tablet or computer) and client (app or connector), status, the Link protocol version, the dates the device was added and removed, the signed device list, push tokens with their refresh date. Device names are encrypted to your own devices; our server cannot read themTo connect your devices and wake themYour account is deleted; push tokens until replaced, revoked, or 270 days without a refresh; revoked devices stay as signed entries without content
With shares: share ID, the sharing account and device, the people who joined (their account and device IDs), role, state, creation and expiry times. Never project or session names, and never a joiner's name or emailTo let the people you choose joinDeleted when the share ends, is revoked or expires (an hourly clean-up removes expired ones)
Link signals: connection offers and network candidates, encrypted to the receiving deviceTo connect two devicesDeleted on delivery, at most 10 minutes
Relay data: encrypted frames when no direct path existsTo carry your connectionNever stored; minutes and bytes per account per day for fair-use limits, kept for that day plus one
Purchases: product, plan, trial or offer, state, period end, check times, the purchase token (sealed) and its hash, and the link to your account if you have one. With each purchase check your phone also sends a one-way hash of the app install, used only to limit how often one install can check. No order ID, price, country or Google account is storedTo confirm your plan, with or without an accountDeleted 30 days after the purchase ends (expired or refunded), so a late refund can still be matched
Founder counter: a hash of the purchase token, the time of sale, whether it was refunded. No accountTo count the limited Founder licences and honour themFor the life of the Founder offer and its licences
Account-deletion jobs: the hashed and sealed Firebase user ID, request time, attempt count, an error codeTo finish deleting your sign-inUntil your Firebase sign-in is deleted (retried every hour)
Usage totals: daily counts of requests, relay use, pairings, connection attempts and purchase checks, summed for everyone; no account, device or IP addressTo stay inside free hosting limits400 days
Milestones, only if you turn them on: a milestone name and the app versionTo count how many people finish setupDaily counts only (400 days); no identifier is sent

Sign-in. Google Firebase Authentication, which is Google's service and not our database, holds your Google name, email address and photo to sign you in. Our own database stores none of them and never writes them down; your session reads them from the sign-in token only while it runs.

Our servers never hold a field for your files, terminal text, prompts, keys, tokens, hosts, or project, session or file names. We publish the server code and schema so anyone can check.

Metadata we cannot avoid. To route a connection, our hosting provider sees your IP address. Our code stores no IP address and infers no location from it; Cloudflare keeps its own logs under its terms. Our servers know which devices belong to an account and when a device holds a connection, but keep no log of who connected to whom.

5. Data outside the app

DataWhyKept until
Emails you send to code@tarrasmart.com, and diagnostics reports you attachTo answer you90 days after your request is closed
Waitlist email and the optional answers you gave (phone model, memory, agents, country, testing interest), collected through a Google Form owned by Tarrasmart AI Code's own Google account. The form is on Google's servers; the answers never reach our app serversTo tell you about the launch and invite testersDeleted 30 days after launch, except for people who chose "keep me posted", whose entry stays until they unsubscribe

Diagnostics reports are built on your phone, shown to you in full, and sent only through your own email app. They hold device class, app and workspace versions, exit reasons and counts, and, only inside a report you send, crash traces of the app's own code from the last 7 days with their messages redacted. Crash traces stay on your phone until you send a report; no crash SDK collects them. A report holds no project content, terminal text, prompts or keys; identifiers are redacted. "Report AI output" in an agent's session menu writes an email the same way, with the excerpt you choose, through your own email app; nothing goes through our servers.

6. Who else sees data

UseBasis (GDPR / UU PDP)
Account, Link, shares, plan confirmationPerformance of a contract (GDPR Art. 6(1)(b); UU PDP Art. 20(2)(b))
Purchase recordsContract and legal obligation
Diagnostics you send, milestones you turn on, waitlistConsent, which you can withdraw at any time
Routing and abuse protection (IP addresses in transit, relay totals)Legitimate interests (GDPR Art. 6(1)(f); UU PDP Art. 20(2)(f))

8. Where data is processed

Cloudflare and Google run servers in many countries, so server data may be processed outside Indonesia and outside your country. We use the safeguards the law requires for such transfers.

9. Security

Every connection to our servers uses TLS. Link uses standard end-to-end encryption (WebRTC with a Noise session keyed by each device's own keys); the relay sees only ciphertext. Secrets on your phone are encrypted with keys held by Android's Keystore. We publish our threat model, Link protocol and a security self-assessment. No method is perfectly secure; if a breach affects you, we tell you and the authorities as the law requires.

10. Your rights

We follow Indonesia's Personal Data Protection Law (Law No. 27 of 2022, "UU PDP") and its implementing regulation (GR 33/2026, from 16 January 2027), and the EU General Data Protection Regulation (GDPR) where it applies. You may:

Account deletion is immediate. In one step it removes your account, device list and public keys, push tokens, shares (ended at once) and the link between your account and your plan, well inside UU PDP's 3 × 24 hours. Your Firebase sign-in is then deleted by an hourly job that retries until it succeeds, normally within the hour. A purchase row without an account stays until 30 days after the purchase ends. What stays: your projects and workspace on your devices (delete them in the app or by uninstalling), purchases held by Google Play (Pro bought through Play keeps working without an account), and backups you saved elsewhere. Copies in our hosting provider's short-term recovery storage age out on its schedule.

If you cannot sign in, email code@tarrasmart.com from your account's address. For other requests, write to the same address. We answer within the time the law sets (under UU PDP, generally 3 × 24 hours for many requests; under GDPR, one month).

11. Children

The app is for people aged 18 and over. We do not knowingly collect data from anyone under 18. If you believe a minor has given us data, contact us and we will delete it.

12. Changes

We update this policy before any new data is collected and show the date at the top. For important changes we also tell you in the app.

13. Contact

PT Tarrasmart Teknologi Indonesia
Menara UMI 4th Floor, Jl. Urip Sumoharjo KM. 5, Makassar, Sulawesi Selatan 90222, Indonesia
code@tarrasmart.com