Tanral.
Trust & transparency

Privacy Policy

Your work deserves a clear explanation of what happens to your data. This policy explains the information Tanral uses, why we use it, and the choices you have.

Effective November 9, 2026 · Last updated November 10, 2026

1. Who this policy covers

Tanral. ("we", "us" or "our") provides the website at tanral.com, the application at app.tanral.com, and related account, connected-agent, waitlist and support services. This policy applies to those services and other Tanral pages that link to it. Contact us about privacy at support@tanral.com.

Tanral helps developers follow work across supported AI coding agents. When you connect a supported agent, it can submit concise project activity and key progress for review in your dashboard and retrieve saved project context. Tanral is currently in development preview, with account registration and sign-in limited to invited users. Features described as planned are not enabled simply because they appear on our website. We will explain additional data practices before introducing features that require different data or permissions.

2. Information we collect

CategoryInformation and sourceWhy we use it
Account informationThe email address you enter, email verification status, account identifiers, authentication provider, account status, account creation and update times, and profile details you provide.Create and authenticate your account, maintain access, and associate your workspace with the correct account.
Google sign-inGoogle supplies your account identifier, email address and verification status, and, when available, your name, given and family names, locale and profile picture.Authenticate you, check preview access eligibility, initialise your profile, and display your name and avatar. See the dedicated Google section below.
Preview accessYour email address, an identifier derived from it, and masked email information used to manage invitations.Check whether an account is invited and manage access to the development preview.
Connected agents and clientsClient and installation identifiers, device display name, operating system and runtime information, agent and plugin versions, connection status and activity times submitted by the integration.Recognise authorised clients, maintain connections, display client information and diagnose compatibility or delivery issues.
Project activity and recordsCompact records submitted by a connected integration, which may include project names and identifiers, agent information, timestamps, task status, summaries, decisions, milestones and references to work products.Display your project activity and progress, preserve useful project records, and return saved context to your authorised connected agent when it requests it.
Waitlist informationYour email address, signup and update times, signup source, consent version and subscription status when you join the website waitlist.Send the launch updates you request and honour opt-out requests. Joining the waitlist does not create an application account.
Technical informationHosting, authentication and security providers process network and device information such as IP address, browser information, request times and security signals. The application may produce diagnostic and error records.Deliver pages, operate sign-in, protect against abuse and diagnose failures.
Support communicationsYour email address and messages or attachments you choose to send us.Respond to questions, troubleshoot issues and handle privacy requests.

The standard agent integration is designed to submit compact records rather than automatically upload complete conversations, source files or raw tool outputs. Submitted summaries and references may nevertheless contain information from your work. Do not include passwords, API keys or other secrets.

You can edit your Tanral display name and upload or remove a profile avatar. Uploaded avatars must be JPEG, PNG or WebP images up to 2 MB. We resize them, remove image metadata and store a processed image for profile display. Avatars are not published as public static files. The current preview has no payment collection, general-purpose file upload or meeting-recording feature.

3. Google sign-in and Google user data

Google sign-in requests only the basic OpenID Connect permissions: openid, email and profile. Depending on the information Google provides, we receive your Google account identifier, email address and verification status, name, given and family names, profile picture and locale.

We use this information to create or authenticate your account, check preview access eligibility, associate your workspace with the correct account, and display your profile. We do not request access to Gmail messages, Google Drive files, Calendar events or contacts, and we do not receive your Google password.

Google sign-in is processed through Amazon Cognito, our authentication provider. We store the account and profile information needed for these purposes, including a processed copy of an available profile picture. Our authentication provider may retain the mapped profile attributes, including the original picture URL. You can change your display name or upload or remove your avatar in Tanral. These choices take priority over later Google sign-ins and do not change your Google account. An unavailable picture does not prevent sign-in. We do not automatically merge separate accounts solely because they share an email address.

We do not sell Google user data, use it for advertising, or use or share it to train, fine-tune or evaluate AI models or generate images or videos. Access is limited to the service providers and authorised personnel who need it to operate authentication, provide support, protect the service, or meet legal obligations. Tanral's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements where applicable.

You can remove Tanral's access in your Google Account connections. Removing that access does not itself delete information already stored by Tanral. To request account deletion, contact support@tanral.com. Google's own processing is described in its Privacy Policy.

4. How and why we use information

We use information to provide the features you request, authenticate accounts, display account activity, respond to support requests, maintain reliability and security, investigate misuse, and comply with applicable legal obligations. Waitlist updates are separate from essential account messages and are sent based on your signup choice.

Where a law requires a legal basis, we rely on the basis appropriate to the activity: performing a contract or taking requested steps before a contract for account services; legitimate interests in operating, securing and supporting the service where those interests are not overridden by your rights; consent where required, including optional launch updates; and legal obligations where applicable. You can withdraw consent without affecting processing that was lawful before withdrawal. We do not make decisions with legal or similarly significant effects about you solely through automated processing.

5. AI and connected agents

Your connected coding agent may prepare records using the model service configured in your agent environment. When that agent requests project context, Tanral returns relevant saved records, which may become part of the agent's model context. Processing by that model service is governed by your configuration and the provider's applicable policies.

