Legal
These are the vendors we use to run Artica, and — more useful than most such lists — exactly what each one receives. The most important row to understand: ticket text reaches only the ephemeral processing layer and the AI providers that read and analyse tickets mid-run. It never reaches storage.
| Subprocessor | Location | Role | What it receives |
|---|---|---|---|
| Vercel Inc. | US | Application hosting; product analytics | Traffic in transit; request logs. Inside the product, cookieless page-view counts (route, referrer, coarse device and browser data) — no user identifiers, no cross-site tracking, nothing on the marketing site |
| Neon Inc. | US | Database (Postgres) | Account data, derived taxonomy (labels, vectors, counts, ticket IDs), article content, encrypted Zendesk tokens. Never ticket text — enforced by an automated build check |
| Cloudflare, Inc. | US | File storage (R2) | Browser-redacted screenshots and article images, in a private bucket under workspace-scoped keys |
| Modal Labs, Inc. | US | Ephemeral compute for ticket analysis | Ticket text in memory, for the duration of a processing run only — never written to a table, volume, or file |
| Functional Software, Inc. (Sentry) | US | Error monitoring | Error reports: stack traces, the request path (query string removed), and error messages passed through the same redaction that guards our own logs before they leave the process. Personal-data capture is off and there is no session replay. No ticket text |
| Inngest Inc. | US | Durable job orchestration | Workspace and run identifiers, job progress state, and derived topic metadata (titles, descriptions). No ticket text, no credentials |
| OpenAI, LLC | US | Text embeddings | Ticket text transiently, to produce vectors; help-center article text |
| Anthropic, PBC | US | AI analysis, generation, and matching | Each ticket's text, read transiently during a run to distil the customer's request — never stored; redacted screenshots; topic and article content |
| Clerk, Inc. | US | Sign-in | Name, email, credentials / OAuth identity |
| Stripe, Inc. | US | Billing | Payment details, collected on Stripe's own surfaces — Artica stores only customer and subscription IDs |
| Resend (Plus Five Five, Inc.) | US | Email delivery | Recipient name and email; email content |
| Zendesk, Inc. | US | Your own helpdesk | The source and destination: Artica reads tickets and help-center content under your OAuth grant, and receives back the drafts and images you export |
We update this page and email workspace Owners at least 30 days before adding or replacing a subprocessor.
GitHub hosts our source code and build pipeline. No customer data flows there — our automated data-retention check runs against a disposable database containing no customer data.
Questions? hello@askartica.com · See also Security and the DPA.