Effective date: October 3, 2026
beau. ("the App") is a social networking application for gay men. The App is operated by Beau Period LLC, a Maine limited liability company ("Beau Period LLC," "we," "us," "our"). This Privacy Policy describes how we collect, use, store, and protect your personal information when you use the App.
| Data | Purpose | Required |
|---|---|---|
| Phone number | Account verification, login | Yes (if signing in with phone) |
| Email address | Account identifier, login, account recovery | Yes (if signing in with Apple or Google) |
| Name | Display on your profile | Yes |
| Date of birth | Age verification | Yes |
| Gender / how you identify | Profile display, matching, and safety features | Yes |
| Who you're interested in | Matching and discovery | Yes if Dating or Play headspace selected |
| Photos (public) | Profile display; a public photo you add later is also posted to the feed automatically (see "Automatic feed items" below) | Yes (at least 1) |
| Photos (private/spicy) | Private sharing via mutual unlock | No |
| Photos you post to a Space | Public display on that venue's Space page, visible to anyone who can view the Space; also posted to the feed automatically | No |
| Feed posts (text, a photo, a song, a place tag) | Shown in the feed to the users your post can reach (Section 7) and, for posts you write yourself, on your profile's feed | No |
| Hearts and reposts | A heart tells a post's author you loved the post; a repost shares another user's post to your own audience with your comment (Section 7) | No |
| Profile prompts and answers | Profile display | No |
| Headspace selections | Matching (Friends, Play, Dating) | Yes (at least 1) |
| Tags (vibe, identity, spicy) | Profile and matching | No |
| Live status text | Profile display, Out Now feed | No |
| Out Now text | Temporary status display | No |
| Place tagged on a post or status (a venue or a city) | Shown on the post as the place name. If your phone is actually there, the tag also makes you Out Now at that place for about three hours: your name is shown at that place on its Space page, in the Out Now list, and on the post as "here now", visible to users whose headspace lets them see it | No (only when you tag a place) |
| Automatic Check-in (opt-in) | Adds to anonymous "here now" counts and weekly activity at Spaces; your individual check-in record is kept for up to 30 days and is never shown to other users | No (off by default) |
| Hometown (city, state) | Profile display, New Here features | No |
| Trips (city, dates) | New Here/traveling features; a trip is also posted to the feed automatically (see "Automatic feed items" below) | No |
| Health information (HIV status, PrEP/doxyPEP, U=U, last-tested date, mpox/HPV/Hep A&B vaccinations) | Profile display, shared at your discretion | No |
| Substance use tags | Profile display | No |
| Playlist URL | Spotify or Apple Music embed on profile; a change is posted to the feed automatically | No |
| Messages | Communication between users | N/A |
| Safety reports and block reasons | Platform safety | When blocking |
| Identity-verification selfie | Compared with your profile photos by a member of our team when we ask you to confirm a profile is really you; deleted once the review is done, unless the account is banned (Sections 6 and 8) | Only if we ask |
| Support tickets and messages | Customer service communications | If you contact support |
Some of what you do on beau. is posted to the feed automatically, in your name, so the feed stays alive without anyone having to write a post: a new public profile photo, a playlist update, favoriting a Space, RSVPing to or hosting a public event, adding photos to a Space, a trip you add (that you are coming to a city, that you are visiting it on the day the trip starts, and, when your device's location shows you have arrived, that you are there), being Out Now at a venue, and your arrival on beau. These items use information that is already on your profile or already visible in the App, and they follow the same audience rules as everything else you post (Section 7). Items tied to a place reach only users within about 25 miles of it, and an Out Now item ends when your status does. Nothing spicy is ever posted automatically, and neither are headspace changes, relationship status, or tag edits.
There is no setting that turns automatic items off. You can delete any of them from your feed after it posts, and an item goes away on its own when you undo the thing behind it (withdraw the RSVP, unfavorite the Space, remove the photo, clear your Out Now). Turning off "Show going-out events" in Settings stops RSVP items, and Hide Profile (a beau.plus feature) stops all of them while it is on.
| Data | Purpose |
|---|---|
| Device location (GPS) | Nearby users, distance display, adaptive radius, and (if you opt in) automatic venue check-in |
| Push notification token | Delivering notifications |
| Account creation date | New Here features, account age |
| Last active timestamp | Out Now feed, online indicators |
| Profile views | When you open another user's profile we record that you did (who viewed whom, and when). beau.plus members can see the names and photos of the people who viewed their profile recently; free members see only a count. Turning on Browse Incognito (a beau.plus feature) keeps your views off other people's lists. View records are deleted after 90 days |
| IP address | Fraud prevention and account security (detecting fake, duplicate, and evading accounts), enforcing where beau. is available, and safety incident reporting (NCMEC compliance). The address your account was created from is retained with your account for as long as the account exists. |
| Device and App version information | Your device model, operating-system version, App version and build, and the identifier of the App update you are running are recorded with your account each time the App launches. We use them for support and debugging, to know which version of the App you are on, and, together with other account signals, to detect fake, duplicate, and evading accounts. They are never shown to other users |
| Crash reports and performance data | Bug fixing and stability monitoring (see "Crash Reporting and Session Replay" below) |
| Subscription and purchase records | Manage beau.plus subscription state (transaction IDs and entitlement status only; payment method is held by Apple or Google, not by us) |
| App interaction events (pseudonymous) | Usage analytics we review in aggregate to improve the App. Events are recorded under a stable pseudonymous identifier derived from your account; no name, contact details, or device identifier is stored with them, and raw events are deleted after 180 days. Pseudonymous is not anonymous: beau. holds the key that could re-associate events with your account, though we do not build individual behavioral profiles from them |
To diagnose bugs and stability issues, beau. uses Sentry to collect crash reports and a small percentage of session replays. Specifically:
If you choose to sync your contacts, the phone numbers in your address book are sent to our servers over an encrypted connection and hashed there with a secret key that never leaves our servers. The raw phone numbers are discarded once they are hashed and are never stored, and we never receive contact names. We store only the hashed values, which are used to calculate mutual friend counts and to power the optional "Hide from Contacts" feature.
The "Hide from Contacts" feature works in both directions: if you enable it, you and the beau. members whose phone numbers are in your synced contacts are hidden from each other in the feed, Explore, and the App's other discovery features. The match compares the hashes from your contact sync with the hashed phone number on each member's account, so it needs your contacts to be synced. You can toggle this in Settings. You can delete your synced contact hashes at any time through Settings.
When you sign up or log in using your phone number, beau. sends a one-time verification code (OTP) by SMS to confirm that you control the number. By entering your phone number in the App and tapping the action that triggers a code (e.g., "Send code"), you consent to receive an SMS verification code at the number you provided.
Carrier name lookup. When our trust and safety team investigates an account, we may ask our SMS provider (Twilio) for the name the phone carrier has on record for the account's number. The answer is kept as a note on the account, visible only to our team, until the account is deleted.
Some of what beau. processes is sensitive, and different kinds are handled differently. What is true of all of it: we never sell it, never share it with advertisers or data brokers, never use it for targeted advertising, never use it to train or operate any artificial-intelligence model, and never use it to make decisions about you with legal or similarly significant effects.
Health fields (HIV status, PrEP/doxyPEP use, U=U, last-tested date, and mpox/HPV/Hep A&B vaccinations) are optional and self-reported, and you can edit or remove them at any time. They are used only to display your profile as you set it up and, if you use them, to power private wellness reminders shown only to you. They are not used for matching, ranking, or filtering, and no one's feed is ever ordered by anyone's health information. We do not verify health information, and you should not treat another user's health information as confirmed.
Substance-use tags are optional and work like other profile tags: if you add them, they are displayed on your profile, factored into match ordering, and available in the filters other users choose, all according to the selections you and they make.
beau. does not collect "sexual orientation" as a separate field, but because beau. is an app for gay men, your presence here and the gender and "who you're interested in" details you provide may reveal your orientation or related characteristics. Gender is required, and "who you're interested in" is required for the Dating and Play headspaces. They are displayed as you choose and are used to operate discovery according to your own selections: in Dating and Play, you and another user see each other only when each of you matches what the other is looking for. Together with other account signals, this information also helps us keep beau. free of fake and abusive accounts.
Your device's location is used to operate location-based features (nearby discovery, distance display, Spaces and check-ins) and to protect the platform (enforcing where beau. is available and preventing abuse). It is never used for advertising and never sold, and other users only ever see the coarsened location information described in Section 7, or a place you chose to tag yourself. Location signals that suggest an account is outside the United States or is misrepresenting where it is can lead to automatic restrictions on that account, which you can ask us to review in the App.
Because your profile is visible to other users you match with, do not add anything to your profile that you would not want other users to see. If you would rather keep your health information, or anything else optional, private, simply leave those fields blank.
Messages. Direct and group messages on beau. are end-to-end encrypted. Each user has a private key that is created on their own device, and we never receive it in a form we can open, so we cannot read the contents of your messages.
Your key and your phone's backups. On iPhone, your private key is included in your phone's own backups, so restoring an iCloud backup, or an encrypted backup from your computer, onto a new iPhone brings your messages with it. Apple protects iCloud backups, and end-to-end encrypts them if you turn on Advanced Data Protection; a computer backup is protected by the password you set for it. We never receive the key from those backups. On Android, your private key is not included in your phone's backups.
Chat backup (optional). If you turn on Chat backup (Settings > Account > Chat backup), beau. gives you a 12-word recovery phrase. Your device uses the phrase to encrypt a copy of your private key, and only that encrypted copy is stored on our servers, together with the technical settings needed to use the phrase again (such as a random salt). We never receive your phrase or the key made from it, so we cannot open your backup. So that you can move to a new phone of the same kind without typing the phrase, the key made from your phrase is also saved in your phone's own synced storage: iCloud Keychain on iPhone, which Apple end-to-end encrypts, and Google Block Store on Android. On Android, it is saved with Google Block Store, which backs it up to Google's cloud; Google end-to-end encrypts that copy when your phone has a screen lock, and without one Google protects it but does not end-to-end encrypt it. Turning Chat backup off deletes the encrypted copy from our servers and the key from iCloud Keychain or Block Store. Deleting your account deletes the encrypted copy from our servers.
Reporting and encryption. Messages are end-to-end encrypted in normal use, so beau. cannot independently read message contents. If you choose to report a message or conversation, the content you submit with that report, and limited surrounding context where technically available, is decrypted on your device and made available to beau.'s safety team for review. Reporting discloses only the messages you choose to submit; it does not give us the ability to read your other messages.
Private photos. Private ("spicy") photos are encrypted using a per-photo symmetric key (NaCl secretbox). The symmetric key is encrypted with your X25519 public key. Private photos are only decryptable when both users have independently shared access with each other (mutual unlock). Revoking access removes the key share, making the photos inaccessible. We cannot view the contents of encrypted private photos without the corresponding key shares. beau. uses available platform controls to deter or restrict screenshots and screen recording where technically supported, but these safeguards cannot guarantee that another user will not capture, photograph, or record content using another device or method. Share private photos and sensitive content only with people you trust.
Chat photos. Photos you send in direct and group chats are encrypted with a per-photo key that is wrapped to the recipient (a direct message uses their public key; a group uses the group key), so our storage providers hold only ciphertext and beau. cannot view the stored image. As with all photos, the image is scanned for illegal or abusive content at upload, before it is encrypted (see Section 6).
Feed posts. Posts are not end-to-end encrypted. The text, public photos, song details, and place tag on a post are stored in readable form so we can show the post to its audience, screen it, and act on reports about it. The exception is a spicy photo posted to the feed: it is encrypted the same way private photos are (a per-photo key shared only with people you have mutually unlocked with), it never joins your profile gallery, and it is shown only in the Play headspace. A reply to a post is an ordinary direct message with its author and is encrypted like any other message; the post itself is not attached to it.
What encryption can't do. When you delete a message or your account, the messages you sent are removed from beau.'s servers, so they also disappear for the people you sent them to. Messages another user sent you remain part of their account until they delete it. None of this can remove copies that have already been delivered, saved, screenshotted, photographed, or exported by another user. Share with people accordingly.
Every photo uploaded to beau. is scanned before encryption or storage by:
These automated minor-detection and photo-safety tools assess whether an uploaded image appears to depict a minor or other prohibited content. beau. does not use these tools to create or store biometric identifiers or facial-recognition templates for identifying users.
Photos posted to the feed go through the same screening as profile photos, including the checks for contact information and QR codes described in our Terms. The text of a post is checked by an automated filter for contact information and certain prohibited terms before it is published; we do not run machine-learning classifiers over the text of your posts, and a person reviews anything that is reported. When we ask you for an identity-verification selfie, the selfie is screened by the same tools for illegal content and is then compared with your profile photos by a member of our trust and safety team, not by software. We do not run facial recognition on it and do not keep a face template.
If apparent CSAM is detected:
This process is required by federal law (18 U.S.C. 2258A) and we cooperate fully with law enforcement in these matters.
Your public profile information (name, photos, prompts, tags, headspaces, status, hometown, trips, and your favorite Spaces) is visible to other users based on headspace overlap and your privacy settings. If you add a venue to a status or post a photo to a Space, those appear on that venue's Space page to other users who can view it. Your age/date of birth is never displayed to other users. Mutual friend counts are displayed, but the identities of mutual friends are never revealed.
The feed. Posts you write are shown to the users your post can reach: the same headspace, block, Not For Me, and contact-hiding rules that decide who sees your profile decide who sees your posts, and a post marked spicy is shown only in the Play headspace. Your posts also appear on your own profile's feed to the same audience (automatic items and shared prompt answers stay on the Home feed only). Other users can repost a post of yours with their own comment. A repost keeps your post's spicy setting and headspace scope but is shown to the reposter's audience, which can include people your own post would not have reached (for example, people farther than 25 miles from a place you tagged). A repost is not a copy: if you delete your post, the reposter's comment stands on its own without your content. When someone hearts your post you can see who did (their name and photo); everyone else sees only a rough sense of how many, never an exact count. Reactions and reposts on your posts notify you by name, and a switch in Settings turns those notifications off. Follows are private: only you can see who follows you and there is no follower count anywhere. When someone follows you, you are notified by name (several follows close together arrive as one notification), and a switch in Settings turns those notifications off; nobody is notified when you unfollow. Songs on posts are Apple Music links; the Apple row below describes what Apple sees.
beau. shows approximate distance between users to power the Nearby feed. You can turn distance display off in Settings, and when it is shown, distances are computed from coarsened coordinates rather than your exact GPS position. To keep the approximate location other people see from jumping around, we keep the general area you are in now and the one before it. The earlier one is forgotten after 30 days. Even so, distance information could in theory be combined to estimate your general location, so use the distance and Hide Profile controls as you see fit.
| Provider | Purpose | Data Shared |
|---|---|---|
| Supabase | Database, authentication, storage | All account data (encrypted at rest) |
| Cloudflare (R2, Images) | Photo storage (profile, feed, and chat photos), image resizing, and content delivery (CDN); marketing-website hosting | Photo files and the requests made to serve them. Public profile and feed photos are stored with provider-level encryption at rest; private (spicy) and chat photos are stored only as ciphertext we encrypt before upload |
| Sightengine | Photo content moderation | Photo data (in memory, not stored) |
| PhotoDNA (Microsoft) | CSAM hash matching | A perceptual hash of each photo, computed on our servers; the photo itself is never sent to Microsoft |
| NCMEC | CyberTipline reporting of apparent CSAM, as required by federal law | Only when a report is filed: the reported image and report data (account identifiers, IP address, and incident details) |
| Apple (App Store, iOS) | Sign in with Apple; subscription billing; anti-fraud device attestation (App Attest) | Sign-in identifier; purchase transactions; a device attestation token (no personal data) |
| Google (Google Play, Android) | Sign in with Google; subscription billing; anti-fraud device attestation (Play Integrity) | Sign-in identifier; purchase transactions; a device integrity token (no personal data) |
| Google Maps Platform (Places API) | Venue search, autocomplete, and place details for Spaces, statuses, and events | Your venue search text and an approximate (city-level) location to rank nearby results, relayed through beau.'s servers. We do not send your precise location, a device identifier, or your device's IP address. |
| Apple Maps (MapKit, iOS) | Showing the venue map on a Space page (iOS) | Venue coordinates, to render the map |
| Apple (iTunes Search API, Apple Music) | Song search when you attach a song to a post; song artwork and 30-second previews on posts that carry a song | Your song search text is sent from your device directly to Apple, and Apple sees the IP address of any device that searches for a song, loads a song's artwork in the feed, or plays a preview. We store only the song's title, artist, and Apple links |
| Expo; Apple Push (APNs); Firebase Cloud Messaging (Android) | Push notifications | Device tokens, notification content |
| Sentry | Crash reporting, performance monitoring, sampled session replay (text + images masked) | Stack traces, device + OS metadata, App version, sampled view-tree replays without text/image content |
| Twilio | SMS delivery (verification codes, and a one-time text for people who asked for one: the launch notice for people who joined the waitlist in an earlier version of the App, or the notice for people who paused their account and asked to hear when their area grows) and phone-number line-type checks that block fake sign-ups, and, when our team investigates an account, the name the carrier has on record for its number | Your phone number |
| Resend | Email delivery (a one-time notice for people who paused their account and asked to hear when their area grows) | Your email address |
We will disclose information to law enforcement when:
We review law-enforcement and legal requests for facial validity and scope, and we may object to, narrow, or decline requests where appropriate and legally permitted. We will still comply with valid legal process and with legally required reporting (such as CSAM reporting to NCMEC).
We do not sell, rent, or trade your personal information to third parties. We do not display ads inside the App, and we do not share your data with data brokers or ad networks. We may promote beau. through advertising on other platforms (such as Apple, Google, or Meta), but we do not give them your personal information for advertising; to measure whether an ad led to a sign-up we rely only on the aggregated, privacy-preserving attribution those platforms provide (for example Apple's SKAdNetwork), which does not identify you.
We do not use your personal information (your profile, photos, messages, or sensitive information) to train, fine-tune, or operate any artificial-intelligence or machine-learning model, and we do not share your personal information with AI providers for those purposes. Matching on beau. uses our own tag-based affinity scoring, not automated profiling of you.
| Data | Retention |
|---|---|
| Active account data | Retained while your account is active |
| Deleted account data | Deleted when you delete your account, except for the limited records described under "What we keep after deletion" below |
| Messages | Deleted when you delete them: removed from view immediately and permanently erased within 30 days. The messages you sent are also deleted when you delete your account; messages another user sent remain until they delete them or delete their account |
| Contact hashes | Deleted when you unsync contacts or delete your account |
| Account creation IP address | Retained with your account while it exists and deleted when you delete your account, except where it forms part of a safety incident record |
| Safety incident records | Retained indefinitely for legal compliance |
| NCMEC report IDs and hashes | Retained indefinitely for legal compliance |
| Safety reports | Retained indefinitely for platform safety |
| Out Now status text | A status stops being visible to other users when it expires (usually 3 hours). Each status, including ones you have replaced with a newer one, is then kept for 30 days and deleted automatically. A status is kept for longer only if it is relevant to an open safety report about your account or is placed under legal hold |
| Expired trips | Deleted automatically after end date passes |
| Venue check-in records | Deleted automatically after 30 days; deleted immediately if a venue is designated sensitive or removed |
| The general area you were in before your current one (used to keep your shown location steady) | 30 days |
| Photos posted to a Space | Kept while posted; deleted when you remove the post or delete your account |
| Feed posts | Kept until you delete the post or your account; posts do not expire on their own. Automatic items tied to something temporary (being Out Now at a venue, a Space's "tonight" item) leave the feed when that ends. Deleting a post removes it and its hearts immediately; a public photo attached to it is no longer linked from the App but may remain in our photo storage until you delete your account |
| Hearts, reposts, follows, feed hides and mutes, pinned chats | Kept until you undo them (a repost is a post of yours and is deleted like one) or delete your account |
| Profile view records | Deleted automatically after 90 days |
| Identity-verification selfies | Deleted as soon as our team finishes the review, with a nightly sweep as a backstop, unless the account is banned (see "Banned accounts" below), and deleted with your account if the review is still open. We keep the outcome of the review (status, date, and reviewer notes) and the automated screening record, which holds a hash of the image and not the image |
Deleting your account permanently deletes your profile, photos, posts, the messages you sent, engagements, follows, blocks, contact hashes, trips, and the rest of your account data. A few narrow categories are kept after deletion, and only for the purposes below:
Banned accounts. Termination for violating our Terms is not the same as deletion. When an account is banned, we retain the account record, including its photos, any identity-verification selfie, and their derived photo hashes, its sign-in and device identifiers, and its enforcement history, for as long as reasonably necessary to enforce the ban, prevent replacement accounts and repeat abuse, comply with law, and resolve disputes. Photos and selfies are kept for one purpose: recognizing when a banned account's photos or face reappear on a new account. Banned photos are never publicly visible or served in the App. An account terminated solely because its holder is under 18 is not handled under this paragraph: it is deleted as described in Section 11, keeping only legally required and safety-related records.
If you are a California resident, the California Consumer Privacy Act (CCPA), as amended by the CPRA, gives you the following rights with respect to personal information that Beau Period LLC collects about you:
To exercise these rights, email hey@beauperiod.com from the email address associated with your account, or use the in-App account deletion option. We will verify your request by confirming your control of the account (typically via SMS or email confirmation tied to the account on file). Authorized agents may submit requests on your behalf with written, signed authorization and proof of identity. We will respond within forty-five (45) days, or notify you of an extension as permitted by law.
If we deny your privacy request, you may appeal by replying to our decision email with "Privacy Appeal" in the subject line, or by contacting hey@beauperiod.com.
beau. is available only in the United States. It is not directed to, marketed in, or offered to individuals located in the European Union, the European Economic Area, or the United Kingdom, and we do not knowingly accept users located there. Where European or UK data-protection law nevertheless applies to a particular processing activity, Beau Period LLC (as the controller) complies with the requirements that apply, including using legally recognized transfer safeguards where required, and you may contact hey@beauperiod.com to exercise any rights available to you under that law.
We implement the following security measures:
Breach notification. No method of storage or transmission is perfectly secure, and we cannot guarantee absolute security. If we become aware of a security breach that compromises your personal information, we will notify affected users and the appropriate authorities without undue delay, as required by applicable law.
beau. is strictly for users aged 18 and older. We do not knowingly allow anyone under 18 to use beau. If a sign-up is blocked because the person is under 18, we keep a minimal record of the blocked attempt (the date of birth entered and the sign-in identifier used) so the attempt cannot simply be repeated with a false date of birth. If we discover that a user is under 18, we close their account right away, so it can no longer be used or seen. We then delete the account and its data, including its photos, after a hold of ninety (90) days, in case the closure was a mistake or the data is needed for a safety or legal matter. If anything from the account was reported to the National Center for Missing & Exploited Children (NCMEC), the hold lasts one (1) year from the most recent report instead, because we are required to preserve that material. After deletion we keep only the limited safety and legal-compliance records described in Section 8, a block on the device so the account cannot simply be made again, and photo hashes that let us recognize the same images if they reappear. The banned-account retention described in Section 8 does not otherwise apply to terminations solely for being under 18. Our content moderation pipeline includes automated minor detection. If you believe a minor is using beau., please report them immediately through the App's safety reporting feature.
Profiles may contain links to third-party services (e.g., Spotify or Apple Music playlist URLs). We are not responsible for the privacy practices of third-party services. Interacting with embedded content is subject to that service's terms and privacy policy.
We may update this Privacy Policy from time to time. We will notify you of material changes through the App or via push notification. The "Effective date" at the top of this page indicates when the policy was last updated.
For privacy questions or to exercise your data rights, contact Beau Period LLC at:
Beau Period LLCIf you are a resident of a U.S. state with a comprehensive consumer privacy law (including but not limited to Colorado, Connecticut, Virginia, Utah, Texas, Oregon, Montana, Delaware, New Hampshire, New Jersey, Iowa, Tennessee, Indiana, Florida, and Maryland), you may have rights similar to those described above for California residents, including the rights to access, correct, delete, and obtain a portable copy of your personal information, and the right to opt out of targeted advertising or profiling. Beau Period LLC does not engage in targeted advertising or profiling that produces legal or similarly significant effects, and does not sell personal information. To exercise applicable rights, contact hey@beauperiod.com. If applicable law gives you the right to appeal our decision on a privacy request, you may appeal by replying to our decision email with "Privacy Appeal" in the subject line, or by contacting hey@beauperiod.com.
beau. is operated from the United States. By using the App, you understand that your personal information will be processed and stored on servers located in the United States. If you access the App from outside the United States, you consent to the transfer of your information to, and processing of it in, the United States, where data-protection laws may differ from those of your jurisdiction.
The beau. website at beauperiod.com is hosted on Cloudflare. Our pages set no cookies and use no advertising trackers, no retargeting pixels, no cross-site tracking, and no third-party behavioral analytics, and we do not build visitor profiles from website activity. Like any website, serving it means our infrastructure providers necessarily process limited network information about each request (such as IP address, browser type, and request metadata) to deliver and protect the site. Some pages, such as the public Spaces directory and the event and Space share pages, are generated from our database, so requests for those pages and their public images also reach our database and storage provider (Supabase) the same way. We do not use any of this to identify or track visitors. The site links to the App Store and Google Play.
Zip codes and the waitlist. Earlier versions of the App asked for a U.S. zip code during onboarding and, where beau. had not yet opened, offered an in-App waitlist. beau. is now available throughout the United States: the App no longer asks for a zip code, there is no waitlist screen, and nothing new is added to the waitlist. beau. has now opened everywhere in the United States, so we no longer send waitlist notices. A waitlist entry held only information that was already on file:
Area-growth notice. If you paused your account and asked us to tell you when your area grows, we keep that request so we can send you one notice, by the channel you chose (email or text), when it does. If you ask us again to email you when your area grows, that counts as asking again.
Unsubscribing from email. Every marketing email from beau. ends with an unsubscribe link. Opening it unsubscribes that address, and we stop sending it marketing email. You can also reply "unsubscribe" to any email from us. To honor that, we keep a scrambled (hashed) form of the address on a do-not-email list, not the address itself, even if you delete your account. Unsubscribing doesn't affect your account, sign-in codes, or messages about your account or safety.
On the waitlist screen in earlier versions of the App, you could optionally opt in to also receive that launch notice as a text message by tapping the affirmative SMS-consent option. Opting in was off by default; if you did not opt in, we will not text you about your waitlist status.
Purpose. Waitlist data is used solely to notify you when beau. launches near you. We do not use this data for marketing unrelated to beau.'s launch and we do not share, sell, or transfer it to third parties.
Retention. A waitlist entry is deleted ninety (90) days after the launch notice for your area was sent, and within a day of when you finish signing up. If we sent you that notice by text, we keep a minimal record of your consent (a hashed form of your phone number, when you opted in, and when we texted you) for four (4) years, so we can show you agreed to the text if it is ever questioned; it is used for nothing else.
Your rights. You can request deletion of your waitlist entry at any time by deleting your account in the App, or by emailing hey@beauperiod.com. We will confirm and delete within thirty (30) days.
In accordance with Apple's App Store privacy disclosure requirements, our App's privacy practices are summarized on the Apple App Store product page (under "App Privacy"). On Android, the equivalent disclosures appear in the "Data safety" section of our Google Play Store listing. The data types we collect, how they are linked to you, and how they are used are reflected in those store disclosures and described in detail in this Privacy Policy, with which they remain consistent.