Privacy
Policy.

1. Who we are

Evil ASF, formerly known as Infinet, is operated by Clarity Digital Development ("we", "us", "our"). Our chat product is available at evilasf.com, and infinetai.org continues to reach the same service. Contact us at [email protected].

The rename on 12 August 2026 changed the product’s name and nothing else. The data controller, what we collect, how long we keep it and your rights over it are all unchanged, and no personal information was transferred to a new party.

2. Scope of this policy

This Privacy Policy covers personal information we collect when you use evilasf.com or infinetai.org, sign up for an account, subscribe to a paid plan, or communicate with us. It does not cover third-party services we link to (including our sister product artifacial.io, which has its own privacy policy).

3. What we collect

3.1 Account information

When you sign up, our authentication provider (Clerk) collects:

• Your email address
• A password hash (or an OAuth identifier if you sign in with Google, GitHub, etc.)
• Profile fields you choose to provide (name, profile picture)
• Session metadata (IP address, user agent, login timestamps) for security

3.2 Payment information

If you subscribe to a paid plan, our payment processor (Stripe) collects and processes your payment card details, billing address, and transaction history. We never see or store your full card number. We receive a Stripe customer ID, the subscription status, and the last four digits for reference.

3.3 Usage data

We record basic operational data:

• Token counts per message (to enforce plan limits)
• Request counts per day (rate limiting)
• Model used per request
• Timestamps of each interaction
• Chat and message identifiers (anonymous UUIDs)

3.4 Chat content (standard mode)

When you use the service in standard mode, the content of your messages is transmitted to our third-party AI inference providers so they can generate responses. Each message is also checked by an automated classifier, run by the same kind of provider, for the only two things we refuse: sexual content involving a minor, and sexual content depicting a real, identifiable person. When a message leads us to search our document archive, our server logs may record a short excerpt of that search (up to 50 characters) and the search terms derived from it, so we can diagnose search quality; our hosting provider keeps these logs for a limited period. Chat history is stored locally in your browser (via browser storage) by default, not on our servers. We do not train AI models on your content. We do not sell, rent, or share your content with advertisers or data brokers.

3.5 Chat content (Private Mode)

When you enable Private Mode (available on VIP and above), your conversation is answered only by models that run inside sealed, hardware-attested computing (a trusted execution environment); if none is available, your message is not sent. Nothing from a private conversation is saved: we do not write its content to our logs, nothing from it is saved to memory or shared, a conversation that has been private stays private, and your chat history stays in your browser. Web search, link previews, voice input and read-aloud are switched off in Private Mode, because each would send your words to a service outside sealed hardware.

Private Mode is not end-to-end encrypted. Our servers receive each message in readable form, in memory, in order to route it, to search our document archive and any memories you have saved, and to screen it for the two things we refuse; that screening also runs on a sealed-hardware model. Our inference provider also receives the message in readable form and relays it to the sealed hardware. We retain only metadata (timestamps, token counts, model used) for billing and operational purposes.

3.6 Community chat

Community rooms and direct messages are stored on our servers. This is different from your conversations with the AI, described above, which stay in your browser. A chat room cannot function without server-side storage, so if you use community chat, assume the messages are retained.

Community messages are not end-to-end encrypted, and Private Mode does not apply to them. We can access message content in rooms and direct messages, including private rooms, and we do so where it is necessary to investigate a report, respond to automated safety screening, enforce the Terms, or comply with a legal obligation. Messages are screened automatically for a narrow set of serious harms — sexual content involving minors, trafficking, credible threats of violence, publishing a private person’s identifying details, and indications of self-harm. We do not screen for opinions, language, or subject matter.

The handle you choose is visible to other members. Deleted and removed messages are hidden from the room but retained in our records, because a deleted message is often the evidence for the report about it. If you do not want a message stored on our servers, do not post it in community chat.

3.7 Shared chat links

If you use the Share button on a conversation, a copy of that conversation is stored on our servers so the link can be opened by whoever you send it to. This is the only case in which your chat with the AI is stored by us, and it happens only when you choose it. The dialog says so before the link is created.

What is stored is a snapshot taken at the moment you shared — messages you send afterwards do not appear on a link you already shared. System instructions, saved memories and any images in the conversation are not included. The link is a random, unguessable address; the page is not indexed by search engines, but anyone you give the link to can read it and can pass it on.

Shared links expire automatically after 30 days and are deleted from our servers. You can revoke one sooner at any time in Settings, which deletes it rather than merely hiding it. Deleting your account deletes all of them. Private Mode conversations cannot be shared — the whole point of Private Mode is that the content does not reach us.

3.8 Memory (opt-in)

Memory is off by default. Your conversations are stored in your own browser and are not sent to us for storage. If you switch memory on in Settings, we store short factual statements — either ones you type yourself, or ones the assistant saves when you tell it something it judges durable, such as a standing preference or a subject you are researching. We do not store the conversations those facts came from.

