Providers we use
These companies run part of Artica for us. Each one receives only what its job needs, under its own data protection terms. Encryption in transit and at rest applies throughout.
| Provider | What for | What it receives | Where | Terms |
|---|---|---|---|---|
| Vercel | Hosting, the website and our servers | Every request to artica.tools, including content passing through unstored (exported tickets and articles, Format fixer articles, pasted keys in sealed form); request logs with IP address and user agent, kept about an hour | United States (our servers); global network for delivery | Privacy policy |
| Clerk | Sign-in and accounts | Your email, name if given, password (hashed), sign-in records with IP address, browser and device | United States | Privacy policy |
| Neon | Database | Account, workspace, usage, article, capture, connection (tokens encrypted), Topic finder result and page-view records | United States (AWS us-east-1, Virginia) | Privacy policy |
| Cloudflare (R2) | File storage | Capture screenshots, article images, and uploaded ticket files until their analysis starts | Cloudflare’s network; the bucket is not restricted to one jurisdiction | Privacy policy |
| Modal | Processing service | Uploaded ticket files and Zendesk tickets, in memory, during a Topic finder analysis; a fresh Zendesk access token per analysis; ticket text and names for a scrubbed Ticket exporter export; logs with counts and ids only | A US company; our jobs are not pinned to a region and may run in any region Modal uses | Privacy policy |
| Anthropic | AI (Claude models) | Redacted capture screenshots, step text, page titles and addresses; scrubbed ticket subjects and first messages and scrubbed file samples; AI-written questions; Format fixer article text with personal data and links replaced | United States | Privacy policy |
| Resend | Sending email | Recipient addresses and the content of the emails we send (welcome, analysis ready, requests and summaries to us) | United States | Privacy policy |
| Google (Workspace) | Our mailbox for hello@artica.tools | Emails you send us and our replies; custom theme requests; our sign-up alerts and daily summaries (emails masked) | Global | Privacy policy |
Not active: Stripe (payments) is integrated but switched off. It receives nothing today. If we turn payments on, Stripe will be added to this table first.
Integrations you choose
These aren’t our subprocessors: they are platforms you use and connect yourself, under your own agreements with them. Artica sends requests to them only when you connect them and use a tool.
| Platform | When | What happens |
|---|---|---|
| Zendesk | You connect it (Ticket exporter, Article exporter, Topic finder, Article generator, Format fixer) | Artica reads tickets and help center content with the access you grant, and writes only when you ask: exporting an article as a draft, or saving a fixed article |
| Intercom, Freshdesk, Help Scout | You paste a key or token in Article exporter | Artica reads your help center’s articles for that export only; the key is never stored |
| Any public help center | You paste its link in Article exporter or Format fixer | Artica reads public pages, one at a time, following robots.txt |
| Google Chrome and the Chrome Web Store | You install the extension | Chrome runs the extension; the store distributes updates |
Changes to this list
When we add or replace a subprocessor, we update this page and its date before the new provider receives any data. To be told by email, write to hello@artica.tools with the subject “Subprocessor updates”; we will email you at least 14 days before a new subprocessor starts processing your customer data, so you can object under our DPA.