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. Ajolla also hosts application modules and offers optional AI-assisted tools. We process data to deliver these features, secure accounts, handle billing, and operate the service.

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.
• Hosted application content: records and files submitted to your enabled modules, end-user identifiers, app settings, and integration secrets you configure. The exact content depends on the modules and data you choose to host.
• Billing metadata: Stripe customer and subscription identifiers, plan, subscription status, and metered usage. Payment details entered in Stripe Checkout or its customer portal go directly to Stripe; Ajolla does not store full payment-card numbers.
• AI feature inputs and outputs: prompts, selected specification or repository context, tool inputs and results, generated responses, and usage counts when you invoke AI-assisted features. These inputs are sent through Vercel AI Gateway to the model provider used for the request.
• 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 and performance reports captured by Sentry when configured, hosting logs, and rate-limit counters in Upstash Redis. Reports can include URL paths, error details, browser information and request context. Avoid putting credentials or sensitive personal data in URLs or error messages.
• Product analytics: Wandamark receives sign-up and session events, including the account identifier and profile display name when available, plus availability test events.
• Browser storage: authentication cookies keep you signed in, and local storage remembers your theme preference.

• 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 run hosted application modules, deliver their configured emails, process subscriptions and usage, and perform AI-assisted tasks you request.
• 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 while your account exists. The account-deletion flow removes your account and associated workspace data from the active service. Provider records and operational backup copies are separate; deleting the account does not automatically erase them.
• Uploaded specs and generated artifacts remain in workspace storage until removed through supported deletion flows. We do not currently promise an independent scheduled purge of project files.
• Workspace activity events currently remain with the account until account deletion; an automatic 18-month deletion schedule is not implemented.
• Hosted application records remain until deleted through the module, app deletion, or account deletion, except for module-specific retention described in the module documentation. Deleting your Ajolla account does not delete copies you exported or data held in services you connected separately.
• Rate-limit counters expire automatically. Hosting, monitoring, analytics, email and payment providers retain their records under their respective service settings and obligations; a single 90-day maximum across those providers has not been verified.
• During beta, Ajolla does not guarantee backup availability, a retention window, or recovery of deleted or lost data. Keep your own copies of specifications, artifacts and hosted application data. Operational backup copies, when taken, are separate from the active account data and do not constitute a recovery guarantee.

Ajolla uses the following service providers. Some providers, including payment providers, may also process information for their own legal and security purposes under their terms and privacy notices.

• Vercel — application hosting, DNS, TLS termination, AI Gateway routing, and isolated execution for code features.
• 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 and configured hosted application emails.
• Stripe — subscription checkout, customer portal, billing and metered usage.
• Anthropic — the currently configured default model provider for optional AI-assisted features, accessed through Vercel AI Gateway. Other model providers may be used if the service configuration changes; this inventory must be updated when that occurs.
• OpenAI — the default embedding provider for the optional hosted AI Assistant's document search, accessed through Vercel AI Gateway using the app owner's configured key. Hosted AI Assistant owners can select other gateway models; the selected model provider receives the relevant chat or document content.
• Wandamark — product analytics, sign-up and session events, and availability monitoring.
• GitHub — repository access when you connect or import a repository, and source-code hosting for Ajolla itself.

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.
• Local storage used 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.

The current database is hosted in the United States. Other service providers may process information in additional countries under their service terms. Ajolla does not currently offer a customer-selected data-residency region. The provider-specific transfer safeguards and contractual inventory are still being verified for public beta; this notice does not claim that a completed transfer assessment or a particular contractual safeguard is already in place.

• 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.