Privacy Policy

Privacy Policy

Effective Date: 11/07/2026

1. Introduction

At Embrs, we are committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use the Embrs mobile applications for iOS and Android, the Embrs web app, and the journey pages organizations share on Embrs (together, the “App”) and Embrs-operated services that support the App (for example, account registration, notifications, and related Embrs websites). It does not cover other products or websites operated by Embrs Inc. that publish their own privacy policies. By using the App, you agree to the practices described in this Privacy Policy. If you do not agree, please do not use the App.

2. Information We Collect

We collect information in a few different ways, including information you provide directly to us, information collected automatically when you use the App, and information from third parties, where applicable. We collect this information to provide and improve our services.

A. Personal Information

  • Account Information: When you register for an account, we may collect your name, email address, mobile phone number (if you use phone sign-in where available), and other contact details. To confirm your age in the mobile app, we first ask your app store: Apple’s Declared Age Range on iPhone, or Google Play Age Signals on Android. You, or your parent for a child account, choose in the system prompt whether to share it. We keep only the age band it gives (13 to 15, 16 to 17, or adult), which store it came from, and when. We do not keep the store’s response, a date of birth, or how your age was verified. If your band changes, for example when you turn 16, the app sends us the new one. If no store signal is available, for example on an older device or if you decline, we ask for your date of birth instead. We keep that date privately, use only the age band it gives, and you can correct it by contacting privacy@embrs.com. Where we have both, the app store’s band is used. We use your age band to apply the protections described in section 9.

  • Payment Information: The Embrs mobile App does not currently process Apple or Google in-app purchases. If you or your organization pay for Embrs through a web or administrative billing flow, payment card and billing details are typically processed by Stripe (or another payment processor identified at checkout). We do not receive or store your full payment card number.

  • Content You Provide: We process the content you create or upload in the App, which may include text, images, video, documents, and audio or voice recordings.

  • Journey Responses: When you take part in a journey an organization shares with you, we process your progress and the responses you give. You can take part in some journeys without an account; we then use an anonymous session to save your progress and responses on your device and our servers.

B. Usage Data

  • App Usage: We collect information about how you use the App, such as the features you use, the content you create, and the frequency and duration of your activities.

  • Device Information: We collect information about the device you use to access Embrs, including the device model, operating system, IP address, and general device identifiers.

  • AI Feature Records: When you use an AI Feature, we keep a record of each request: which feature was used, the results of our automated safety screening, which tools the feature used, and how much it used. These records do not include what you wrote. We use them to detect abuse, such as someone else using your account, and to resolve billing questions. For each conversation with the assistant that helps build journeys, we keep the most recent of these records, and older ones are removed as new ones are added. Records of how much a feature used are kept with the account’s usage and billing records, and counts of what our safety screening flagged are kept by category, without what was written or who wrote it.

  • Debugging Logs: To find and fix problems with AI Features, we keep logs of requests to them, including what was sent to the AI service provider and what it returned. These logs are kept by Cloudflare, which routes our requests to AI service providers, and are available only to our team. They have no fixed end date: the oldest are deleted as newer ones are added. Text that our automated content checks send to OpenAI’s moderation model (see section 3), and the results, are logged there too. Logs of these checks are automatically deleted after about 30 days, can be read only by members of our team with access to them, and are used only to operate and secure Embrs. Images are not kept in these logs.

  • Safety Check Results: When our automated checks look at content (see “Automated Content Checks” in section 3), we keep a record of the result: the categories found and, for images, the model’s scores. This record does not include the words of a post or reply, though text checked by OpenAI’s moderation model is kept in the logs described above. The check does not keep a copy of an image. For a name, username, bio, or description, we keep the earlier version so that we can put it back if a check fails. Earlier versions are deleted 90 days after the check, and so are the results, even if your account is deleted sooner. When a check removes a post or reply, though, we keep that result, which does not include the words, for as long as we hold the post or reply, so that it stays removed. What a check found and what we did about it stays in our moderation records. If the content has been reported, is part of a child-safety matter, or must be kept because of a law enforcement request or another legal requirement, we keep the result for as long as that requires. When content is reported, or an image a check flags has to be kept, we keep a copy of it as evidence, as described in section 3.

