← Back to altr.bio

Privacy Policy

Last updated October 17, 2026

What we collect, why we collect it, and who else sees it. Written to be read, not to be survived.

1. Who handles your data

BRND Creative Inc., 131 Continental Dr, Suite 305, Newark, DE 19713, United States, is the controller of the personal data described here. Write to support@brnd.company about anything on this page.

2. What we collect

  • Account: your email address, your altr.bio address, and your sign-in method. If you sign in with Google, we receive from Google your Google account ID, email address, name, and whether Google has verified that email address. If you sign in with Apple in the ALTR iOS app, we receive from Apple your Apple user ID, the email address Apple shares with us (which may be a private relay address from Apple's Hide My Email), and whether Apple has verified it; the first time you sign in, your device may also pass on the name you choose to share, which we use as your display name. Your device also passes us a one-time code from Apple, which we may exchange for an Apple refresh token. We keep that token only in encrypted form and use it for one thing: to ask Apple to cancel ALTR's Sign in with Apple access when you delete your account (section 8).
  • Source material: the public posts, captions, and comments from the accounts you connect, so your ALTR can learn your voice. We fetch these through Apify from the platform you named.
  • Connected accounts: a creator can prove that a YouTube, X or TikTok account is theirs by connecting it through the platform's official sign-in. This official sign-in verification is rolling out: we offer it only for the platforms where it is available, and you can always prove ownership with a profile code instead. You approve access on the platform's own page, and the platform gives us a one-time access token. We use it once to read the account's identity (the YouTube channel, X user or TikTok user) and take only its handle from what the platform returns. For TikTok we use TikTok Login Kit and ask only for the user.info.basic and user.info.profile scopes; user.info.profile is the one that returns the handle. We then drop the token right away and do not store it: for X and TikTok we send it back to the platform to cancel it (if that request fails, an X token expires on its own within two hours and a TikTok token within 24 hours), and for YouTube we do not cancel it, because that would also cancel your Google sign-in to ALTR if you use one, so it simply expires on its own, within about an hour. We do not keep access or refresh tokens. We do not read your videos or posts through the connection, so nothing that is not public is read. X's approval page asks for permission to read posts because its account-identity endpoint requires it; we call only that endpoint; the source material your ALTR learns from is still collected through Apify from public posts only. What we keep is the verification itself: the platform, the handle and when it was verified. Connecting an Instagram account is not turned on; if we turn it on, we will update this policy before doing so.
  • Conversations: the messages fans send to an ALTR and the replies it writes. Creators see numbers for each fan under a fan number that only works inside their ALTR — credits spent, messages sent, gifts, and when the fan is active. They never see the messages, the fan’s name, or a summary of one fan.
  • Money: gift and message records, your balance, and the last four digits and brand of a card. Stripe holds the full card number — we never receive it.
  • Payouts: payouts to creators, the bank account details they need, and identity and tax checks are not turned on. If we turn them on, we will update this policy before doing so.
  • Technical: your browser's user agent and the country of your connection, kept with each sign-in (so you can see and sign out your devices); your browser's user agent, kept with your acceptance of the service agreement; a hashed version of your IP address, kept with your acceptance of terms and with reports filed while signed out; and the country (in the US, the state) of your connection, checked on each request to apply regional rules.
  • Mobile app: if you use the ALTR app for iOS or Android, the app keeps your sign-in token in your device's secure storage and deletes it when you sign out. With each request our servers see the IP address of your connection and the user agent your device sends, and we keep that user agent with each sign-in, as described under Technical. The app does not ask for access to your camera, microphone, photos, contacts or location. Push notifications are not turned on: the app does not ask for permission to send them and keeps no push token. If we turn them on, we will update this policy before doing so. Purchases through the App Store or Google Play are not turned on in the app.
  • Analytics: your IP address and the approximate location derived from it, device, browser and network details, the screens you visit, and how you use the service. Section 4 lists every item.
  • Support: what you write to us when you ask for help or file a report.

3. Why we use it

We do not sell your personal data, and we do not use your conversations to train our own models.

  • To run the service you asked for — building your ALTR, letting fans talk to it, showing your page.
  • To confirm that a YouTube, X or TikTok account you connect is yours (section 2).
  • To take payments.
  • To keep the place safe: filtering messages, checking age signals, screening fans' messages for signs of suicide or self-harm risk, threats of violence, or a user under 18 (section 6), acting on reports, catching fraud.
  • To fix what breaks, and to understand which parts of the product are used, on which devices and from which regions (section 4).
  • To meet legal obligations, including tax reporting and answering lawful requests.

4. Service analytics and transfer abroad

To analyze and improve the service, we collect the information below and transfer it to Mixpanel, Inc. in the United States. This collection and transfer are part of the Terms and this Privacy Policy, which you agree to when you sign up: by signing up you agree to them. They are not a separate option you turn on or off. Visits from people who are not signed in are collected the same way, under an anonymous device identifier.

  • What we collect: IP address and the approximate location derived from it (country, region, city); an anonymous device identifier stored in your browser; device and browser details: user agent, browser and operating system name and version, platform and CPU architecture and bitness, device model and maker, screen and window size, pixel ratio, color depth, touch support, CPU cores, memory class, languages, time zone and UTC offset, light or dark color scheme, and app or browser display mode; network details: connection type, estimated speed and latency, and data saver mode; the address of the screens you visit, including the query and public handles and slugs (one-time tokens and identifiers are masked), the referring page and referring domain, and campaign parameters (UTM); your in-app actions and usage records (service events such as signup method, chats and sessions started, the model used, content rating and role); your account ID (when signed in).
  • What we do not collect: GPS or precise coordinates, hardware serial numbers, MAC or IMEI, advertising IDs, or message text.
  • In the ALTR mobile app: the app itself sends nothing to Mixpanel and stores no analytics identifier on your device. Our servers send Mixpanel the service events from your use of the app, with the IP address of your connection and the approximate location derived from it, the user agent your device sends with the app's requests, and your account ID (when signed in). The device, browser and network details above that a browser reports are not collected from the app.
  • How: Generated and collected automatically by your browser and our servers while you use the service.
  • Why: Service analytics and improvement: understanding which screens and features are used, on which devices and from which regions, so we can fix problems and improve ALTR.
  • Legal basis: For members, the Terms and this Privacy Policy agreed to at signup; that agreement includes the transfer abroad below (PIPA Article 28-8). Visitors who are not signed in are informed of this collection and transfer through this published Privacy Policy.
  • Transfer abroad: Recipient: Mixpanel, Inc., our analytics provider (contact: compliance@mixpanel.com). Country: the United States (Mixpanel US data center). When and how: each time you use the service, over encrypted internet connections (HTTPS). Items: the items above. Purpose: the purpose above. Retention: 2 years from the event date, then deleted automatically.
  • What ALTR keeps itself: Accounts that turned on analytics under the earlier optional setting, which was removed on October 11, 2026, still have that choice and their latest device and IP details in ALTR's own database. These are cleared when the account is deleted; only the time of the choice remains on record.
  • Withdrawing an earlier choice: Accounts that turned on analytics under that earlier optional setting can still withdraw that choice by writing to support@brnd.company; the in-app control was removed. When we receive the withdrawal, we stop updating the account's analytics profile at Mixpanel immediately, except to record the withdrawal itself, and we delete that profile after our team reviews and confirms the request. If you delete your account instead, the profile is deleted right away, without that review.
  • How long: Records sent to Mixpanel are kept for 2 years from the event date and then deleted automatically. To have them deleted sooner, contact us through the Help center (altr.bio/s/help) or at support@brnd.company.
  • How to refuse: Service analytics are part of using the service and cannot be switched off on their own; collection stops when you delete your account. A request to suspend processing sent to support@brnd.company is handled as the law requires; because analytics are part of the service, it is carried out by deleting the account. You can also ask us to delete records already sent to Mixpanel before the 2-year retention ends.

5. Who else sees it

We use these providers to run the service. Each one only gets what its job needs, and each is bound by contract to use it for nothing else.

  • Amazon Web Services — hosting, storage, and the Bedrock model service (United States and Asia Pacific). Bedrock also runs the AI that screens fan messages for safety (section 6), in the United States.
  • Amazon Web Services (Amazon Managed Service for Prometheus) — our operational metrics, so we can see whether the service is up, fast and working: counts and timings of requests by route pattern (such as /v1/play/sessions/:id) and status code, AI model token and cost totals by model, and counts of service outcomes such as chat turns, safety-check results, credit charges and failed emails. These are totals across everyone who uses the service; they carry no account ID, IP address, email address, device identifier, or anything you write. Stored in Amazon Web Services' Seoul region in Korea and kept for 90 days.
  • Anthropic — the language models that write ALTR replies and help creators build an ALTR. The fan's message, any photo attached to it and the conversation context are sent to it to produce a reply. We do not use other model providers for replies or media; if we turn one on, we will update this policy before doing so.
  • Slack (Slack Technologies) — internal alerts to our safety team when a fan message is flagged (section 6). The alert carries the kind of flag, a score and conversation and ALTR identifiers — never the message text. United States.
  • Resend — sending our email: account email, and the safety alerts to our safety team. United States.
  • Stripe — payments: saving a card, buying credits, receipts and refunds. Stripe Identity — identity verification when you turn on 19+ mode or publish adult content: you show a government ID and a selfie to Stripe, and we receive only whether it passed and your date of birth. Payouts and tax checks through Stripe are not turned on; if we turn them on, we will update this policy before doing so.
  • Apify — fetching the public posts from the social accounts you connect.
  • Google (YouTube) — when a creator connects a YouTube account: Google's sign-in grants access, and the YouTube API Services return the account's identity so we can confirm ownership (section 2). ALTR uses the YouTube API Services; Google's privacy policy is at http://www.google.com/policies/privacy. ALTR's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. United States.
  • X (X Corp.) — when a creator connects an X account: X's sign-in grants access, and the X API returns the account's identity so we can confirm ownership (section 2). United States.
  • TikTok (the TikTok company that operates TikTok in your region) — when a creator connects a TikTok account: TikTok Login Kit grants access with the user.info.basic and user.info.profile scopes, and the TikTok API returns the account's basic profile so we can confirm ownership (section 2). TikTok's privacy policy is at https://www.tiktok.com/legal/privacy-policy. United States.
  • Google (Google Sign-In) — when you sign in with Google: you approve the sign-in on Google's own page, and our servers send Google the one-time authorization code it returns, to receive the items in section 2. We keep no Google token from signing in. United States.
  • Apple (Apple Inc.) — when you sign in with Apple in the ALTR iOS app: our servers send Apple the one-time code from that sign-in to get a refresh token, and when you delete your account they send that refresh token back to Apple to cancel ALTR's Sign in with Apple access (sections 2, 7 and 8). United States.
  • Sentry — error reports, so we can fix crashes, and the feedback you send with the in-app feedback button: your message, any email or screenshot you add, your account ID and handle, the screen you were on, and your browser; your IP address is sent with the request, and Sentry may use it to derive an approximate location. United States.
  • GIPHY (Giphy, Inc.) — the GIFs you can search for and send in a chat. Our servers send it your search words; your browser loads the GIFs from its servers. United States.
  • Mixpanel — product analytics (section 4). United States.

6. What happens when an ALTR answers

When a fan sends a message, we send that message, recent conversation context, and the material that defines the persona to Anthropic (section 5). It returns a reply, which we filter and then show.

The reply is generated. It is not written by the creator, and we do not check it for truth.

Safety screening: in the same moment, in every chat, an AI model on Amazon Web Services' Bedrock service (United States; section 5) reads the fan's latest message, with the ALTR's previous reply as context, and estimates whether it shows suicidal thoughts or intent to self-harm, a threat of violence against a real person, or that the fan is under 18. Our own servers also check the message against a fixed list of phrases about self-harm, threats and age — always as a floor for self-harm, and in place of the model when it is unavailable; this check sends nothing anywhere. The safety model receives nothing else from the conversation, and the check does not change the reply. In creator-persona and 19+ chats, and for photos that contain text, a separate check on Bedrock also reads the conversation context and the ALTR's reply, or the text in the photo (section 10).

Why: to show crisis resources (such as 988 in the US or 109 in Korea) to a fan who may be at risk, to have the ALTR respond more carefully for a while after that, and to alert our safety team.

What we keep: when a message is flagged we record the kind of flag, the score, whether the AI model or the phrase list produced it, the time, and identifiers for the conversation, the message, the fan's account and the ALTR, plus whether our safety team was alerted and has reviewed it. We do not copy the message — our safety team reads it in the conversation through our operations console. Only when the message never became part of the conversation (it was blocked) do we keep its first 500 characters with the record. Safety alerts to our team (Slack and email, section 5) carry the kind of flag, the score and identifiers — never the message text.

7. How long we keep it

  • Account and persona data: while your account is open, then deleted within 30 days of closure.
  • Connected accounts (section 2): we keep no access or refresh tokens. The verification (platform, handle and when it was verified) is kept until you remove it or your account is deleted.
  • Conversations: while the ALTR is live, then deleted within 30 days of its deletion.
  • Safety flag records (section 6), including any kept excerpt: kept with the conversation they belong to and deleted with it.
  • Payment and payout records: seven years, because tax and accounting law requires it.
  • Sign in with Apple refresh token (section 2): kept in encrypted form while your account is open. When you delete your account we ask Apple to cancel it, and we delete it once Apple confirms. If Apple does not confirm, we try again every hour, for up to 24 attempts in all; after that the token stays stored, encrypted and unused, until our team fixes the cause and then cancels or deletes it.
  • Technical logs: 90 days.
  • Operational metrics (section 5): 90 days, then deleted automatically.
  • Service analytics: records sent to Mixpanel are kept for 2 years from the event date, then deleted automatically. Any device and IP details in our own database are cleared when you delete your account (section 4).
  • Backups age out on their own schedule, within 35 days of deletion.

8. Your rights

You can ask us for a copy of your data, ask us to correct it, ask us to delete it, or ask us to stop a particular use. Write to support@brnd.company and we will answer within 30 days.

Depending on where you live you may also have the right to complain to a data protection authority, and to object to processing or ask us to restrict it. Residents of California may ask what we disclosed and to whom; we do not sell or share personal information as those words are defined there.

Deleting your account deletes your ALTR and your conversations. It does not delete the payment records we must keep.

If you sign in with Apple, deleting your account also asks Apple to cancel ALTR's Sign in with Apple access, using the token described in section 2. We delete that token once Apple confirms. If Apple does not confirm, we try again every hour, for up to 24 attempts in all; after that the token stays stored, encrypted and unused, until our team fixes the cause and then cancels or deletes it (section 7). You can also stop using Sign in with Apple with ALTR at any time in your Apple Account settings.

To remove the verification from a YouTube, X or TikTok account you connected (section 2), write to support@brnd.company; there is no in-app control for this yet. Removing it means an ALTR presented as that account's owner becomes private until you verify again. We keep no token after connecting. For X, we ask X to cancel the token right away and never store it; if that request fails, the token expires on its own within two hours. For TikTok, we ask TikTok to cancel the token right away and never store it; if that request fails, the token expires on its own within 24 hours. For YouTube, ALTR stays listed in your Google account at https://security.google.com/settings/security/permissions, with YouTube read access, even though we keep no token. If you also sign in to ALTR with Google, it is the same entry as that sign-in permission, so removing it there also removes your Google sign-in permission and Google will ask you to approve ALTR again the next time you sign in with Google.

Service analytics stop when you delete your account. A request to suspend processing is handled as the law requires and, for service analytics, carried out by deleting the account. To have records already sent to Mixpanel deleted before their 2-year expiry, write to support@brnd.company (section 4).

If your account turned on analytics under the earlier optional setting, which was removed on October 11, 2026, you can withdraw that choice by writing to support@brnd.company. When you do, updates to your analytics profile at Mixpanel stop immediately, except a record of the withdrawal itself, and the profile is deleted after our team reviews the request. Deleting your account deletes it right away (section 4).

9. Children

You must be at least 13 years old to use altr.bio, and anyone under 19 needs a parent or guardian's permission (Terms, section 2). We do not knowingly collect data from anyone under 13. Adult (19+) content requires identity verification that confirms you are 19 or older. If you believe a child under 13 is using altr.bio, write to support@brnd.company and we will act.

10. Where your data goes

We process data in the United States and in the Asia Pacific region. If you are in the European Economic Area, the United Kingdom, or Korea, your data is transferred to those places under the standard contractual clauses or an equivalent lawful mechanism.

Service analytics are transferred to Mixpanel, Inc. in the United States. This transfer is part of the Terms and this Privacy Policy you agree to at signup. Section 4 sets out the recipient, its contact, the country, when and how the data is sent, the items, the purpose, how long it is kept, and how to refuse.

Our databases, file storage, the check of photos fans send (Amazon Rekognition) and our operational metrics (Amazon Managed Service for Prometheus, section 5) run in Amazon Web Services' Seoul region in Korea. The recipients below receive personal data outside Korea. These transfers are part of the Terms and this Privacy Policy you agree to at signup, and each is needed to provide the feature it serves.

  • Anthropic: Recipient: Anthropic PBC, which provides the AI models that write ALTR replies and help creators build an ALTR (contact: privacy@anthropic.com). Country: the United States, where Anthropic stores the data; the model itself may run in other countries where Anthropic operates. When and how: each time a fan sends a message or photo to an ALTR and each time a creator builds or edits an ALTR, over encrypted internet connections (HTTPS). Items: the fan's message and any photo attached to it, recent conversation context, and the material that defines the persona, including the public posts collected from the creator's connected accounts; the instructions a creator writes while building an ALTR. Purpose: to generate replies, to read any text in a fan's photo so it can be safety-checked, and to build personas. Retention: Anthropic deletes inputs and outputs within 30 days, except where it keeps them longer to enforce its usage policy or because the law requires it (https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data).
  • Amazon Web Services (Bedrock): Recipient: Amazon Web Services, Inc., whose Amazon Bedrock service runs our safety screening (contact: through https://aws.amazon.com/privacy/). Country: the United States (US West (Oregon); the safety screening in section 6 may also be processed in US East (N. Virginia) and US East (Ohio)). When and how: each time a fan sends a message in a chat, each time a fan sends a photo that contains text, and for each message and reply in creator-persona and 19+ chats, over encrypted internet connections (HTTPS). Items: the fan's latest message and the ALTR's previous reply (section 6); for a photo that contains text, the text read from it together with the fan's message; in creator-persona and 19+ chats, also the conversation context and persona instructions sent with the message, and the ALTR's reply. Purpose: to detect signs of suicide or self-harm risk, threats of violence, or a user under 18 (section 6), and to block messages and replies that break our rules. Retention: we have not turned on Bedrock's request logging; any retention by AWS for abuse detection is as set out in https://docs.aws.amazon.com/bedrock/latest/userguide/data-retention.html.
  • Stripe: Recipient: Stripe, LLC, our payment processor (contact: privacy@stripe.com). Country: the United States. When and how: each time you save a card, buy credits or receive a refund, over encrypted internet connections (HTTPS); card details you type on Stripe's payment page go to Stripe directly, not through us. Items: your account ID, your email address (for the receipt), the credit pack and amount, the card you saved with Stripe, and, on Stripe's page, the card details you enter. Purpose: to take payments, keep a saved card for later purchases, send receipts, process refunds and prevent fraud. Identity verification (Stripe Identity): when you start verification to turn on 19+ mode or publish adult content, we send your account ID and the verification session, and you show Stripe a government ID and a selfie on Stripe's page; Stripe returns whether it passed and your date of birth, and we keep only those together with the session ID — we never receive the ID images. Retention: for as long as Stripe provides its services and as long as the law requires it to keep payment records, as set out in https://stripe.com/privacy; Stripe's retention of verification documents is set out there too.
  • Apify: Recipient: Apify Technologies s.r.o., which collects public social posts for us (contact: privacy@apify.com). Country: the Czech Republic; Apify processes and stores data mainly in the European Union and the United States. When and how: when a creator connects a social account and when we refresh that account's public posts, over encrypted internet connections (HTTPS). Items: the address or handle of the public account the creator names and the number of posts to fetch; Apify then collects that account's public posts, captions and comments and returns them to us. Purpose: to collect the source material an ALTR learns from (section 2). Retention: only as long as needed for that purpose, as set out in https://docs.apify.com/legal/privacy-policy.
  • Google (YouTube): Recipient: Google LLC, which runs Google's sign-in for the connection, and its affiliate YouTube LLC, which provides the YouTube API Services (contact: through https://policies.google.com/privacy). Country: the United States. When and how: once, when a creator connects a YouTube account, over encrypted internet connections (HTTPS); you approve access on Google's own page, so what you enter there goes to Google directly, not through us. Items: the one-time authorization code Google returns, to get an access token; that access token, used once to read your channel's identity (section 2) and then discarded, not stored; it expires on its own, within about an hour. Google returns the items in section 2. Purpose: to confirm the creator owns the account (section 2). Retention: we keep no token; anything Google keeps is as set out in the Google Privacy Policy (http://www.google.com/policies/privacy). ALTR uses the YouTube API Services. You can remove ALTR's access at any time at https://security.google.com/settings/security/permissions (section 8).
  • X: Recipient: X Corp., which runs X's sign-in for the connection and the X API (contact: https://help.x.com/forms/privacy). Country: the United States. When and how: once, when a creator connects an X account, over encrypted internet connections (HTTPS); you approve access on X's own page, so what you enter there goes to X directly, not through us. Items: the one-time authorization code X returns, with the one-time PKCE verifier, to get an access token; that access token, used once to read your X account's identity (section 2) and then sent back to X to cancel it. X returns the items in section 2. Purpose: to confirm the creator owns the account (section 2). Retention: we keep no token; anything X keeps is as set out in X's privacy policy (https://x.com/en/privacy). You can remove ALTR's access at any time in the Apps and sessions section of your X settings (https://help.x.com/en/managing-your-account/connect-or-revoke-access-to-third-party-apps; section 8).
  • TikTok: Recipient: the TikTok company that operates TikTok in your region, which runs TikTok Login Kit for the connection and the TikTok API (contact: https://www.tiktok.com/legal/report/privacy). Country: the United States, and other countries where TikTok and its affiliates process data. When and how: once, when a creator connects a TikTok account, over encrypted internet connections (HTTPS); you approve access on TikTok's own page, so what you enter there goes to TikTok directly, not through us. Items: the one-time authorization code TikTok returns, to get an access token for the user.info.basic and user.info.profile scopes; that access token, used once to read your TikTok account's basic profile (section 2) and then sent back to TikTok to cancel it. TikTok returns the items in section 2. Purpose: to confirm the creator owns the account (section 2). Retention: we keep no token; anything TikTok keeps is as set out in TikTok's privacy policy (https://www.tiktok.com/legal/privacy-policy).
  • Google (Sign-In): Recipient: Google LLC, which runs Google's sign-in (contact: through https://policies.google.com/privacy). Country: the United States. When and how: each time you sign in with Google, over encrypted internet connections (HTTPS); you approve the sign-in on Google's own page, so what you enter there goes to Google directly, not through us. Items: the one-time authorization code Google returns, which our servers exchange for your identity; Google returns the items in section 2. Purpose: to sign you in. Retention: we keep no Google token from signing in; anything Google keeps is as set out in the Google Privacy Policy (https://policies.google.com/privacy).
  • Apple: Recipient: Apple Inc., which runs Sign in with Apple (contact: through https://www.apple.com/legal/privacy/contact/). Country: the United States. When and how: when you sign in with Apple in the ALTR iOS app and when you delete your account, over encrypted internet connections (HTTPS); you approve the sign-in on Apple's own screen on your device, so what you enter there goes to Apple directly, not through us. Items: the one-time code from your sign-in, to get a refresh token; when you delete your account, that refresh token, to cancel ALTR's Sign in with Apple access (sections 2, 7 and 8). Purpose: to sign you in and to cancel ALTR's access when you delete your account. Retention: we keep the refresh token as set out in section 7; anything Apple keeps is as set out in Apple's privacy policy (https://www.apple.com/legal/privacy/).
  • Sentry: Recipient: Functional Software, Inc. (Sentry), our error-reporting and feedback tool (contact: compliance@sentry.io). Country: the United States (Sentry's US data center). When and how: when an error happens on our servers, and when you send feedback with the in-app feedback button, over encrypted internet connections (HTTPS). Items: for errors, the error type, message and stack trace, the request path, a request ID and status code, and your account ID if you are signed in; for feedback, the items in section 5 (your IP address is sent with the request, and Sentry may use it to derive an approximate location). Purpose: to find and fix problems and to read your feedback. Retention: error reports are kept for up to 90 days under Sentry's standard retention (https://docs.sentry.io/security-legal-pii/security/data-retention-periods/); other data as set out in https://sentry.io/privacy/.
  • Slack: Recipient: Slack Technologies, LLC, our internal messaging tool (contact: privacy@slack.com). Country: the United States. When and how: when a fan message is flagged by safety screening (section 6) and when we receive a withdrawal of an earlier analytics choice (section 4), over encrypted internet connections (HTTPS). Items: for safety alerts, the kind of flag, the score, the ALTR's handle, and conversation and ALTR identifiers — never the message text; for withdrawals, the request ID, the account ID and the time of the request — never the email address. Purpose: to alert our team so it can act. Retention: kept in our Slack workspace under the retention settings we choose, as set out in https://slack.com/trust/privacy/privacy-policy.
  • Resend: Recipient: Plus Five Five, Inc. (Resend), our email delivery provider (contact: support@resend.com). Country: the United States. When and how: each time we send an email, over encrypted internet connections (HTTPS). Items: the recipient's email address and the content of the email, such as sign-in, verification and password-reset links, account notices and confirmations of your requests; emails to our team carry safety alerts and request notices with identifiers only. Purpose: to deliver email. Retention: only as long as needed for that purpose, as set out in https://resend.com/legal/privacy-policy.
  • GIPHY: Recipient: Giphy, Inc., which provides the GIFs you can send in a chat (contact: support@giphy.com). Country: the United States. When and how: when you search for a GIF, our servers send your search words to GIPHY; when a GIF is shown in a chat, your browser loads it from GIPHY's servers; both over encrypted internet connections (HTTPS). Items: the search words you type (our servers send them without your account ID or IP address); when your browser loads a GIF, what any web request carries, such as your IP address and browser details. Purpose: to let you find, send and see GIFs. Retention: for as long as needed to provide its services or as the law requires, as set out in https://support.giphy.com/hc/en-us/articles/360032872931.
  • How to refuse: These transfers are needed to provide the service and cannot be switched off on their own. To stop them, do not use the feature that needs them, or delete your account or ask us to delete it. For questions or requests, write to support@brnd.company.
  • If you refuse: Without the transfers to Anthropic and Amazon Web Services you cannot chat with ALTRs, and without Anthropic you cannot build or edit an ALTR. Without Stripe you cannot save a card or buy credits. Without Apify we cannot collect posts from your social accounts. Without Google, X or TikTok you cannot connect a YouTube, X or TikTok account; you can still prove ownership with a profile code. Without GIPHY you cannot search for, send or see GIFs. Without Resend we cannot send you sign-in, verification or password-reset emails or other account emails. Error reports to Sentry and alerts to Slack are part of running the service, so refusing them means deleting your account; feedback reaches Sentry only when you use the feedback button. Without Google or Apple you cannot sign in with Google or with Apple; you can still sign in with an email address and password.

11. How we protect it

Traffic is encrypted in transit. We do not collect payout bank details (payouts are not turned on, section 2). IP addresses kept with terms acceptances and reports are hashed before they are stored; for accounts that turned on analytics under the earlier optional setting (removed on October 11, 2026), the latest IP address is kept as is alongside that choice, and cleared when the account is deleted (section 4). Access to production data is limited to the people who need it and is logged.

No system is perfect. If a breach affects you, we will tell you and the relevant authority as the law requires.

12. Cookies

You can clear or block cookies in your browser. The sign-in cookie is required to use an account.

  • A sign-in token, so you stay logged in.
  • A language preference, so the site opens in the language you chose.
  • Analytics: a cookie that tells our servers your account ID, role, whether you have an ALTR and its status, and screen size class, and an anonymous device identifier kept in your browser's storage (section 4). Mixpanel sets no cookies of its own on altr.bio.

13. Changes

When this policy changes we update the date at the top, and we tell you on the site before a material change takes effect.

October 16, 2026: section 2 now says that push notifications in the ALTR mobile app are not turned on: the app does not ask for permission to send them and keeps no push token, and we will update this policy before turning them on.

October 17, 2026: sections 3 and 5 now describe identity verification through Stripe Identity, which is turned on for 19+ mode and for publishing adult content: you show a government ID and a selfie to Stripe, and we receive only the result and your date of birth.

October 16, 2026: section 9 now says altr.bio is for people 13 and older, that anyone under 19 needs a parent or guardian's permission, and that adult (19+) content requires identity verification that confirms you are 19 or older.

October 15, 2026: sections 2, 4, 7 and 8 now describe the ALTR mobile app: signing in with Apple, what we receive from Apple, and the Apple token we keep only to cancel ALTR's access when you delete your account; the sign-in token the app keeps on your device; and how service analytics work in the app. Sections 5 and 10 now also list Google, for signing in with Google, and Apple, for signing in with Apple.

October 14, 2026: sections 5, 7 and 10 now describe our operational metrics: totals of requests, response times, AI model usage and service outcomes, with no account ID, IP address or anything you write, stored with Amazon Managed Service for Prometheus in Amazon Web Services' Seoul region and kept for 90 days.

October 13, 2026: section 2 now describes what creators see about their fans: numbers for each fan under a fan number that only works inside their ALTR, never the messages, the fan’s name, or a summary of one fan. It no longer says creators can pay to read an identified fan’s history, which was never offered.

October 12, 2026: sections 2, 3, 5, 8 and 10 now describe connecting a TikTok account to prove it is yours, through TikTok Login Kit with the user.info.basic and user.info.profile scopes: we use only the handle and send the token back to TikTok to cancel it. Section 2 now says that verification through a platform's official sign-in is rolling out and offered only where it is available, and that a profile code always works instead. Connecting Instagram is not turned on.

October 11, 2026: section 10 now sets out, for every recipient that receives personal data outside Korea, the recipient, its contact, the country, when and how the data is sent, the items, the purpose and how long it is kept, and how to refuse. Section 5 now also lists GIPHY, which provides the GIFs you can send in a chat. Sections 4 and 8 now say how an account that turned on analytics under the earlier optional setting, removed on October 11, 2026, can withdraw that choice by writing to support@brnd.company, and how the withdrawal is handled. Sections 2, 3, 5 and 6 now describe only the model provider, payment features and safety checks that are turned on. Sections 2, 3, 5, 7, 8 and 10 now describe connecting a YouTube or X account to prove it is yours: what we receive from Google and X, what we send them, that we keep no token and read no posts through the connection, and how to remove the verification. Connecting TikTok or Instagram is not turned on.

October 10, 2026: service analytics and their transfer to Mixpanel in the United States are no longer a separate optional consent; they are part of the Terms and this Privacy Policy you agree to at signup (section 4). Sections 2, 3, 5, 7, 8, 10, 11 and 12 now say the same.

October 8, 2026: added section 4 on optional analytics and its transfer to Mixpanel in the United States, and brought the collection, retention, transfer, security and cookie sections in line with it.

October 8, 2026: added safety screening of fan messages by AI on Amazon Web Services' Bedrock, and Slack and Resend for safety alerts and email (sections 3, 5, 6 and 7).

14. Contact

BRND Creative Inc., 131 Continental Dr, Suite 305, Newark, DE 19713, United States.

Privacy questions and reports both reach one inbox: support@brnd.company

Privacy Policy · altr.bio