Privacy

Information used

Baatchit uses your verified account identity and email for sign-in and invitation matching, your chosen display name, and your workspace and project memberships. It stores the work, updates, decisions, documents, links, comments, spending and payment details you or authorized collaborators enter, together with order, correction, review and notification history.

Google sign-in and Drive

Google sign-in verifies your personal account through Supabase Auth. Connecting Google Drive is a separate choice by a workspace teammate. Baatchit requests your account email and the limited drive.file permission to create app folders, upload files and retrieve files used with Baatchit. This permission can also edit or delete those specific files, including cleaning up failed uploads.

The connected account's encrypted refresh token is held on the server so authorized workspace uploads and downloads can continue without its user being online. Tokens and Google client secrets are not returned to teammates or Partners. Baatchit uses Google information for sign-in and the requested workspace features, not for advertising or sale of Google data.

Baatchit's use of information received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements.

Storage and service providers

The application runs through OpenAI Sites on Cloudflare. Structured records use the Site's D1 database. Personal authentication uses Supabase Auth and your sign-in provider. New uploaded files use your workspace's connected Google Drive; preserved older uploads can remain in private R2 storage. Files you link retain their original provider and permissions.

Baatchit uses essential sign-in and connection cookies. Providers process information needed to deliver their services under their own policies. If you use connected Baatchit tools in ChatGPT, accessible project content requested by that interaction is returned to that service.

Who can see the work

Current teammates share access within their workspace. Member spending is team-readable and member-editable. Project Partners see their own submissions and the deliberately shared project content, including separate shared spending and selected work. Internal blockers, resource notes, decisions, earlier internal work history, team notifications and internal totals are not included in that shared view.

Sharing inside Baatchit does not make a Drive file public or change an original linked file's permissions. The connected Drive account can also access its files directly through Google Drive. Removing a Baatchit membership does not revoke a person's independent access granted outside Baatchit.

Your choices and retained history

You can change your own display name, choose what to submit or share and revoke Baatchit's Google access through Google Account connections. Revocation stops further Drive access; it does not delete existing files or workspace records. A teammate can reconnect the same storage account.

Workspace records, versions and correction history remain stored for collaboration and audit. Archiving an item or replacing a file does not purge its history or original stored file. For questions or requests about your data, account access or deletion, contact jindalabhishek455@gmail.com. Provider retention and independently shared originals may require separate action with those services.