C. Cookies, SDKs, and Similar Technologies

  • Cookies and SDKs: We may use cookies, software development kits (SDKs), and similar technologies on the App and on Embrs websites that support the App to operate features, remember preferences, measure performance, send push notifications, and help keep Embrs secure. You can control some of these technologies through your device or browser settings where applicable.

D. Service Providers

We use trusted third-party service providers to help operate the App. Depending on how you use Embrs, these currently include providers such as:

  • Hosting and infrastructure: Supabase; Cloudflare (including Workers, Durable Objects, Workflows, R2 storage, Stream, Images, and related media services); Google Cloud, which runs the Embrs web app and journey pages and processes uploaded video and audio; and Framer, which hosts the embrs.com website.

  • Authentication and security: Supabase Auth; Google sign-in; Apple sign-in; Cloudflare Turnstile, which checks that visitors to journey pages and new guest sessions are not bots; and, where phone sign-in is enabled, Telnyx for SMS delivery.

  • Email: Resend, to deliver sign-in codes, invitations, and other emails from Embrs.

  • AI services: Cloudflare Workers AI, to transcribe audio and video into captions and transcripts, to screen what is sent to AI features and journeys before they are published for content our policies do not allow, to check the names of group chats and group chat photos (see “Automated Content Checks” in section 3), and to power other AI features; ElevenLabs, to turn text into narrated audio; and OpenAI, Anthropic, Google (Gemini), and Fireworks AI (which runs open models, such as DeepSeek and MiniMax, on its own servers), for features that help organizations build journeys, and OpenAI to check public posts, replies, captions, names, bios, and images (see “Automated Content Checks” in section 3). Some of these requests pass through Cloudflare AI Gateway. See “AI Features” in section 3.

  • Analytics, crash reporting, and push: Firebase Analytics and Firebase Crashlytics in the mobile apps; Firebase Cloud Messaging and Apple Push Notification service to deliver notifications, which means the notification text (for example, a sender’s name and a short preview) passes through Google and Apple; PostHog for product analytics on the Embrs web app and journey pages, linked to your account when you are signed in; and a visit counter on our web pages: Cloudflare Web Analytics on the Embrs web app and journey pages, and Framer’s site analytics on the embrs.com website. Each is a script that runs for every visitor and counts visits without cookies and without identifying you. If you do not want your visits counted, you can block these scripts in your browser’s settings or with a content blocker, or write to us with your objection at privacy@embrs.com. Cloudflare, which hosts our invitation and share links, also counts requests to them on its own servers (for example, how many there are, from which countries, and any errors), with nothing running on your device.

  • Payments: Stripe, when organization or other billing is processed outside Apple or Google in-app purchase.

These providers process information on our behalf and only as needed to provide their services to us. We may update this list as our stack changes.

E. Content From Other Sites

Posts and journeys can include content hosted by other sites, such as YouTube videos, Unsplash photos, and previews of linked web pages. When you view that content, your device loads it from the other site, which receives your IP address and browser or device information under its own privacy policy.

3. How We Use Your Information

We use the information we collect to operate and improve the App, communicate with you, and help keep Embrs safe and secure. These uses generally fall into core service delivery, improvement and personalization, communications, and security.

  • To Provide and Maintain Our Services: To operate Embrs, provide features, and respond to support requests.

  • To Improve Our Services: To analyze usage, fix bugs, and develop new features.

  • To Personalize Your Experience: To tailor content and features based on your preferences.

  • To Communicate with You: To send service-related notices, updates, or promotional communications. You may opt out of promotional messages at any time.

  • To Verify Your Identity: To send a one-time verification code by email or, where phone sign-in is available, by SMS. See “SMS and Text Messaging” below.

  • To Process Payments: Where billing is offered outside the App, to process transactions through our payment processor and manage billing-related communications.

  • To Ensure Safety and Security: To review reports, detect, prevent, and address fraud, abuse, or other harmful activities, including by automatically screening content sent to AI Features and journeys before they are published and by the automated content checks described below, and to enforce our Terms, Acceptable Use Policy, and Safety Standards.

