Legal

Privacy Policy

Last updated: 1 January 2026. This policy explains what personal data we collect, how we use it, and your rights in relation to it.

1. Who We Are

Albanika Press operates the APIA platform at intelarchive.com. For questions about this policy, contact us at hello@intelarchive.com.

2. Data We Collect

Account information. When you register, we collect your email address and the name you provide. Authentication is handled by Clerk; we store only the Clerk user ID on our side to associate your account with your subscription, folders, and download history.

Subscription and billing. Payment processing is handled by Stripe. We do not store card numbers or full payment details. We receive confirmation of payment status, subscription tier, and transaction amounts from Stripe.

Usage data. We record which documents you download (to track page credits and enable free re-downloads), your saved searches, research folders, and AI query history. This data is tied to your account and stored in our database.

Log data. Our hosting infrastructure (Vercel) automatically collects standard server logs including IP addresses, browser type, and pages visited. These logs are retained for a short period for security and debugging purposes.

3. How We Use Your Data

  • To provide and maintain your access to the Service
  • To process payments and manage your subscription
  • To enforce page credit allowances and quota limits
  • To restore your research workspace (folders, saved searches) across sessions
  • To send you transactional emails (account confirmations, billing receipts)
  • To detect and prevent fraud, abuse, and security incidents
  • To improve the Service through aggregated, anonymised usage analytics

We do not sell your personal data to third parties. We do not use your data for advertising.

4. Third-Party Services

We rely on the following sub-processors to operate the Service:

ClerkIdentity and authentication
StripePayment processing
SupabaseDatabase hosting (PostgreSQL)
VercelApplication hosting and edge delivery
Cloudflare R2Document and asset storage
AnthropicAI Research Assistant (Claude API)

Each sub-processor handles data in accordance with its own privacy policy and, where applicable, data processing agreements with Albanika Press.

5. AI Research Assistant and Document Queries

When you use the AI Research Assistant, your query and relevant document excerpts are sent to the Anthropic Claude API for processing. Anthropic's usage policies prohibit them from training models on API inputs by default. We do not log the content of AI responses beyond what is stored in your saved chat history within APIA.

6. Data Retention

We retain your account data and usage history for as long as your account remains active. If you delete your account, we will delete or anonymise your personal data within 30 days, except where we are required to retain it for legal or financial compliance purposes (e.g. billing records, which may be retained for up to 7 years).

7. Cookies

APIA uses session cookies and local storage to maintain your authenticated session (managed by Clerk). We do not use third-party tracking or advertising cookies. You can disable cookies in your browser settings, but this will prevent you from signing in.

8. Your Rights

Depending on your jurisdiction, you may have the right to access, correct, or delete the personal data we hold about you, to restrict or object to processing, or to receive a portable copy of your data. To exercise any of these rights, email us at hello@intelarchive.com. We will respond within 30 days.

9. Security

We use industry-standard measures to protect your data, including TLS encryption in transit, hashed credentials via Clerk, private-bucket storage with short-lived signed URLs for documents, and restricted database access. No system is perfectly secure; if you discover a vulnerability, please disclose it responsibly to support@intelarchive.com.

10. Children

APIA is not directed at children under 16 years of age. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us and we will delete it promptly.

11. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be communicated by email or via a notice on the platform before taking effect. The date at the top of this page indicates when the policy was last revised.

12. Contact

For privacy-related enquiries or to exercise your rights, contact us at hello@intelarchive.com.

13. MCP Connector (AI Assistant Integration)

Intelligence Archive offers a connector for AI assistants (including Claude) via the Model Context Protocol (MCP). This section describes how the MCP connector handles your data.

Document data returned to the AI assistant. When you use the connector through an AI assistant, it returns document title, date, classification marking, collection scope, AI-generated synopsis, extracted entities (persons, organisations, locations), CIA cryptonyms, page count, dominant themes, and a direct link to the document on Intelligence Archive.

Document data never returned to the AI assistant. Full OCR text (raw page transcriptions) is used internally to power search relevance but is never sent to the AI assistant through any tool. Raw PDF storage keys and direct file URLs are also never exposed.

User account data accessed during authentication. When you authenticate the connector with your Intelligence Archive account, the connector reads your account tier (Free, Researcher, or Scholar) and an internal account identifier. This is used solely to determine which citation formats you are entitled to access. Your email address and name are never read by the MCP connector and are never sent to the AI assistant.

Data retention. The MCP connector is stateless. It does not store, log, or retain the content of your research queries or the documents returned in any response. Each tool call is processed independently and no conversation history is retained by the connector. Standard server logs (Vercel) may record request metadata such as timestamps and HTTP status codes for operational monitoring; they do not contain query content or document data.

Authentication and revoking access. If you authenticate the connector with your Intelligence Archive account, an OAuth connection is established via Clerk. You can revoke this connection at any time through your AI assistant's connector or integration settings, or by contacting us at support@intelarchive.com. Revoking the connection does not affect your Intelligence Archive account or any data stored within it.

Unauthenticated use. Search and discovery tools (document search, entity search, cryptonym lookup, and document retrieval) are available without authentication. No account or personal data is required to use these tools.

Rate limiting. To protect service availability, unauthenticated requests are rate-limited by network IP address using a short-lived sliding window. No personal data is stored as part of this process.

Questions about the MCP connector and privacy can be directed to support@intelarchive.com.