Tanral receives the records submitted by the integration and does not currently operate a separate cloud summarization model for these records. We do not use Google sign-in data to train, fine-tune or evaluate AI models, or to generate images or videos. Tanral does not provide AI image or video generation.

Connecting an agent does not grant blanket permission to access unrelated accounts, send messages or take other actions on your behalf. If we introduce additional AI processing, integrations or actions, we will describe the data involved, relevant providers, permissions and controls before you enable those features.

6. When information is shared

We do not sell personal information, rent mailing lists, or share personal information for cross-context behavioural advertising. We disclose information only as needed for the purposes described in this policy:

  • Service providers. AWS processes information needed for authentication, application hosting, storage, API operations, logging and email delivery. Google processes Google sign-in. Cloudflare provides website delivery, DNS and related website security and email services. Information is disclosed to these providers only as needed for their functions and the purposes described here. They may also process information under their own applicable policies.
  • Your connected agents. When an authorised agent requests project context, we return relevant saved records to that agent. The records may be processed by the model service you configure, as explained in the AI and connected agents section.
  • Support and administration. Access by support and administrative personnel is limited to what is needed to operate, secure and support the service.
  • Your instructions. We may disclose information when you specifically ask us to do so.
  • Legal and safety needs. We may disclose information when required by law, in response to valid legal process, or when reasonably necessary to protect rights, safety or service integrity.
  • Business changes. If the service is transferred as part of a merger, acquisition or similar transaction, relevant information may transfer subject to applicable law and appropriate notice.

We do not sell Google user data or use it for advertising. Provider policies: AWS, Cloudflare and Google.

7. Storage, retention and security

Core account and application records are currently processed and stored on AWS in the United States, primarily Ohio. Website delivery and service providers may process network or support information in other locations. We do not promise that all data stays in your country. Where legally required, international transfers must have an applicable transfer mechanism or safeguard; we do not treat use of the website alone as a substitute for those requirements.

We retain account and profile information for as long as reasonably needed to provide your account and meet applicable security, support and legal requirements. Project records, operational events and diagnostic logs may have different retention periods. There is currently no automatic account-expiry or inactivity-deletion schedule. Waitlist information is retained to manage your requested updates and subscription status; a minimal suppression record may be retained to prevent resubscription after you opt out. Support correspondence is retained only as reasonably needed to resolve and document the issue and meet legal obligations.

Current product application diagnostic logs have a 14-day retention setting; the separate waitlist application logs have a 7-day setting. Infrastructure providers may have different operational or security retention periods. Backup copies and records subject to applicable legal or security retention requirements may remain for their relevant retention periods after active records are deleted. They are not kept for unrelated use. Contact us if you need information about retention for a particular record.

We use encrypted connections, access restrictions and managed infrastructure security controls to protect information, including Google user data. No internet service or storage system can be guaranteed completely secure. If you suspect unauthorised access, contact us promptly.

8. Cookies, storage and security checks

The current Tanral website and application do not use advertising trackers or third-party audience analytics. Essential authentication and security features may use cookies or browser storage. The application uses the authentication SDK's local browser storage to retain session tokens and restore your session across reloads and tabs on the same application origin. The SDK can renew expired access tokens while a valid refresh token remains available. Signing out clears the application's stored session. Temporary sign-in state is used to complete a redirect. A Google or authentication-provider session may continue separately.

If you manually choose a Dashboard language, we also save that language code in local storage on this browser so your choice is remembered. The preference is not sent to our servers. Choose Auto to remove the saved preference and follow your browser language again. If browser storage is unavailable, switching still works for the current page.

The website waitlist uses Cloudflare Turnstile to distinguish legitimate submissions from abuse. Turnstile processes device and network signals for that security purpose. Google and other providers may set their own cookies when you use their pages. You can control cookies in your browser, though blocking essential storage may prevent sign-in or security checks from working.

9. Your choices and privacy requests

You can request access, correction, a copy of your records or deletion by contacting support@tanral.com. You can also request removal from the website waitlist or stop launch updates. We may verify your identity before acting on a request; do not send your password or verification codes. There is no self-service account deletion screen in the current preview.

Removing Tanral's access from your Google Account prevents further authorised access through that connection, but does not itself delete information already stored by Tanral. Signing out, revoking a client connection and requesting account deletion are separate actions. Tell us which records or services your request concerns; account deletion and waitlist opt-out are also separate.

Depending on applicable law, you may have rights to restrict processing, object to particular uses, receive portable data, withdraw consent, appeal a decision about a rights request, or complain to a relevant data protection authority. We will respond within the period required by applicable law and explain any lawful limits or information we must retain. We do not retaliate against you for exercising applicable privacy rights.

10. Children

Tanral is intended for adults aged 18 or older and is not directed to children. We do not knowingly collect children’s personal information. If you believe a child has provided information, contact us so we can investigate and address it.

11. Updates and contact

We will update this page when our practices change and show the new effective date. For material changes, we will provide an additional notice through the application, email or another appropriate channel where required. New optional processing will require any consent or authorisation that applicable law requires.

Questions about this policy or your information? Contact Tanral at support@tanral.com.