AI Features

Some features of the App use artificial intelligence, as described in our Terms. For example, we transcribe the audio in videos and recordings you upload to create captions and transcripts, we turn text into narrated audio, and we offer tools that help organizations build journeys from material they provide.

  • What is sent: When you or an organization uses an AI Feature, we send the AI service providers listed in section 2.D only the content that feature needs, such as the audio being transcribed, the text being narrated, or the messages, documents, and images an organization provides to build a journey. They process it to produce the result for us.

  • Crisis resources: If a message to the assistant that helps build journeys suggests that someone may be at risk of harm, the assistant shows crisis helplines. We keep a count of how often the helplines were shown, which does not include the message or who sent it. The message itself stays in the conversation like any other message.

  • No training: We do not use your content to train AI models. We use these providers’ business services, under which they do not use the content we send them to train their models.

  • Voice: We use your voice recordings to play them back and to create captions and transcripts. We do not create voiceprints or use your voice to identify or authenticate you.

  • Storage: Captions and transcripts are deleted when the video or recording they belong to is deleted. The conversations and drafts used to build a journey are kept until the account or organization they belong to is deleted, as described in “Data Retention”.

Automated Content Checks

To help keep Embrs safe, we check some content automatically, in addition to reviewing what people report to us.

  • Public text: Posts, replies, and captions; profile names, usernames, and bios; and the names of organizations and channels are checked right after they are posted or changed, by OpenAI’s moderation model, for content our Acceptable Use Policy does not allow. The names of group chats are checked the same way by a model running on Cloudflare Workers AI.

  • Images: Images in posts and replies, the poster image of a video, and profile and channel photos are checked once, when they are first used in one of those places, by OpenAI’s moderation model, for sexual and graphic content. A group chat’s photo is checked the same way by a model running on Cloudflare Workers AI. Only the image is checked, never the words or captions around it. Videos themselves, and organization logos and banners, are not checked this way.

  • Your chats: We do not currently use automated systems to check the words you write in one-to-one or group chats, including captions on photos and videos you send in them. A group’s name is checked like other public names, but its messages are not. Voice and video messages are transcribed to create captions, as described in “AI Features”, and those transcripts are not checked either. If that changes, we will update this policy before it does. The words in a chat reach our team only when someone in it reports it. A photo or video sent only in a chat is not checked by any automated system, and nothing from a chat is sent to OpenAI.

  • Action before review: If a check finds content in a serious category, such as threats of violence, sexual content, the sexual exploitation of children, other sex crimes, hate, or weapons capable of mass harm, it acts before a person reviews it: a post or reply is removed, and a name or bio goes back to what it was before. We tell you when this happens, which of our guidelines it broke, and whether the decision was automated. Repeated violations lead to warnings, temporary blocks on one feature, and suspension. If we got it wrong, write to safety@embrs.com. If we agree, we restore the post, or tell you that you can change the name or bio back. Other results are recorded but not acted on, and content about self-harm is not removed. Our team can also restrict an account: while it is restricted, its new posts and replies are visible only to the account itself until our team releases them or the restriction ends. We tell the person what is restricted, for how long, and which guideline it concerns, and again if we lift it early. A clearly sexual image in a post or reply is removed, and its author is told. One that is close to the line is shown behind a warning that you can tap through until our team reviews it, and if they leave it up, the warning comes off. A clearly sexual profile, channel, or group photo is not used, and the earlier photo stays. If an image that was checked this way is also sent in a chat, a sexual one is blurred there until someone taps to see it. Graphic or violent images are never removed automatically, because context matters, such as news. They are shown behind a warning that you can tap through, in public and in chats, and public ones go to our team, who remove the most extreme. Images are delivered right away, and these actions apply a few seconds later, once the check finishes. Graphic or violent images, and sexual images waiting for review, are hidden from users under 18, and in a chat that includes someone under 18 graphic images cannot be revealed.

  • Unsent messages: When you unsend a chat message, it is removed for everyone in the conversation right away. So that a harmful message can still be reviewed, we keep a hidden copy of it, and of any photo, video, voice message, or document in it, for 30 days. If someone in the conversation reports the conversation, or the person who sent the message, the copy can be included in the report, limited to messages the person reporting could see. Our team reviews the copy only as part of a report, or when the law requires it. After 30 days the copy is deleted, unless the message has been reported, is part of an open report or a child-safety matter, or the law requires us to keep it. If your account is permanently deleted sooner, the copy is deleted with it, with the same exceptions.

  • Reports: When you report something, we keep a copy of it as it was, a record of who is involved, and, for a chat message, up to 10 earlier messages in that conversation that you could see. Media in the reported item is kept from deletion. Only a small number of our team can read these copies, and every time they do is logged. They are kept even if the content is later deleted or unsent, or either account is deleted, generally for 3 years after the report closes, and longer for child-safety matters or where the law requires it.

  • Child sexual abuse material: If a check or a report finds apparent child sexual abuse material, we remove it, suspend the account, preserve the material and related information as the law requires, and report it to the National Center for Missing & Exploited Children (see section 5).

