Privacy · Private beta information

Responsible person and privacy contact

Albert Pons Vega is responsible for CAPIBARA and is based in Spain. You can contact him about privacy at capibara.support@gmail.com, including if you cannot sign in.

You may request access, rectification, erasure, restriction or portability of your data, and object where applicable. Requests are normally addressed within one month, subject to identity checks and any lawful extensions or retention exceptions. You may complain to the Spanish Data Protection Agency (AEPD).

Your data and privacy

Google sign-in provides an account identifier and, when available, your verified email and profile name. CAPIBARA stores account/session records, project and endpoint definitions, saved SQL, plan/credit activity and any feedback or support-access grants you create.

These records provide sign-in, saved designs, generation, allowances, abuse prevention and support. CAPIBARA does not store your Google password or collect card details. Server sessions and browser theme/session storage are used for application operation; this notice is not an advertising-cookie consent request.

CAPIBARA uses bounded operational logs designed to omit request bodies, cookies, SQL and OAuth tokens. Hosting/provider diagnostics and backups require separate operator controls. Do not put real personal data, passwords, access tokens or confidential production information into test projects or feedback.

Support and feedback

Use Support in the workspace to send a message when the email channel is configured. Sending a message does not grant access to a project. Project review requires your separate 24-hour read-only grant, which you can revoke; administrators cannot edit or download a customer's API through that support access.

Feedback is available to eligible invitation testers while the feature is enabled. Feedback can remain stored after the feedback screen is disabled. Contact the operator through Support for privacy or deletion requests; no automatic account-erasure workflow is currently provided.

Beta retention policy

Accounts and saved projects are retained while the account exists. Verified erasure requests are handled within one month where applicable; data needed for legal obligations or claims may be retained only as necessary. Deleting an account also requires handling its associated records.

Beta feedback is retained for 90 days after submission. Support email is retained for 90 days after the last interaction. Backup copies have a maximum intended age of 30 days; deleted data can remain in isolated backups until those copies expire.

Operational logs have a 48-hour retention target. The existing bounded hourly rotation alone does not enforce a strict age limit. Scheduled cleanup, mailbox and backup expiry must be configured and verified before external testers are invited. These limits are the defined beta operating policy, not a claim that every automatic cleanup job already exists.

Purpose, providers and launch scope

Account and project processing supports the service you request. Security and abuse prevention support legitimate operational interests. Optional feedback is used to improve the beta. Google handles sign-in, and the configured Gmail channel delivers support messages; each provider also has its own privacy practices. CAPIBARA does not sell your project data.

This build is for private testing. The actual hosting/backup providers, processing locations, applicable transfer safeguards and operator procedures must be documented before external invitations open. Generated ZIPs are independent applications: you are responsible for their credentials, database access and deployment.