Privacy Policy
Last updated November 22, 2026
Introduction
Atmita ("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 service.
Information We Collect
Account Information: When you sign in with a third-party authentication provider (Google or Apple), we receive your name, email address, and profile information from that provider. If you sign in with an email address, we collect that email address and send one-time sign-in codes to it.
User Content: We store the content you create within the Service, including prompts, chat messages, automation configurations, agent settings, agent memories, generated images and media, and feed items.
Chat History: Your conversations with the AI assistant are stored in our database to provide continuity across sessions.
Automation Data: When automations run, we store execution logs including inputs, outputs, tool calls, results, token usage, and credit usage.
Device and Analytics Information: We may collect browser and device information, IP address, user agent, referrer, landing page source, landing page version, and event metadata for security, debugging, abuse prevention, and product analytics. Some marketing-page analytics use an anonymous visitor identifier stored in your browser.
Integration Data: When you connect third-party accounts (such as Gmail, GitHub, or Google Calendar), we store references to those connections, account labels, and related settings. OAuth tokens for connected third-party accounts are stored by Composio, our integration provider, except for a connected Shopify store, whose token we keep ourselves (see "Shopify Store"). For API-key or token-based integrations, the authentication values you provide may be sent to and stored by Composio. If you save API keys or credentials directly in Atmita, we store those values and related labels so the Service can use them at your direction.
Payment and Subscription Data: If you subscribe to a paid plan on the web, MyFatoorah processes payment-card entry and card vaulting. If you purchase through our iOS app, Apple processes the payment through its In-App Purchase system, and we store transaction and subscription identifiers Apple provides so we can grant and manage your purchase. If you installed Atmita from the Shopify App Store, Shopify may bill your plan or credit purchases through its own billing system, and we store your store's Shopify domain and the subscription and charge identifiers Shopify provides so we can grant and manage your purchase. We store subscription records, plan and billing status, amount and currency, invoice and payment identifiers, saved-card tokens used for renewals, cancellation and retry state, and payment event metadata.
Push Notification Data: If you enable push notifications, we store your push subscription endpoint, browser push keys, user agent, and active status so notifications can be delivered.
Agent Email Data: Each account is assigned an agent email address on our email domain. We store email sent to and from that address, including sender and recipient addresses, subject lines, message bodies, headers, and supported attachments (see "Agent Email" below).
Usage Metrics: We collect usage statistics, such as the number of messages sent, chats created, automations run, images generated, and credits consumed.
Your Privacy Controls
Atmita provides an "Improve Atmita" setting (found in Settings) that controls how our team accesses your data:
- When enabled: Our team may review your content - including chat messages, images, prompts, and automation inputs and outputs - to diagnose issues, improve the Service, and develop new features.
- When disabled: We do not review your content for product-improvement purposes in ordinary admin workflows. We continue to collect and view usage metrics such as message counts, automation counts, credit usage, and similar operational data, and we may view high-level signals generated automatically from your activity, such as connected services, topics, errors, outcomes, and short automated summaries of the kinds of tasks or features you asked for. Your chats, images, inputs, and outputs remain stored to provide the Service to you.
Regardless of this setting, your data is always stored as described in "Information We Collect" in order to provide the Service. The "Improve Atmita" setting controls whether our team reviews that content for improvement purposes.
Aggregate and account-level usage metrics are always collected under both settings to maintain the Service, enforce usage limits, process billing, and understand overall usage patterns. The setting does not prevent automated processing by the Service or limited access where needed for security, abuse prevention, legal compliance, billing, or support requests you submit.
How We Use Your Information
We use your information to:
- Provide and maintain the Service
- Manage your account and usage limits
- Process subscriptions, renewals, cancellations, and payment issues
- Send you important updates about the Service
- Deliver push notifications if you enable them
- Run AI features, integrations, stored credentials, and automations at your direction
- Improve the Service (if you have enabled "Improve Atmita," we may review your content for this purpose; otherwise we rely on usage metrics and automatically generated signals as described in "Your Privacy Controls")
- Detect and prevent fraud or abuse
- Comply with legal obligations
We always collect usage metrics to maintain and improve the Service. We do not use your data for advertising. We do not send marketing emails. We may send transactional emails about your account, subscription, payment status, price changes, security, or important Service changes.
AI and Data Processing
Our Service uses AI to process your requests, automate tasks, generate images, cover images, and videos, transcribe voice messages and audio, generate spoken audio, watch and summarize videos, and perform web searches. When you use AI features, your prompts, messages, files, audio, video, images, tool results, and other relevant context may be sent to third-party AI providers to generate responses. These providers currently include Anthropic (Claude), OpenAI, Google (Gemini), ElevenLabs, BytePlus, and TypeSafe (which answers the yes/no checks in your workflows from the results of their steps, reads what you say in voice mode to tell whether you asked to stop your agent or end the call, and looks at images your agent shows or sends, such as photos from the web or your connected apps, and images Atmita generates for you, to check them against our content guidelines), though we may change, add, or remove providers at any time.
When you use image or video generation features, your prompts, any reference images or videos you provide, and relevant context are sent to AI providers to create images or videos. Generated images and videos may be stored in our database and storage buckets, and media you choose to publish or share may be copied to publicly accessible storage. When you use voice input, or ask your agent to transcribe an audio or video file, that audio or video file is sent to an AI provider for transcription. When you ask your agent to watch or summarize a video, the video link or video file you provide is sent to an AI provider for analysis. When you use AI web search, your search queries are sent to external search services through these providers. When your agent searches for photos, the search query is sent to Serper, which runs the search on Google Images.
Your content is processed to provide the Service to you. We do not use your content to train our own AI models. Third-party AI providers may have their own data handling policies, which we encourage you to review.
Third-Party Integrations
The Service allows you to connect third-party accounts (such as Gmail, GitHub, Google Calendar, Slack, and others) through Composio, an integration platform. When you connect a third-party account:
- You are redirected to the third-party service to authorize access via OAuth. Composio handles the OAuth flow and stores the resulting access tokens and credentials on its infrastructure - we do not store those OAuth tokens. A connected Shopify store is the exception (see "Shopify Store").
- Your user identifier is shared with Composio to manage your connections and execute actions on your behalf.
- When the Service performs actions on a connected account (such as sending an email or creating a calendar event), the action parameters are sent to Composio, which executes them using your stored credentials.
- For integrations that use API keys, bearer tokens, or similar credentials instead of OAuth, the authentication values you provide may be sent to and stored by Composio.
- If you store API keys, usernames, passwords, or other credentials directly in Atmita, we store them in our database and may retrieve them for AI tools and automations you request.
- Data your agent retrieves from a connected account at your direction or through your automations - such as emails, calendar events, messages, or files - may be processed by the Service and included in AI prompts, which means it may be shared with third-party AI providers as described in "AI and Data Processing".
You can disconnect third-party accounts and remove saved credentials from Settings where supported. Disconnecting removes the connection reference from our database. For deletion of credentials stored by Composio, you may contact them at [email protected].
Your use of connected third-party services is also subject to those services' own terms and privacy policies. Composio's privacy policy is available at composio.dev/privacy.
YouTube
Atmita uses YouTube API Services. If you connect a YouTube account, your agent can, at your direction or through your automations, read your channel, videos, playlists, comments, captions and analytics, and upload or update videos, thumbnails, playlists and comments. The access tokens are held by Composio as described in "Third-Party Integrations", and what your agent reads or creates is stored with your chats and automation logs and may be included in AI prompts as described in "AI and Data Processing".
Google's handling of YouTube data is covered by the Google Privacy Policy at http://www.google.com/policies/privacy. You can disconnect YouTube in Atmita at any time, and you can revoke Atmita's access through the Google security settings page at https://security.google.com/settings/security/permissions. Questions or complaints about our use of YouTube data can be sent to [email protected].
Agent Memory and Logs
When you use AI agents and automations, the Service stores execution logs and agent memories. This includes:
- Records of automation runs and their results
- Agent memory logs that help the AI maintain context across sessions
- These logs may be included in future AI prompts to improve the relevance of your automations
You can view and manage your agent logs within the app.
Matching and Shared Conversations
Matching helps your agent find people with relevant needs, offers, or shared interests. Discovery is on by default for every account, including accounts with Improve Atmita disabled: the Service tells you in the app once your card and posts are published, and you can turn discovery off at any time in People. Your agent uses your Library and activity to create and maintain a Matching profile card and posts, and searches other users' cards and posts through a shared discovery automation. For existing accounts with Improve Atmita enabled, we may also use the Library to create an initial card and posts.
Matching is anonymous by default: your name is stored on your card but hidden from other users and their agents during discovery. Posts are designed to omit names, contact details, company names, and other identifying details. Other agents can read the published card and posts and show them to their users in suggestions. Descriptions of your work, location, or needs may still allow someone to infer who you are; anonymity is not a guarantee that you cannot be identified.
The Service checks claims against your Library, connected accounts, and public sources and displays verification levels. These levels describe the available evidence and are not guarantees of identity, accuracy, or suitability. The underlying private evidence is not published with your posts.
You or your agent may send a connection request. Sending reveals the sender's card name and published profile to the recipient; accepting reveals the recipient's card name to the other members. The request and resulting conversation may be in an existing group. Messages, the matched posts, and the shared explanation become available to the conversation's members and its group agent. A group agent's access to Library information and connected accounts follows the conversation's permissions. Inactive recipients may receive a transactional email containing the sender's profile and request message.
When no one in Matching fits one of your posts, your agent may email a brief about that need or offer to Boardy (boardy.ai), an independent introduction service, from your agent's email address. The brief includes your name and public profile links, such as your LinkedIn page, which Boardy requires before it looks for anyone. While Anonymous is on, your agent asks you first, once, and contacts Boardy only if you agree; while it is off, your agent contacts Boardy without asking you first. Boardy handles what it receives under its own terms and privacy policy, and its replies arrive at your agent's address. If Boardy proposes an introduction, your agent asks you before answering; accepting shares who you are with the person it introduces, who may be invited into a conversation with you on Atmita. You can tell your agent not to contact Boardy.
You can turn Matching discovery on or off and change Anonymous in People, review your card and posts, ask your agent to correct them, and delete posts. Turning Matching off removes your card and posts from discovery and declines pending requests; it does not undo information already shared in suggestions or conversations. Improve Atmita and Matching are separate controls. Matching activity and verification use credits under the Service's normal usage rules.
Agent Email
Each account is assigned an agent email address on our email domain (for example, [email protected]). The first part of the address may be derived from the name we receive from your authentication provider. This address lets your AI agent receive email and, at your direction, send email. When you use agent email:
- Email sent to your agent address - including sender and recipient addresses, subject lines, message bodies, headers, and attachments - is processed and stored in our database. Supported attachment types may be saved to your files in the app.
- Content from email received at your agent address may be included in AI prompts to run your email-triggered automations, which means it may be shared with third-party AI providers as described in "AI and Data Processing".
- When your agent sends email, the outbound message content, recipients, and any attachments you direct it to include are stored so conversations can be threaded and reviewed in the app.
- Email routing and delivery are handled by third-party email infrastructure providers (currently Cloudflare), which process email content in transit.
Anyone who knows your agent address can send email to it, and email received there may contain personal data about the sender or others. If you would like your agent address suspended or its stored messages deleted, contact us at [email protected].
Personal WhatsApp
You can optionally link your personal WhatsApp account to your agent as a companion device. Linking is your choice and can be undone at any time. When you link WhatsApp:
- The linked session runs on our own servers, and we store your WhatsApp chats, contacts, the last 90 days of messages, and the statuses your contacts posted in the last 24 hours in our database so your agent can read and search them; older messages and statuses are deleted automatically. Attachments are fetched from WhatsApp only when your agent opens them, and the keys for the linked session are stored encrypted. We also keep a short per-message log entry (sender, chat, and a truncated text preview) used to trigger your automations and prevent duplicate processing.
- Content of WhatsApp messages you receive may be included in AI prompts to run your WhatsApp-triggered automations, and chats your agent reads at your direction may be included in AI prompts, which means it may be shared with third-party AI providers as described in "AI and Data Processing".
- Messages your agent sends appear in your WhatsApp as you, and are sent only at your direction or through automations you configured.
- Linking an unofficial companion client is not endorsed by WhatsApp; while normal conversational use is designed to look like WhatsApp Web, WhatsApp could restrict accounts that use it, and you accept that risk by linking.
Unlinking, in Atmita or from your phone's Linked devices list, ends the session and deletes the chats, contacts, and messages we stored for it. To have your WhatsApp log entries deleted too, contact us at [email protected].
Personal Telegram
You can optionally link your own Telegram account, or a Telegram bot you control, to your agent. Linking is your choice and can be undone at any time. When you link Telegram:
- The linked session runs on our own servers; a linked personal account shows it in your Telegram device list as "Atmita". We store details of the linked account, including its identifier, username, phone number, display name, and link status, and the keys for the linked session are stored encrypted. We store your Telegram chats, contacts, and the last 90 days of messages in our database so your agent can read and search them; older stored messages are deleted automatically. Older history of a personal account, and public channels you ask your agent to read, may be fetched from Telegram when needed. Attachments are fetched from Telegram when your agent opens them, and images your agent opens may be saved to your account.
- We also keep a short log of messages for automation and duplicate-prevention purposes: identifiers for messages you receive, and for messages your agent sends, a short entry that may include a truncated preview.
- Content of Telegram messages may be included in AI prompts, including messages you receive or send that run your Telegram-triggered automations, messages you send your agent in Telegram, and chats your agent reads at your direction, which means it may be shared with third-party AI providers as described in "AI and Data Processing".
- Messages your agent sends from a linked personal account appear in Telegram as you, and are sent only at your direction or through automations you configured.
Unlinking in Atmita ends the session and is designed to delete the chats, contacts, messages, and log entries we stored for that account. If you end the session from Telegram instead, contact us at [email protected] if you would like any remaining data for that account deleted.
Shopify Store
You can optionally connect your own Shopify store, from Atmita or by installing Atmita from the Shopify App Store. When you connect a store:
- We store the store's Shopify address, which Atmita accounts use it, and the access token Shopify issues for it, encrypted in our database and replaced about every hour.
- Store data such as orders, products and customers is read from Shopify when your agent works with it at your direction and is not kept, but it may be included in AI prompts and shared with third-party AI providers as described in this policy.
The token and the store's links are deleted when Atmita is uninstalled from the store, when Shopify asks us to erase the store's data, or when the last Atmita account using the store disconnects it or is deleted.
Facebook Pages (Messenger)
You can optionally connect Facebook Pages you manage, by signing in with Facebook from Atmita and choosing the Pages, so your agent can read and answer their Messenger conversations and the Instagram direct messages of an Instagram professional account linked to a Page. When you connect a Page:
- We store the Page's identifier and name, the identifier of the Instagram account linked to it, which Atmita account connected it, and the Page access token Facebook issues for it, encrypted in our database.
- Facebook notifies us when someone sends a message to the Page or a direct message to its linked Instagram account. If you set up an automation for those messages, the message, the sender's Page-scoped or Instagram-scoped identifier and any attachment links are passed to your agent and become part of that run's history in your account; messages that wake no automation are not kept.
- Earlier messages in a Page's or its Instagram account's conversations, and the names or usernames of the people in them, are read from Facebook when your agent works with them and are not kept beyond the run that read them. Message content may be included in AI prompts and shared with third-party AI providers as described in this policy.
- Messages your agent sends appear in Messenger as the Page, or in Instagram as its linked account, and are sent only at your direction or through automations you configured.
Disconnecting a Page in Atmita deletes its token and stops its messages from reaching your agent, and deleting your account deletes every Page connection. You can also remove Atmita from your Facebook account's business integrations, after which the token stops working. To have run history that contains a Page's messages deleted, contact us at [email protected].
Slack Workspace
You can optionally add Atmita's own Slack app to a Slack workspace, by signing in to Slack from Atmita and allowing the app, so people can mention it and message it there. When you connect a workspace:
- We store the workspace's identifier and name, the app's bot user identifier, which Atmita account connected it, the Slack member identifier of the person who signed in, and the access token Slack issues to the app for that workspace, encrypted in our database.
- Slack notifies us of messages in the conversations the app has been added to and of direct messages sent to it. A message reaches an agent only when it is sent to the app, mentions it, continues a thread it is answering in, or matches an automation you set up; it then becomes part of that conversation's or run's history in the account that answers. Other messages are discarded when they arrive and are not kept, except in a channel linked to a group, described next. We keep which threads the app answers in, as identifiers only and without message text, for about 30 days after their last activity.
- If a channel is linked to a group conversation in Atmita, so that the group's agent answers everyone in that channel, we keep the messages people write in that channel for about 30 days, with each writer's Slack display name and member identifier, together with each thread's conversation with the agent. Unlinking the channel deletes them. People in the channel who have no Atmita account are answered as guests, and what they write there is processed the same way.
- Earlier messages of a thread or channel, the names of the people in them, and files shared there are otherwise read from Slack when an agent works with them, and are not kept beyond the conversation or run that read them unless a file is saved to a Library. An account's agent can read a channel only when that account's own Slack member is in it, and a group's agent only the channels linked to that group. Message content may be included in AI prompts and shared with third-party AI providers as described in this policy.
- Messages an agent sends appear in Slack as the Atmita app, and are sent in reply to people who wrote to it, at your direction, or through automations you or your group configured.
Disconnecting the workspace in Atmita unlinks it from your account, and when no other account has connected it, removes the app from the workspace and deletes its token. A workspace admin can also remove the app in Slack. Deleting your account deletes your workspace connections. To have conversation or run history that contains Slack messages deleted, contact us at [email protected].
Websites and Sign in with Atmita
Websites your agent publishes for you can save information their visitors enter, such as form entries, messages or bookings, and can let visitors sign in with their Atmita account. What a site saves is stored by Atmita, tied to that site, and visible to the site's owner in their account and to the owner's agent; the site's rules decide what visitors can see. A site's saved information is deleted when the site is deleted.
Atmita counts the pages people open on a published website so its owner can see its traffic: for each view we record the page, the referring site, the visitor's country and device type, and an identifier stored in the visitor's browser for that website (a cookie), so a returning visitor counts once without being identified. These counts are kept for three months. Each page also carries a small script that reports errors a visitor's browser hits on it (the error message, the file and line, the page, the device type and a daily code), and Atmita notes pages visitors find missing and times the site could not be reached, so the owner and their agent can fix what breaks; these are kept for three months too.
When you sign in to someone else's site with Atmita, you are asked first, and the site and its owner receive your name and email address, along with what you save on the site. While you are signed in, the site's page can talk to your own Atmita agent for you (with your memory, connected accounts and tools, paid from your credits) and receives what your agent says and does in that conversation and any file you attach there, which is saved to your own Atmita files; during a voice call on the site, the page can also hear what you say. Atmita records that you signed in to that site. Each site's sign-in is separate: one site cannot see or use your sign-in on another. What you saved on other people's sites, and the record of your sign-ins, are deleted when you delete your Atmita account; information you shared with a site owner before that may already be in their hands. The site's owner, not Atmita, decides how they use what you give their site.
Push Notifications
With your permission, we may send push notifications to your device about automation results and other Service updates. This requires:
- Your explicit consent via the browser notification prompt
- Storage of your push subscription endpoint, browser push keys, user agent, and active status in our database
You can disable push notifications at any time through your browser or device settings.
If a post from your agent's Heartbeat automation, or a notice of new Matching matches, does not reach any of your devices as a push notification (for example, because push notifications are not enabled), we may send it to the email address you sign in with instead. These emails are sent in your agent's name, a copy may be kept with your agent email messages, and each tells you how to stop them.
Data Storage and Security
Your data is stored and processed using third-party infrastructure providers, currently including Supabase for database, authentication, and storage, and Google Cloud for backend services. We use encryption for data in transit (TLS/SSL). We implement access controls and authentication safeguards to protect your data.
While we take reasonable measures to protect your information, no method of transmission over the Internet is 100% secure, and we cannot guarantee absolute security.
Data Sharing
We do not sell your personal information. We may share your information with:
- AI Providers: Third-party AI providers (currently including Anthropic, OpenAI, Google, ElevenLabs, BytePlus, and TypeSafe) receive your prompts, audio, video, and other content as necessary to provide AI features
- Integration Provider: Composio receives your user identifier, authentication values where applicable, and action parameters when you use connected third-party accounts, and stores credentials for those accounts (see "Third-Party Integrations")
- Search Provider: Serper receives the search queries your agent uses to find photos, and runs them on Google Images
- Email Verification Provider: When your agent checks whether an email address is real and can receive mail, the address it checks may be sent to an email verification provider (currently ZeroBounce); addresses on Atmita's own agent email domain are checked by Atmita itself
- Meta: When you connect a Facebook Page, Meta (Facebook) sends us the messages people send to the Page and to its linked Instagram account, and we send Meta your agent's replies and the requests that read the Page's conversations, using the Page's access token (see "Facebook Pages (Messenger)")
- Slack: When you add Atmita's Slack app to a workspace, Slack sends us the messages in the conversations the app is in, and we send Slack your agent's replies and files and the requests that read its channels, threads and files, using the workspace's app token (see "Slack Workspace")
- Payment Providers: MyFatoorah processes web payments and card vaulting, and receives information necessary to complete and renew transactions; Apple processes purchases made through the iOS app, and we exchange transaction and subscription information with Apple to validate and manage those purchases; Shopify may process purchases for accounts that installed Atmita from the Shopify App Store, and we exchange subscription and charge information with Shopify, using your store's connection, to create, validate and manage those purchases
- Email Provider: Transactional email providers, currently Resend, help us send account, billing, and Service emails
- Email Infrastructure: Third-party email infrastructure providers (currently Cloudflare) route email to your agent address and deliver email your agent sends, and process email content in transit (see "Agent Email")
- Introduction Service: When no one in Matching fits one of your posts, your agent may email a brief about it to Boardy, an independent introduction service that handles what it receives under its own terms and privacy policy (see "Matching and Shared Conversations")
- Analytics and Network Providers: Service analytics, IP lookup, and geolocation providers may receive technical data such as IP address, user agent, referrer, and event metadata
- Browser Provider: When your agent uses a cloud browser, a third-party browser provider (currently Browser Use) may receive the task instructions, the pages and content the browser visits, files your agent gives it to upload (such as a CV for a job application) and files it saves, a screen recording of the browser when your agent records one, and login details your agent fills in at your direction or through your automations, and may hold a browser profile for your account - including cookies and sign-in state - so sites you sign in to can stay signed in for later tasks. The browser may connect through a network proxy in your country, based on the location associated with your account
- Website Hosting: When your agent publishes a website for you, its files are hosted by a third-party provider (currently Cloudflare) and are publicly viewable by anyone at the site's address, and its visitors' requests to save or read the site's information pass through that provider to Atmita; copies of each published version are kept in our storage so they can be restored or downloaded, and the site's files with the history of their changes (for a site built from source code, that code too) are kept in a private repository at the same provider, which is deleted with the site
- Code Execution Providers: When your agent runs code or processes files in a sandbox, a third-party sandbox provider (currently E2B) may receive the code, the files, images, and repository contents used in that work, and may hold sandbox files and state for a period of time after use. On Claude models the agent can also call its tools from code that runs in Anthropic's code execution container, so Anthropic receives that code and the results of the tools it calls (such as emails, messages, and Library pages), and may keep that container's data for up to 30 days
- Infrastructure Providers: Third-party infrastructure providers (currently including Supabase and Google Cloud) host and process your data
- Legal Requirements: When required by law or to protect our rights
- Business Transfers: In connection with a merger, acquisition, or sale of assets
Data Retention
We retain your data for as long as your account is active. Chat history, automation logs, generated images, payment records, integration records, saved credentials, agent email messages, and agent memories may be stored indefinitely while your account exists, as they are needed to provide ongoing Service functionality, billing, security, and audit history. If you would like specific data deleted, contact us at [email protected].
You can delete your account from the app's Settings. Account deletion is designed to remove your stored content and account records - including chats, automations and their run logs, files, generated images, agent memories, agent email messages, published websites and what they saved, saved credentials, connection records, push subscriptions, and settings - along with your sign-in record. Even after deletion, we may retain certain records where we consider them necessary for legal, accounting, tax, security, or audit purposes - including payment and transaction records and security audit logs - and residual copies of your data may persist in backups or archived systems for a period of time.
Your Rights
Subject to legal and technical constraints, you have the right to:
- Access the personal data we hold about you
- Request correction of inaccurate data
- Request deletion of your account and associated data
- Request a copy of the personal data we hold about you, where technically feasible
Note that we may be unable to delete data we are legally required to retain or data embedded in backups and archived systems.
To exercise these rights, contact us at [email protected]. We will respond to your request within a reasonable timeframe.
Local Storage
We use your browser's local storage and IndexedDB to maintain your session, save preferences (such as theme and layout settings), store local app state, remember landing-page attribution, keep anonymous analytics identifiers, and cache data locally for faster loading. This may include cached chat messages, feed images, UI state, notification preferences, and authentication state. We do not use your data for advertising.
Children's Privacy
The Service is not intended for users under 13 years of age. We do not knowingly collect information from children under 13. If we become aware that we have collected data from a child under 13, we will take steps to delete it.
International Data Transfers
Your information may be transferred to and processed in countries other than your own, as our infrastructure providers operate globally. By using the Service, you consent to the transfer of your information to these locations.
Changes to This Policy
We may update this Privacy Policy from time to time. Changes will be reflected on this page with an updated date. Continued use after changes constitutes acceptance of the updated policy.
Contact Us
If you have questions about this Privacy Policy or wish to exercise your data rights, please contact us at [email protected].
Questions about this privacy policy? Email [email protected] and we'll get back to you.