4. SMS and Text Messaging

Where phone-number sign-in is available, when you sign in to Embrs with a phone number we send you a one-time verification code by SMS (currently via Telnyx). We use your phone number to verify that you control that number and to secure your account. Phone-number sign-in may not be enabled for all users or regions at all times.

  • How you consent: You provide your mobile number yourself on the Embrs sign-in screen and confirm that you agree to receive a verification code before any message is sent. We never send a message to a number you did not enter yourself. Providing your number is the only way to opt in, and consent is not a condition of any purchase.

  • Message frequency: Message frequency varies and depends on how often you sign in. Each sign-in attempt sends a single verification code.

  • Cost: Message and data rates may apply. Embrs does not charge you for these messages; your mobile carrier may.

  • How to opt out: Reply STOP to any message to stop receiving them, or HELP for help. Opting out will prevent you from signing in with your phone number. You can reply START to resubscribe.

We do not sell, rent, or share your phone number or your SMS consent with third parties or affiliates for their own marketing purposes. We share your phone number only with the telecommunications provider that delivers the message on our behalf (currently Telnyx), and only for the purpose of delivering it.

Delivery is not guaranteed. Mobile carriers are not liable for delayed or undelivered messages.

For help with text messages, contact info@embrs.com.

5. How We Share Your Information

We do not sell your personal information. We may share your information in the following circumstances:

  • With Service Providers: With the providers described in section 2.D and other trusted providers who assist us in operating the App. These providers are obligated to protect your information and use it only for specified purposes. Phone numbers and SMS consent are never shared with third parties for their own marketing purposes.

  • With Organizations: When you join an organization on Embrs or take part in a journey it shares with you, that organization can see what you share with it: your name and profile within the organization, the content you create in its space or on its behalf (“Organization Content”, as defined in our Terms), and your responses to its journeys. The organization controls its Organization Content and the responses shared with it, decides how long they are kept, and may have its own privacy practices. Requests about that information can go to the organization, and we will help it respond. An organization’s members can also connect AI assistants they choose (for example, Claude or ChatGPT) to their Embrs account to review the organization’s journeys and their activity, including written journey responses. Those responses are shown without participants’ names, and the assistant’s own provider handles them under its own terms.

  • For Legal Reasons: To comply with legal obligations, enforce our rights, or protect the safety and security of Embrs and its users. When we find apparent child sexual abuse material, U.S. law requires us to report it to the CyberTipline of the National Center for Missing & Exploited Children (NCMEC). A report may include the material, information about the account involved (such as its username, email address, phone number, and the IP address and time of the upload), and related content, such as the surrounding messages. NCMEC may share reports with law enforcement.

  • Business Transfers: In connection with a merger, acquisition, or sale of all or a portion of our assets.

