Privacy

• Account: email address, name, identity-provider identifiers, avatar, authentication events, and account timestamps.
• Pending sign-up: before an account exists, the address a sign-up link was sent to, the destination page, and a one-way digest of the link. The link itself is never stored. If the sign-up is not completed, this record is all that exists and it expires.
• Request throttling: one-way digests of the address and of a keyed hash of the requesting IP address, with a timestamp, used to limit how often sign-up and reset emails can be requested. No address, IP address, name, or password is stored in readable form.
• Teams and rooms: membership, roles, invitations, objectives, messages, tasks, claims, approvals, agent state, activity, and room history.
• Repository: GitHub identity, App installation, selected repository names and identifiers, branches, commits, pull requests, file paths, diffs, terminal output, saved workspace checkpoints, shared repository instructions, and shared context attachments. For a repository file attached as context, Batawn stores its path, immutable Git blob identifier, size, and content hash. For a locally uploaded context file, Batawn stores the uploaded text. Batawn does not store a complete repository clone.
• Agent integration: machine and session identifiers, host type, integration version, supported controls, connection state, and tool events.
• Shared connections: when a team connects a third-party provider (Vercel, Supabase, GitHub, PostHog, Resend, or Stripe), the provider account’s name and identifier, the scopes granted, connection health, and the OAuth credentials Batawn uses to act as that account, which are stored encrypted. For each room, the actions, targets, and environments it allows and its approval mode. For each action an agent requests, who asked, which agent, the action, target, and environment, a copy of the arguments with sensitive values removed, the arguments themselves stored encrypted, the decision and who made it, the outcome, a size-limited copy of the provider’s result with sensitive values removed, any manual follow-up, and the history of the connection and the request.
• Billing: Stripe customer and subscription identifiers, plan status, seat count, invoice state, and trial dates. Stripe receives payment details; Batawn does not receive complete card numbers.
• Support and security: correspondence, support-access records, IP and request metadata in infrastructure logs, error diagnostics, and abuse or incident records.
• Optional analytics: page and product events, device and browser information, and masked session recordings after consent.

We receive information from you, your teammates, your browser and installed Batawn integration, GitHub, authentication providers, Stripe, third-party providers your team connects for shared connections, and the infrastructure that carries your requests. A teammate may add you to a team, invite you to a room, send you a message, or create content referring to you.

• Provide accounts, rooms, coordination, GitHub access, shared provider connections, support, and billing as necessary to perform our contract.
• Authenticate users, enforce permissions, prevent abuse, investigate errors, and protect the service based on contractual necessity and legitimate interests in security.
• Process payments, tax information, disputes, and lawful requests to meet contractual and legal obligations.
• Measure and improve the product using optional analytics only after consent where consent is required.
• Communicate service, security, billing, and policy notices as needed to perform the contract or meet legal obligations.

We do not make decisions that produce legal or similarly significant effects using automated processing.

We use the following providers for the stated purposes:

When a team connects a third-party provider for shared connections, Batawn sends that provider the actions the team’s rooms request, as the account the team connected and on the team’s instructions. Those providers are chosen by the team and handle that data under the team’s own terms with them, separately from Batawn’s own use of any of the same companies listed above.

We may disclose information when required by law, to protect people or the service, or as part of a merger, financing, acquisition, or sale, subject to appropriate confidentiality and notice where permitted. We do not sell personal information or share it for cross-context behavioural advertising.

Authentication and security storage are necessary to sign you in and protect the service. Vercel page analytics and PostHog product analytics and session recording are optional and do not start until you choose “Accept analytics.” Choosing “Reject” does not limit the service. You can reopen Analytics choices from the control shown at the bottom of the site. A recognised Global Privacy Control signal is treated as rejection of optional analytics.

Batawn does not respond separately to legacy Do Not Track signals, which do not express one consistent choice. It does honour the choices described above.

• Account and team information remains while the account or team exists.
• Sign-up links expire one hour after they are sent, and the pending sign-up record is deleted seven days after that. Throttling records are deleted two hours after they are written.
• Resend holds delivery metadata for the emails Batawn sends — the recipient address, the subject, and the delivery status — under its own retention period.
• Room history and checkpoints remain while the room exists. Closing removes other participants but preserves the record for its owner.
• Repository instructions and repository-level context attachments remain available to rooms on the same team and repository until a member removes them or the team is deleted. Task context attachments are preserved with the task, become read-only when work starts, and remain with completed task history.
• A shared connection’s stored credentials are deleted when the connection is disconnected or the team is deleted. The history of the actions requested through it — decisions, outcomes, results with sensitive values removed, and follow-ups — remains with the room while the room exists.
• Deleting a team removes its rooms, membership, repository credentials, invitations, and Customer Content. A minimal deletion record remains to prevent slug reuse and document the deletion.
• Authentication, billing, tax, fraud, support, and legal records remain as long as reasonably necessary for security, accounting, disputes, and law.
• Provider logs, backups, analytics, and diagnostics remain under the provider retention periods we configure or that apply to the service plan, then expire or are overwritten.

Room deletion and full account deletion are support requests today. Email support@batawn.com from the account address. We may verify your identity and authority over affected teams before deleting information.

Batawn uses access controls, row-level database policies, encrypted transport, short-lived GitHub credentials, encrypted third-party provider credentials, restricted service roles, masked analytics, scrubbed error reporting, and recorded support access. More detail, including current limitations, appears on the Security page. No system can guarantee absolute security.

Batawn is operated in the United States and uses providers that may process information in the United States and other countries. Where required, transfers use recognised safeguards such as adequacy decisions, the European Commission’s Standard Contractual Clauses, and the UK transfer addendum. The DPA describes the customer-data transfer terms.

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or obtain a copy of personal information, withdraw consent, and appeal a refused request. Email support@batawn.com. We will verify the request and respond within the period required by applicable law. You may also complain to your local data-protection authority.

California residents may request the categories, sources, purposes, recipients, and specific pieces of personal information covered by applicable law. Batawn does not discriminate for exercising privacy rights and does not sell or share personal information as those terms are defined by California law.

Batawn is a business collaboration service and is not directed to children under 13. We do not knowingly collect personal information from a child under 13. Contact us if you believe such information was submitted so we can investigate and delete it.

We will post policy changes with a new version and effective date. A material change may require renewed acknowledgement before protected use. Questions and requests go to support@batawn.com.

Aditya Tickoo, operating as Batawn in San Jose, California, United States, is the controller of account, billing, support, security, and website information described here. Amrit Tickoo acts as Aditya’s legal guardian and adult representative. Contact support@batawn.com for privacy questions or requests.

When a customer submits personal data contained in repositories, prompts, room messages, or other Customer Content, the customer normally determines why that data is processed and Batawn acts as its processor. The Data Processing Addendum governs that processing.