Everything saved is listed back to you in Settings, in full and in plain text. You can delete any entry individually or erase all of them at once. Switching memory off stops us reading or writing memories immediately but does not delete what is already stored — use “forget everything” for that. Deleting your account removes all of it.

3.9 Diagnostic data

We collect basic server logs (IP address, request path, status code, user agent, timestamp) for security, abuse prevention, and debugging. These logs are retained for up to 90 days.

3.10 Cookies and local storage

Clerk, our sign-in provider, sets cookies that keep you signed in. When you pay, you are sent to Stripe’s own checkout page, and Stripe sets its cookies there, on its own site. Stripe’s payment script also loads on our pricing page and inside the app, so that a checkout can start, and it sets its own fraud-prevention cookies on our site as well. Your browser’s storage keeps your chat history on your device, plus a few settings, such as whether you have already seen the tour. The cookies we set ourselves, to measure where visitors come from, are described next.

Where visitors come from (first party). If you arrive from a creator’s referral link, from one of our ads, from a link we send you in an Instagram message, or from any other link to us that carries campaign tags, we store which link, ad or post brought you, in cookies we set ourselves: inf_ref, inf_ref_at and inf_ref_hit for referrals, and ad_touch, ad_touch_ft and ad_hit for everything else. The referral cookies last 60 days and the others 90 days, except inf_ref_hit and ad_hit, which last ten minutes.

A link we send you in an Instagram message, for example after you comment on one of our posts, is evilasf.com/t/ followed by a number. That number identifies the Instagram post the message was sent about, not you. Every tap on the link is recorded, including a repeat tap, and so is the app loading the page in advance.

When you arrive through one of these links, we store a visit record: which link, ad or post it was, the page you landed on, the time, and a scrambled (hashed) form of your IP address. For every link except a creator’s referral link, the record also notes the country your connection comes from and whether the link opened inside an app’s built-in browser. That record does not name any account.

We use the referral cookies to pay creators what they are owed, and the others to count which ads and posts lead to sign-ups and payments. If you arrived from an ad, a message link or another tagged link and then create an account in the same browser, we note on your account which one brought you and when you arrived (the first and the latest, if there was more than one). That note is deleted with your account. The cookies themselves stay in your browser until they expire or you clear them.

What we do not do. We do not use Google Analytics, the Meta Pixel, the TikTok Pixel, or any other advertising tracker. The only outside analytics service we use is PostHog, on the public pages listed in 3.11 below and only in the way described there. The chat app does not start PostHog, and it loads no advertising code. The ad and message-link records described above stay on our own servers: we do not send your sign-ups, your payments, your chats or any identifier back to TikTok, Meta or any other advertising network, and we do not track you across other websites.

3.11 Website analytics (PostHog)

On some of our public pages we use PostHog, a website analytics service, to see how those pages are read: which links and posts bring people to them, how long people stay, and how far down they scroll. We use PostHog’s cloud in the European Union, at eu.i.posthog.com.

Where it runs. Only on these pages of evilasf.com: the home page, pricing, the coverage page, our philosophy page, the uncensored AI page, the surveillance pages, the Flock page, the blog, this privacy policy, the terms of service, the API terms, and the main affiliate program page. No other page loads it, and it records nothing from any other page. That includes the chat app, community, your account and billing pages, sign-in and sign-up, shared conversations, the document archive and the cipher pages, the affiliate dashboard, handbook and terms, and the form for reporting intimate images. A link from one of the pages above to any of these opens it as a fresh page, so PostHog does not come along.

What it records. Each time you open one of the pages above, and when you leave it, PostHog receives:

• The page’s address, cut down to the page itself and its campaign tags (the utm_ tags that say which link brought you). Anything else in the address is removed before it is sent.
• The website that sent you, by its domain name only, never the page you were on there. When you came from another of our own pages, this is left blank.
• How long you stayed on each of the pages above, and how far down you scrolled.
• Your browser and its version, your operating system and its version, whether you are on a phone, tablet or computer, and the size of your screen and browser window.
• The technical details PostHog needs to file each event: the time, random identifiers for the visit and the page, our PostHog project key, the name and version of PostHog’s code, and a flag telling it not to build a profile.

That is everything our code sends. If you came from a link we sent you in an Instagram message (see 3.10), the campaign tags include the number of the Instagram post the message was about, so PostHog sees that number too. It identifies the post, not you.

