Privacy Policy

Ajolla is operated as an early-access developer infrastructure product that turns OpenAPI specifications into TypeScript SDKs, developer documentation, and Model Context Protocol (MCP) servers. The data we process is limited to what is needed to deliver those features, secure the workspace, and operate the service reliably.

For any privacy question, data-access request, or data-deletion request, contact privacy@ajolla.dev. We aim to acknowledge within five business days.

• Account identifiers: your email address (always) and basic profile attributes returned by your authentication provider when you sign in with Google or GitHub (display name, avatar URL, provider user ID).
• Authentication telemetry: timestamps of magic-link sends, OAuth sign-ins, sign-outs, and failed attempts, used for security and abuse prevention.
• Workspace content: OpenAPI documents you upload, derived metadata (endpoints, schemas, security schemes, tags), validation issues raised during parsing, and the cached parsed intermediate representation used to power the previews.
• Generated artifacts: TypeScript SDK packages, MCP server packages, and the documentation site rendered live from your spec — all scoped to the project that produced them.
• Activity events: append-only records of project creation, spec ingestion, and generation runs, used to render the dashboard activity feed and for audit-style review.
• Operational telemetry: error reports captured by Sentry, request-level diagnostics, and rate-limit counters held in Upstash Redis. These contain HTTP context such as URL paths, status codes, browser type, and the IP-derived rate-limit key — but never the body of an uploaded spec or a generated artifact.
• Cookies: a small number of strictly necessary cookies set by our authentication provider and web framework to keep you signed in and to remember your theme preference. The providers behind these are listed in the sub-processors section.

• To create and authenticate your workspace account and to deliver magic-link or OAuth sign-in.
• To parse the OpenAPI specifications you upload, generate the SDK, docs, and MCP artifacts, and present them in the in-browser preview.
• To store generated artifacts so you can re-download them without re-running the generator.
• To enforce project ownership boundaries through row-level security and to defend the service against abuse (rate limiting, error monitoring, anomaly review).
• To investigate incidents, support requests, and security events in a way that lets us reproduce the issue.
• To improve the product, including diagnosing parser regressions on real specs and improving codegen quality. We do not train models on your specs or generated artifacts.

• Contract — to deliver the product and the features you sign up for.
• Legitimate interests — to keep the service available, secure, and free of abuse.
• Consent — for any optional analytics or marketing communications, which you can withdraw at any time.
• Legal obligation — to respond to verified law-enforcement requests or other legally compelled disclosures.

• Account data is retained for as long as your account exists. When you delete the account, identifiable account data is removed within 30 days, except where retention is required for legal, accounting, or security reasons.
• Uploaded specs and generated artifacts are retained for as long as the parent project exists. Deleting a project removes the rows immediately and the storage objects within 30 days.
• Activity events are retained for 18 months for audit purposes, then deleted.
• Operational telemetry (Sentry errors, rate-limit counters) is retained for at most 90 days.
• Backups follow a rolling 35-day window and are encrypted at rest.

Ajolla uses the following sub-processors to operate the service. Each is bound by contractual data-protection obligations and only receives the data it needs to perform its function.

• Vercel — application hosting, edge runtime, and TLS termination.
• Supabase — Postgres database, authentication, and object storage for uploaded specs and generated artifacts.
• Upstash — Redis-backed rate-limit and abuse-prevention counters.
• Sentry — error monitoring and performance diagnostics.
• Resend — transactional email delivery for magic-link sign-in.
• Cloudflare — DNS and DDoS protection for the production domain.

The list above is the current set of sub-processors. We will provide reasonable advance notice before adding or replacing a sub-processor that processes customer content, by updating this page and notifying account owners by email.

• Authentication cookies set by Supabase Auth to keep your session signed in across requests.
• A theme cookie set by next-themes to remember your preferred light/dark mode.
• No third-party advertising cookies are set. No cross-site tracking pixels are loaded on the marketing site.

Ajolla operates on infrastructure that may process data in the United States and the European Union. Where personal data is transferred from the EEA, UK, or Switzerland, we rely on the European Commission’s Standard Contractual Clauses (and the UK Addendum where applicable) as the transfer mechanism, along with the technical safeguards described in the Security Policy.

• Access — request a copy of the personal data we hold about you.
• Correction — ask us to correct inaccurate or incomplete personal data.
• Deletion — ask us to delete personal data when there is no overriding legal or operational reason to retain it.
• Portability — request an export of the OpenAPI specs and generated artifacts in your workspace.
• Objection — object to processing based on legitimate interests in specific circumstances.
• Lodge a complaint — if you are in the EU/UK, you have the right to lodge a complaint with your local supervisory authority.

To exercise any of these rights, email privacy@ajolla.dev. We will verify your identity before acting on the request and respond within 30 days, or notify you if an extension is required.

Ajolla is not directed at children under 16, and we do not knowingly collect personal data from anyone under 16. If you believe a child has provided personal data to us, contact us so we can delete it.

We may revise this policy as the product evolves. Material changes will be announced in-product or by email to affected accounts before they take effect. The “Last updated” date at the top of the page reflects the most recent revision.