6. Data Security

We implement reasonable administrative, technical, and organizational safeguards to protect your information. However, no system is completely secure, and we cannot guarantee absolute security.

7. Data Retention

We retain your information for as long as necessary to provide our services, comply with legal obligations, resolve disputes, and enforce our agreements. If you delete your account, it is hidden right away, and you can restore it by signing back in within 15 days. After that we permanently delete your account and personal information. That includes your profile, your one-to-one messages, your connections, and the content and media you created outside organizations. Debugging logs, including logs of our automated content checks (see section 2.B), are not deleted when you delete your account, so they can outlast it. Records of AI Feature requests (see section 2.B) do not include what you wrote, and after your account is deleted they no longer identify you. We keep only limited information we need for legal, security, or billing reasons (for example, a record of your deletion request, records of moderation actions, safety check results, sign-in security logs, and billing records), along with usage records that no longer identify you. Copies in backups and in our service providers’ systems are removed on their own schedules. Organization Content stays with the organization, with your name and profile removed. Messages you sent in an organization’s group conversations remain there, shown as from a “Former member”. If you are the primary owner of an organization that has other members, you transfer ownership of it or delete it before deleting your account. If an organization removes you, you keep your own account, and the organization keeps its Organization Content.

8. Your Rights and Choices

Depending on your location, you may have rights under applicable data protection laws, and those rights may vary by jurisdiction. We do not sell your personal information. Where required by law, you may have rights to access, correct, delete, or obtain a copy of your personal information, and to opt out of certain processing.

  • Access and Correction: You may access and update certain personal information through your account settings, or by contacting us at privacy@embrs.com.

  • Deletion: You may delete your account in the App’s settings (on the web, under Settings, then Profile) or by contacting privacy@embrs.com. Deletion follows the 15-day restore period described in “Data Retention” before permanent removal, subject to legal requirements.

  • Data Portability: You may request a copy of your personal data by contacting privacy@embrs.com. We will respond as required by applicable law.

  • Opt-Out: You may opt out of promotional communications by following the instructions in those messages or adjusting your preferences in the App. To stop verification text messages where phone sign-in is used, reply STOP to any message.

9. Children’s and Teens’ Privacy

Embrs is not intended for use by individuals under the age of 13. We do not knowingly collect personal information from children under 13. Users are asked to confirm they are 13 or older. If we become aware that we have collected personal information from a child under 13, we will take steps to delete it. See also the eligibility rules in our Terms & Conditions.

Users Aged 13 to 17

  • How we know your age: We ask your app store for your age band, or ask for your date of birth if it cannot tell us, as described in section 2.A. Existing accounts are asked the next time they open the mobile app. Your age band, and the date of birth if you gave one, can be changed only by contacting us. If someone answers that they are under 13 while signing up, the sign-up ends and the new account is deleted with everything in it. Only the device keeps a note of when the answer was given, which blocks a different answer for a day. If someone with an existing account answers that they are under 13, we do not keep the date they gave. We keep a record of the account and when the answer was given, refuse another date of birth for that account for a day, and sign them out.

  • Images: Graphic or violent images are hidden from you, and in a chat you are in they cannot be revealed.

  • Reports first: Reports about child safety are reviewed before other reports.

10. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we change it, we will update the dates at the top of this page, and if we make material changes, we will also provide notice through the App or other reasonable means. Continued use of the App after changes take effect constitutes acceptance of the revised policy.

11. Contact Us

If you have questions or concerns about this Privacy Policy or our data practices, please contact us at privacy@embrs.com.