What it does not do. PostHog sets no cookies and saves nothing in your browser’s storage. Its identifier for you is random and lasts only as long as the page stays open. Moving from one of the pages above to another usually keeps the same one, but reloading the page, or coming back later, starts a new one. So PostHog does not connect one visit to the next. It is never told who you are, it builds no profile of you, and it does not link any visit to your account. It does not make a screen recording or replay of your visit, and it does not capture your clicks or your typing. It makes no heatmaps, shows no surveys, and fetches no settings that could switch any of that on. Like any website your browser connects to, PostHog sees your IP address when an event arrives. It is set to discard it rather than keep it, and to work out no location from it.

Do Not Track and Global Privacy Control. If your browser sends either signal, PostHog is not loaded at all, and nothing is sent to it.

4. How we use your information

• Operate the service: Route your messages to AI providers, return responses, enforce plan limits.
• Billing: Process subscriptions, handle upgrades/downgrades, manage refunds when applicable.
• Security and abuse prevention: Detect and block fraudulent accounts, abusive patterns, or violations of our Acceptable Use Policy.
• Communication: Respond to support requests, send transactional emails (billing receipts, subscription changes, service announcements).
• Legal compliance: Respond to lawful requests from courts or regulators where required by law.

We do not use your content to train AI models. We do not sell your personal information. We do not share your content with advertisers.

5. Third-party processors

We rely on the following third parties to run Evil ASF. Each has their own privacy practices and certifications:

• Clerk — authentication and session management
• Stripe — payment processing, billing, subscription management
• Third-party AI inference providers — chat completions, voice, and vision processing
• Railway — application hosting and database
• Firecrawl — URL scraping (when you enable the web-scraping feature)
• PostHog — website analytics on our public marketing pages, hosted in the European Union (see 3.11)

When you use features like web search or voice, content is transmitted to those services to be processed. We do not control their data practices beyond our contractual agreements with them.

6. Data retention

• Account data: Retained for as long as your account is active. You can delete your account yourself at any time under Settings → Account; this removes your account data immediately rather than on a request queue, and cancels any active subscription at the same time.
• Payment records: Retained as required by applicable tax and accounting law (typically 7 years).
• Usage logs: Retained for 90 days.
• Chat content (standard mode): Stored locally in your browser. You can clear it anytime via your browser's storage settings or by clicking "Clear all data" in the app.
• Chat content (Private Mode): Not retained server-side. Visible only to you in your browser. Cannot be shared as a link.
• Shared chat links: A snapshot of the conversation you chose to share, stored on our servers and deleted automatically 30 days after you created the link. You can revoke a link sooner from Settings, which deletes the snapshot immediately. Deleting your account deletes all of them.
• Community messages: Retained for 12 months, then deleted. Messages that are subject to an unresolved report, or that we are required to preserve for a legal obligation, are kept until that is concluded. Deleting your account removes your handle and your membership of any room; it does not delete messages you have already sent to other people, which remain part of those conversations.

7. Your rights

Depending on your jurisdiction, you may have the right to:

• Access — request a copy of the personal data we hold about you.
• Correct — ask us to fix inaccurate data.
• Delete — delete your account and its data yourself from Settings → Account, or ask us to. Either way we act subject to legal retention requirements (e.g. tax records held by our payment processor).
• Object — object to our processing of your data.
• Portability — receive your data in a portable format.
• Withdraw consent — where we rely on consent, you can withdraw it anytime.

To exercise these rights, email [email protected]. We will respond within 30 days.

8. Children

Evil ASF is not intended for users under 18. We do not knowingly collect personal data from children. If you believe a child has created an account, please contact us and we will delete the account.

9. International data transfers

Our services are hosted in the United States. If you access Evil ASF from outside the US, your data will be transferred to and processed in the US and potentially in other jurisdictions where our service providers operate. By using the service, you consent to this transfer.

10. Security

We use industry-standard safeguards including HTTPS/TLS for all data in transit, encrypted storage at rest for databases, and access controls on internal systems. Private Mode runs the model inside sealed, hardware-attested computing and keeps its content out of our logs and storage; it is not end-to-end encrypted (see section 3.5). However, no system is perfectly secure. If we become aware of a breach affecting your data, we will notify you within the time period required by applicable law.

11. California residents (CCPA/CPRA)

If you are a California resident, you have additional rights under the California Consumer Privacy Act including the right to know what personal information is collected, the right to delete personal information, the right to opt out of sale or sharing of personal information (we do not sell or share), and the right to non-discrimination for exercising these rights. To exercise any of these, contact us at the email above.

12. European residents (GDPR)

If you are in the European Economic Area, United Kingdom, or Switzerland, our legal bases for processing are: performance of contract (providing the service you signed up for), legitimate interests (security, abuse prevention), legal obligation (tax records), and consent (optional features). You have the right to lodge a complaint with your local data protection authority.

13. Changes to this policy

We may update this policy occasionally. Material changes will be announced on this page with an updated effective date, and for significant changes we will email registered users. Your continued use after a change constitutes acceptance.

14. Contact

Questions, requests, or concerns: [email protected]