Last updated: October 12, 2026

Augself ("we", "our", or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard your information when you use our digital twin platform. We comply with the General Data Protection Regulation (GDPR) and Swiss data protection laws.

What a twin is, and which data is public

A twin is a public-facing publishing tool. It answers questions about its owner, from the documents its owner uploads, for anyone who opens its link. That is the product working as intended, and it means the two kinds of data in Augself are not treated the same way.

Documents you upload are public by design

Anything you add to your twin's knowledge base can be surfaced, quoted or paraphrased in a conversation with any visitor. Your twin exists in order to do that. Upload only what you are content for anyone with the link to read, and keep private records, client confidential material and anything you would not publish out of the knowledge base.

Visitor conversations are not public

What a visitor types to a twin is that visitor's own personal data, and we are responsible for it. Conversations are visible to the twin's owner and to us as the platform operator; they are not published, and another visitor opening the same twin cannot see them. This is where the obligations described in the rest of this policy mainly apply, because a visitor can disclose far more about themselves in a conversation than an owner ever meant to publish.

Owners of a Discovery Assistant should read this the same way: the business documents behind it are published to prospects, and what a prospect says in reply is their own confidential information, held on their behalf rather than yours.

1. Data Controller

Augself is the data controller responsible for your personal data. For any privacy-related inquiries, please contact us at:

Email: privacy@augself.ai

2. Information We Collect

2.1 Account Information

Email address (required for account creation)
Full name (optional)
Password (stored securely using bcrypt hashing)
How you arrived: the campaign tags carried by the link you followed, if it carried any, and the address of the site that linked to you

We read this once, when you first open the site, and we keep it only if you then create an account. It is how we tell which of our own links and which referring sites bring people to Augself. Your browser normally sends us only the site name, not the page you were reading. We do not use it to build a profile of you, we do not share it with anyone, and we record nothing at all about visitors who do not register.

2.2 Content You Provide

Documents you upload to train your digital twin
Twin configuration (name, bio, personality settings)

What visitors say to your twin is not covered here. It is their data rather than yours, and it is described in 2.5 below.

2.3 Payment Information

Payment processing is handled by Stripe. We do not store your credit card details. We receive only confirmation of payment status and Stripe customer ID.

2.4 Usage Data

Chat message counts and usage statistics
Login timestamps
Feature usage patterns

2.5 Visitor Conversations

When someone opens a twin's public link and starts a conversation, we collect the following about that visitor. We collect it from the visitor, and the twin's owner can read it:

The messages they send and the replies the twin generates
A session identifier, stored in their browser, which lets them return to their own conversation
Their IP address and browser user agent, recorded when the conversation starts
For a Discovery Assistant, the contact and qualification details the assistant captures when a visitor offers them: name, email address, company, role, what they said they need, and a summary of the conversation

A visitor does not need an account, and we do not ask them to create one.

3. How We Use Your Information

We use your information to:

Provide and maintain the Service
Process your digital twin's responses using AI
Process payments and manage subscriptions
Send important service notifications
Improve our Service based on usage patterns
Comply with legal obligations

4. Legal Basis for Processing (GDPR)

We process your data based on:

Contract: Processing necessary to provide the Service you requested
Legitimate Interest: Improving our Service and ensuring security
Legal Obligation: Compliance with applicable laws
Consent: Where explicitly provided for optional features

5. Data Sharing and Third Parties

We share data with the following third parties:

5.1 AI Providers

To generate AI responses, we send relevant document content and chat messages to:

OpenAI (for GPT models)
Anthropic (for Claude models)

These providers process data according to their respective privacy policies and data processing agreements.

5.2 Payment Processing

Stripe processes all payments. Your payment information is handled directly by Stripe under their Privacy Policy.

5.3 Infrastructure

Our Service is hosted on Railway, which provides secure cloud infrastructure. Railway holds everything the Service stores: accounts, uploaded documents, the vector index built from them, and conversation history. Section 10 names the region.

5.4 Email Delivery

Transactional email is sent through Resend, which receives the recipient's email address and the content of the message. That content includes:

Account email: verification and password reset links, welcome messages
Notifications to a twin's owner: the visitor's question, a summary of the conversation, and the visitor's name and email address where they gave them
For a Discovery Assistant, the lead summary described in 2.5, sent to the owner
Contact form submissions, sent to our support address

5.5 Image Hosting

Profile pictures and chat avatars are uploaded to, stored and resized by Cloudinary, which receives the image file and an identifier derived from your account or twin. No documents, conversations or account details are sent to Cloudinary.

Neither Resend nor Cloudinary is currently configured with an EU processing region; section 10 explains the safeguards that apply.

5.6 Error Reporting

Sentry receives error diagnostics from the hosted Service, processed in the European Union. It is configured to exclude request bodies, user identifiers and performance tracing. Because an error message or a log line can quote a value, we name Sentry as a processor rather than claim it never receives personal data.

6. Data Retention

Active accounts: Data retained while your account is active
Deleted accounts: Deleting your account blocks sign-in immediately and marks the account for deletion. For 30 days you can restore it by signing in and confirming recovery. After that it is erased
Chat logs: Retained until the twin's owner deletes them, or until the owner's account is erased
Payment records: Retained as required by law (typically 7 years)

Erasure runs automatically. A daily process permanently deletes every account whose 30 days have passed, so deletion happens within a day of the grace period ending rather than waiting for anyone to act. It removes the account record, the twins you created, the documents you uploaded, the search index built from them, and the conversations your twins held, including visitors' messages. It cannot be undone.

Payment records are the exception and are kept for the period the law requires. If you want confirmation that your data has been erased, or erasure sooner than the grace period allows, email privacy@augself.ai. Your right to erasure under section 7 is separate from the grace period and we act on it when you ask.

7. Your Rights (GDPR)

Under GDPR, you have the right to:

Access: Request a copy of your personal data
Rectification: Correct inaccurate personal data
Erasure: Request deletion of your personal data
Restriction: Request limitation of processing
Portability: Receive your data in a portable format
Objection: Object to certain processing activities
Withdraw Consent: Where processing is based on consent

To exercise these rights, contact us at privacy@augself.ai. We will respond within 30 days.

8. Self-Hosted Deployments

For self-hosted deployments, your data remains entirely on your own infrastructure. The only data transmitted to Augself is:

License key validation requests (license key and instance ID)

No document content, chat messages, or personal data is transmitted to our servers in self-hosted mode.

9. Data Security

We implement appropriate security measures including:

Encryption of data in transit (HTTPS/TLS)
Secure password hashing (bcrypt)
Access controls and authentication
Automated availability checks on the hosted Service

10. International Data Transfers

The Service stores your data inside the European Economic Area (EEA) and sends some of it outside the EEA to be processed. The hosted Service runs on Railway infrastructure in the Netherlands (Amsterdam, europe-west4), which is where accounts, documents, chat history and the vector store are held. This moved from the United States (Oregon, us-west2) on 8 October 2026.

Processing still happens outside the EEA. The AI providers named in section 5.1 generate responses and embeddings in the United States, so the text of your documents and the content of conversations is transferred there each time a twin answers. The email and image providers named in sections 5.4 and 5.5 may also process outside the EEA.

We keep off-platform backups of the production database on encrypted storage in Switzerland, which the European Commission recognises as providing an adequate level of data protection.

Where the Service runs is a configuration choice and may change again. This section states where it runs today. It is not a commitment to keep your data in any particular country, and nothing elsewhere in the Service should be read as one.

For the transfers out of the EEA described above, we rely on appropriate safeguards, including:

Standard Contractual Clauses approved by the European Commission
Data processing agreements with all third-party providers

If your data must stay within a particular jurisdiction, use a self-hosted deployment, where it never reaches our infrastructure at all (see section 8).

11. Cookies

We use essential cookies for authentication and session management. We do not use tracking or advertising cookies. Essential cookies cannot be disabled as they are necessary for the Service to function.

We also use your browser's own session storage to hold the arrival details described in section 2.1 between the page you land on and the registration form. It is cleared when you close the tab, it is never read by another website, and it is not used to recognise you on a later visit.

12. Children's Privacy

Our Service is not intended for children under 16. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us.

13. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of significant changes via email or through the Service. The "Last updated" date at the top indicates the most recent revision.

14. Supervisory Authority

If you are in the EEA or Switzerland and believe we have not adequately addressed your concerns, you have the right to lodge a complaint with your local data protection authority.

For Switzerland: Federal Data Protection and Information Commissioner (FDPIC)

15. Contact Us

For any questions about this Privacy Policy or our data practices:

Email: privacy@augself.ai