Privacy Policy

What Alexandria is

Alexandria provides instructions that your own AI uses to build and read a detailed mirror of your thinking. The strongest available private home may be user-owned Git files, documents in your own Google Drive, or your AI provider’s personalisation. If none is writable, your AI leaves an explicit handoff in the chat instead of claiming it saved anything. An optional hosted connector lets compatible loops use the Library, Marketplace, membership, and publishing features.

Your private mirror stays private

Your private mirror stays with the storage or AI provider you chose. Private Git and Drive files remain in accounts you control; native memories remain with your AI provider. Alexandria has no endpoint that accepts this private material and cannot read or retrieve it. Backups and cross-app connections are optional and use only accounts you approve.

This promise covers the private mirror. Information you deliberately publish, feedback you submit, and the connector records described below do reach services we operate.

What the hosted connector stores

Account and billing records. Your GitHub ID and login, email address, billing status, and Stripe customer or subscription identifiers. Account records are encrypted at rest.

Authentication records. A SHA-256 hash of your Alexandria API key; the raw key stays on your machine. Short-lived browser session and onboarding tokens are also stored when those flows are used.

Onboarding email. If you provide your email when you start Alexandria, we store it so we can send the matching setup message, help you finish, and occasionally send useful product notes. Every message has an unsubscribe link. Your private files and captures are never part of this email record.

Service activity. A 60-day log of which Alexandria endpoints your account used and when; module IDs you explicitly approve reporting, with any notes you explicitly attach; Library publishing, access, purchase, account-connection events, and feedback you explicitly submit.

Content you publish. Files, works, quizzes, profile details, and other material you deliberately send to the Library, together with their titles, access settings, prices, and file metadata.

Website analytics

We use Vercel Web Analytics for aggregate page views, referrers, country or region, browser, operating system, and device type. Vercel says this service uses no cookies, stores anonymised data, and resets its visitor-identification hash every 24 hours. We do not use advertising trackers or cross-site fingerprinting. Read Vercel’s analytics privacy documentation.

Payments

Stripe processes payments. Alexandria does not receive or store complete card numbers. Stripe receives the information needed to process the payment and keeps it under Stripe’s privacy policy.

Retention

Account records stay while your account is active. Endpoint event logs expire after 60 days. Module-call, Library activity, transaction, and submitted-feedback records do not currently expire automatically. Published content stays until you unpublish it or delete your account; unpublishing cannot recall copies someone already downloaded or shared. We may retain records when required for security, fraud prevention, payments, disputes, or law.

Your choices and rights

Your private mirror is already portable: ordinary files you can read, edit, move, or delete. Deleting ~/alexandria/ removes the local loop but does not delete an optional hosted account.

Depending on where you live, you may have rights to know or access personal data, correct it, delete it, receive a portable copy, restrict or object to processing, and appeal a decision. We do not sell personal information or share it for cross-context behavioural advertising.

To exercise a right, delete an account, or ask us to remove submitted feedback, email benmowinckel@gmail.com. We may need to verify your identity. We will answer within the period required by applicable law.

You can sign out of the website from the library. That ends the browser session on this device. It does not delete your account or the key on your computer.

Contact

Benjamin a. Mowinckel — benmowinckel@gmail.com

Terms of Service