Inkagai is a product operated by Algodyne Corporation, a Delaware corporation.
This register identifies external providers authorized for production processing. A provider must not be represented as active merely because an integration, binding, or future design exists in source code.
| Provider | Service category | Data or content processed | Activation boundary |
|---|---|---|---|
| Cloudflare | Hosting, Workers, D1, R2, KV, DNS, content delivery, security, Turnstile, transactional email, and observability | Request metadata, account and product data stored in enabled Cloudflare services, media and artifacts stored in enabled buckets, transactional email delivery data, and security events | Active only for the specific production bindings and services configured in the deployed environment; author campaign delivery is not active |
| Stripe | Checkout, payments, billing, tax, fraud prevention, refunds, and disputes | Customer and checkout information, payment method information, transaction data, tax information, fraud signals, refunds, and disputes | Active only when production billing is provisioned and a user enters a Stripe-supported payment flow |
| Contact mailboxes (Gmail) receiving mail forwarded from privacy@inkagai.com, support@inkagai.com, and legal@inkagai.com | The contents and headers of email a person sends to those contact addresses | Active for inbound contact mail only; no account or product data is stored with Google | |
| Crossref | Bibliographic metadata lookup (DOI resolution) through the Crossref REST API at api.crossref.org | Not a recipient of personal data (identifier-only, server-side): the DOI a signed-in user submits for resolution; the response is the corresponding publication metadata. No account content is sent | Queried server-side only when a signed-in user triggers a DOI lookup in the research features (per-account daily cap enforced by Inkagai). Outbound, user-triggered lookup: no direct user relationship, no DPA executed |
| arXiv (Cornell University) | Bibliographic metadata lookup (arXiv identifier resolution) through the arXiv Atom API at export.arxiv.org | Not a recipient of personal data (identifier-only, server-side): the arXiv identifier a signed-in user submits for resolution; the response is the corresponding publication metadata. No account content is sent | Queried server-side only when a signed-in user triggers an arXiv lookup in the research features (per-account daily cap enforced by Inkagai). Outbound, user-triggered lookup: no direct user relationship, no DPA executed |
Transfer posture. Cloudflare, Inc. is listed on the Data Privacy Framework List with status Active under the EU-U.S. DPF, the UK Extension to the EU-U.S. DPF, and the Swiss-U.S. DPF (verified November 11, 2026 at dataprivacyframework.gov/participant/5666; next certification due September 15, 2027), with Standard Contractual Clauses published as fallback. Stripe, LLC is listed on the Data Privacy Framework List with status Active under the EU-U.S. DPF, the UK Extension to the EU-U.S. DPF, and the Swiss-U.S. DPF (verified November 11, 2026 at dataprivacyframework.gov/participant/10014; next certification due May 11, 2027), with Standard Contractual Clauses published as fallback. The evidence requirement in Provider rules governs any claim Algodyne makes.
Outbound bibliographic lookups. Crossref and arXiv are not recipients of personal data (identifier-only, server-side). They are United States–operated public scholarly services queried server-side when a signed-in user asks the research tools to resolve a DOI or arXiv identifier. Inkagai sends only the validated identifier — caller-controlled URLs are rejected, redirects are refused, and responses are content-type checked and size-capped — and receives publication metadata back. The outbound client sets no contact information: no mailto parameter is sent and no User-Agent header is set (apps/worker/src/bibliography-metadata.ts). If a contact address is ever added for Crossref request etiquette, it must be an Algodyne operations address, never a user's address. No data-processing agreement is executed because there is no personal-data processing relationship.
Removed providers. Cloudflare Workers AI and OpenRouter were removed on October 1, 2026 (operator decision #2646: Inkagai provides no AI processing, sells no tokens, and routes no content to model providers). The Workers AI binding and the OpenRouter integration were deleted; no AI inputs are processed by any provider on Algodyne's behalf. Author-directed AI runs on the author's own connected model through the Author MCP and is not an Algodyne subprocessor relationship.
Provider rules
- Algodyne does not authorize a provider to use Private Content for model training without separate, explicit, opt-in authorization for the specific content and purpose.
- Optional providers must be added to this register before processing production user data.
- Author campaign delivery through Cloudflare remains inactive in production. Cloudflare documents Email Service as transactional-only; #982 records the operator's explicit accepted-risk exception for the isolated author-domain lane. The newsletter legal, vendor, transfer, and go/no-go evidence remains pending in
docs/compliance/newsletter-compliance-register.md; campaign delivery stays inactive until it is approved. - Removing a provider from production requires removing or updating every policy, configuration reference, and data-flow description that names it.
- Provider-specific retention, location, transfer, certification, or deletion claims require corresponding contractual and operational evidence.
Cloudflare contract and transfer posture
The contract packet includes the Cloudflare Customer DPA version 6.4, dated April 3, 2026, the Cloudflare Standard Contractual Clauses, and the Cloudflare subprocessor list. The Cloudflare Customer DPA is incorporated into the main agreement (operator acceptance confirmed November 11, 2026); Stripe's Data Processing Agreement is incorporated into the Stripe Services Agreement.
The public security packet includes the Cloudflare Information Security Exhibit and Cloudflare compliance resources, including its current SOC 2 Type II and ISO posture. Current audit reports, certificates, attestations, and penetration-test summaries are restricted in the signed-in dashboard behind confidentiality terms. Those terms have not been accepted and the restricted evidence has not been reviewed. The newsletter review also uses Cloudflare's APPI material and D1 data-location documentation.
Production, staging, preview, and dev D1 databases currently report jurisdiction: null. Because D1 jurisdiction is fixed at database creation, no EU, FedRAMP, Japan, or other regional-residency claim applies to the existing databases. Author newsletter production requires a named approver to accept this global-processing and transfer posture in docs/compliance/newsletter-compliance-register.md.
Contact
Legal notices, privacy requests, and policy questions: privacy@inkagai.com (support@inkagai.com as a fallback)
Operator: Algodyne Corporation, Delaware, United States