Last updated: October 15, 2026. Draft, pending legal review.
OkMaybe is run by OKMAYBE, LLC, an Oregon limited liability company at 1929 SW Carter Lane, Portland, OR 97201 ("we", "us"). This policy explains what we collect and what we do with it.
We collect only what OkMaybe needs to work: your phone number, the name you choose to go by (a first name or nickname is enough), what you post, the people you choose to add and the choices they make about hearing from you, records of how the app is used, which never include what you wrote, and, if you write to us, what you send and how to reply to you. We never upload your address book; only the people you pick are saved. No ads, no advertising identifiers, no selling of data, no AI reading your posts. No other company or app can reach your data through an API or integration; the only outside companies that handle it are the service providers that run OkMaybe, listed below. In the app's Settings you can export your people, topics, posts, photos, and replies, or delete everything; you can also ask us by email or at okmaybe.app/delete.
Your phone number identifies you and is where texts are delivered. A friend who offers you a topic gives us your number; if you later sign in with the same number, it is the same record. We store numbers in a standard international format. When you sign in in the app, Google's Firebase Authentication texts you the code.
Two kinds. The name you choose to go by when you sign in (a first name or nickname is enough), which is shown to the people you share with, including in the digest texts and notifications they receive, such as "Maya and Sam shared with you". Those texts pass through our text-message provider and the reader's carrier, and can appear on the reader's lock screen. Notifications pass through Apple's push service and Google's Firebase Cloud Messaging and can also appear on the reader's lock screen. Notifications can show topic names; to keep them off your lock screen, set Show Previews to When Unlocked in your phone's notification settings. You can change this name in Settings at any time; the new name replaces the old one wherever OkMaybe shows it, but texts already sent keep the name they were sent with. If you saved someone under your own name for them, you see that name instead of the one they chose. And the name a friend picks for you from their own contacts when they add you, which is stored only on that friend's list and is never shown to anyone else, including you. If you reply to someone's post, or hearted it, your name, or the name they saved for you, can appear in the digest text or notification they receive, such as "Sam replied to you" or "Sam loved your post".
If you choose to add one, a photo shown in the circle beside your name. It is optional; the app offers it once when you first sign in, and you can add, change, or remove it in Your profile. Your phone shrinks it to a small square and removes its location, camera, and time data before it reaches us. We use it only to show it as "Who sees what" describes. We don't use it to recognize faces, derive anything from it, advertise, or train any AI.
You pick people with your phone's contact picker, or type a number and a name; only the people you pick reach us. On iOS 18 and later, you share contacts with OkMaybe by tapping them in a search; on your phone, OkMaybe reads only the name, company name, and phone numbers of contacts you shared, only to search them. Removing someone from My people doesn't unshare them; you can change that in your phone's Settings. We never upload your address book. The numbers and names of the people you pick are stored on your own list. We use them only to deliver what you asked for: to offer those people your topics and to show them to you. We never use them to suggest people to anyone, to match them with other people's contacts, or to market to them.
When a friend adds you, they give us your phone number and the name they know you by. We text you nothing because of it: nothing reaches you until that friend texts you from their own phone, and our number texts you only after you choose to hear from them. The app prepares the friend's text, which can name the topic they're sharing, and they can change it before they send it; it comes from their phone and number, never ours. If several friends add the same number, it points to one record, so each of them is linked to the same person; none of them can see that the others added you, or the names they gave you. If you never sign in and never choose to hear from anyone, we delete your number and your record 12 months after a friend last added, offered, or invited you, or sooner if every friend who added you removes you. We keep only the records listed under "Data retention" as remaining after deletion: a record of any choice you made on an invitation page, a record that your number opted out, and, if you asked, a scrambled copy of your number so it is never added again. If someone blocks you, we don't delete your number and record after those 12 months: we keep them, with what friends gave us about you, for as long as the block exists, even if you never sign in, so the block keeps working. Nothing is sent to you because of it. If you ask us to delete your number, we delete it and every block naming you, so the block ends. You can ask us to delete it at any time, without signing up, by emailing hello@okmaybe.app from or about your number, and you can ask that it never be added again.
Text, photos, and links you post to a topic; replies between you and the author of a post, and the author's hearts on them; hearts on posts. A reply appears in the app and in the digest of the person it is addressed to, never in anyone else's. When you add a link, even before you post it, our server visits it to make a preview, so the site receives a request from our server and can tell that the link was opened. The preview (title, description, and image) is stored with the post, and kept in a shared cache for about 7 days even if you never post it; the cache does not record who added the link.
You can also post a spot, an offer to do something together, or an Ask, a question, with the details you set for it. When you answer a spot OK or Maybe, we store your answer and when you gave it, and a record of each change for 30 days. Your answer is deleted with the spot or your account, or if you are removed from its topic, or if you or the host blocks the other.
Which topics you accepted and how often you chose to hear about each one; the day you prefer weekly digests; your time zone, taken from your phone or browser each time you open OkMaybe so digests arrive in your morning; whether your digests come as texts, as notifications, or not at all (Off), and whether you want notifications when someone replies to you, hearts your post, or posts a spot or Ask; whether you opened a digest, which your Earlier digests list shows you as a dot until you do, and whether you replied to a post a digest carried, both stored with your record and otherwise used only in aggregate; when you were last active in OkMaybe, which a sharer sees as a time once you have answered one of their invitations, as "Who sees what" explains; and when you last opened each reply thread, which only you and our servers can see and which we use only to mark what's new.
When you ask for a code on an OkMaybe invitation or digest link in a browser, we text it to your number to confirm it is you. Once confirmed, the browser keeps a random identifier in a cookie, and we store a scrambled copy of it with your record, with when you confirmed it and which version of the Terms you agreed to by confirming. Without another code, that browser can then show and change your choices, show posts in the topics offered to you, show your replies and who they are with, show your earlier digests, and send replies as you. Anyone using that browser can do the same, so confirm only a browser you alone use. To stop that, tap "Not you? Forget this browser" at the foot of our web pages, which deletes our copy at once, or email hello@okmaybe.app and we will forget every browser remembered for your number. Otherwise we delete our copy a year after the browser was last used. Clearing your cookies removes the identifier from that browser only. Our pages also keep, in your browser's local storage, whether you chose the full or compact view of posts; it is never sent to us, and clearing your browser's site data removes it.
Hiding. If you hide someone who shares with you, we keep a record of whom you hid and when, which only you can see, in Settings › Hidden people. Hiding sets each of their topics you follow to Off; for 24 hours we also keep what each was set to, so Undo can put it back. We don't tell them, but, as with turning a topic off, the number of people who receive their topic can change. The record is deleted when you show them again, when either of you blocks the other, or when either of you deletes your account.
Blocks. If you block someone, we keep a record of it: whom you blocked, when, where you blocked them from, and the name you knew them by and the number you had saved for them, if any. Only you can see it, in Settings › Blocked people, and we never tell the person you blocked. While the block exists, neither of you gets the other's topics, posts, replies, or hearts, by text, notification, or web page. Blocking removes each of you from the other's My people and from each other's topics, and permanently deletes the reply conversations between you and the hearts each of you gave the other's posts. Unblocking does not bring them back. A block ends if either of you deletes your account, or if the person you blocked asks us to delete their number.
Reports. If you report a post, a reply, or someone's profile photo, we store your report: what you reported and your reason and note; for a post or reply, who wrote it, with their name and number, and a copy of the post, or of the reply and the conversation it is in, made when you report it; and for a photo, which photo it was and the person's name and number. A reported photo is kept, seen only by the people who run OkMaybe, until we close the report, even if its owner changes or removes it or deletes their account; if we take it down we keep a copy with your report, and if we don't, we delete it. If we take down what you reported, we also keep a copy of its photos with your report. That copy is kept even if the content is later deleted, including by a block or by either person deleting their account. Your report reaches the people who run OkMaybe as an email in our mailbox at Zoho Mail, with its text, in which web addresses are altered so they can't be clicked, but never its photos or link previews. The email never contains the photo; it links to it in a place only the people who run OkMaybe can open. The email copy in our mailbox, including your note, is deleted on the same schedule as the report. The person you reported is not told who reported them.
If you ask for an invite on okmaybe.app, we receive your email address and, if you give it, your name. If you use Send feedback in the app, we receive your message, the name on your account, an internal reference to your account, and the app version, never your phone number unless you type it. Either one reaches us as an email in our mailbox at Zoho Mail. We use an invite request only to reply to you and send the invitation you asked for, and feedback only to reply to you and improve OkMaybe; we never add you to a mailing list. If we invite you to test the app, we give your email address to Apple so it can send you the TestFlight invitation. To stop repeated invite requests, we count the requests from each email address and each internet address for one day, under a scrambled code that contains neither, and then delete the count. In feedback, please leave out health or other private details; we don't need them. If you ask to delete your account at okmaybe.app/delete, we receive your phone number, your email address, and whether you asked not to be added again, as an email in our mailbox. We use them only to confirm and carry out the request, and delete the email once it is done. We count requests from each email address, internet address, and phone number for one day, under a scrambled code that contains none of them, and then delete the count.
If you allow notifications from OkMaybe, your phone gives the app a token, a random code that lets Apple's and Google's push services deliver notifications to this installation of the app. We keep the token of the phone you used most recently with your record, with the type of phone, the app's build number, whether notifications are allowed, and when it last changed, and use it only to send the notifications you chose. To make the token, Google's Firebase Cloud Messaging uses an identifier for this installation of the app; it is not an advertising identifier. When you sign out, the app removes the token from our servers; if someone else signs in on that phone, it moves to them; it is deleted with your account. Turning off notifications for OkMaybe in your phone's Settings stops them at once.
Which features are used. The app records events such as creating a topic or choosing a cadence, each as a count or a fixed choice, never the words of a post, a name, or a phone number. Google Analytics for Firebase adds an identifier for this installation of the app (it is not an advertising identifier and changes if you reinstall), your device model, operating system, language, and app version, and an approximate location worked out from your internet address. When you sign in, these events are linked to the internal identifier of your record, never your phone number, and we note the installation identifier on your record so we can delete its events with your account. If the app crashes, it sends a crash report to Google's Firebase Crashlytics: the stack trace, which shows where in the app's code the crash happened, your device model, operating system, and the app version, an identifier for this installation of the app, and the app's most recent usage events described above; never the message of an error in the app's own code, what was on the screen, your name, or your phone number. A crash report does not include the internal identifier of your record, and Google keeps it for about 90 days, even if you delete your account sooner. Google Analytics for Firebase also records that a crash happened, as one of the usage events above, and like them it is linked to the internal identifier of your record.
Our servers also record events such as sending or opening a digest or changing a cadence, under the internal identifier of your record and never your phone number, whether or not you use the app.
There are no advertising identifiers, and nothing is used for advertising.
In the app, Google Analytics for Firebase collects the usage information described above for us, and Firebase Crashlytics collects the crash reports described above. Firebase Cloud Messaging uses an installation identifier only to deliver notifications. No other company collects information about your use of OkMaybe through the app. Photos on our pages load from Google Cloud Storage, which hosts OkMaybe's files; no other company's code runs on our pages. OkMaybe does not track you across other sites or apps, so a browser's Do Not Track signal changes nothing about how we handle your data.
We do not use your content to train any AI, and no AI service reads your posts or replies.
This is the part most privacy policies skip, so here it is plainly.
We do not sell your personal information, to advertisers, data brokers, or anyone else, and we do not share it for advertising.
If you don't use the app, the first text from our number is usually a confirmation code, sent when someone asks for one on an invitation or digest link addressed to your number. Usually that is you. If it wasn't, ignore it or reply STOP.
You receive digest texts from our number only if you chose a cadence for at least one topic, on your invitation page or in the app. Signing in or creating a topic never starts them; a topic you create sends you no digest until you choose one. If you turn on Your digest for a topic you created, your digest tells you about replies to your posts there. A digest may also mention, in the same text, a new topic that another person has offered you. We also send a fresh link when you tap "Text me a new link" on an expired page.
If you use the app and allow notifications, your digests come as notifications instead of texts, and we don't text them to you. You can choose Texts in Settings, or when you first choose how often in the app; we show you what you're agreeing to first, and texts start only after you tap Get texts. Choosing Daily, Weekly, or Monthly in the app never starts texts on its own; only Get texts does. If you replied STOP, texts stay off until you reply START. If notifications stop working, your digests wait until you turn notifications back on or choose texts.
You can also turn digests Off in Settings, or when you first choose how often in the app: no digests are sent by text or notification, and your topic choices are kept for when you turn them back on.
At most 1 text a day about what people shared, depending on your choices, plus codes and links you ask for, and a text if a spot you said OK to is cancelled or no longer happening; rarely, that can mean a second text in a day. Message and data rates may apply. Reply HELP for help, or STOP to stop all texts from our number, about every person and topic.
Reply STOP (or tell us in any way, including by email at hello@okmaybe.app) to stop all texts from our number, about every person and topic. We keep a record that your number opted out, even after deletion, so we don't text it again. Reply START to turn texts back on. STOP doesn't stop a friend texting you from their own phone: their texts, invitations included, come from their phone, not from us. To have your number deleted, or never added by anyone again, email hello@okmaybe.app.
If you text our number, our system checks the text only for STOP, START, or HELP and does not store it. To other texts it sends one automatic reply, at most once a day. To handle each text once, we keep a scrambled code for the message for 30 days (for a START, as long as OkMaybe operates) and, if we sent that reply, a scrambled code for your number for 2 days. Twilio keeps the text in its message logs under its own retention policy.
Data is encrypted in transit and at rest. Every read and write is checked against who you are. Web links are scoped to one person and one purpose and expire after 30 days. An invitation link shows or changes your choices, and shows posts and replies, only in a browser you have confirmed with a code sent to your number, so the friend who sent it cannot use it as you. A digest link shows that digest's posts to anyone who has it, so treat it as private. Pasting a link into another app can let that app's company fetch it. Access to production data is limited to what is necessary to run the service. If OkMaybe's founder can't run it, a person he has named, and a developer they appoint under a confidentiality agreement, may access OkMaybe's systems only to keep it running.
These apply to everyone, wherever you are.
To exercise a right the app doesn't cover, email hello@okmaybe.app.
If you asked for an invite or sent us a message without an account, email hello@okmaybe.app and we will tell you what we have or delete it.
If you live in California, Virginia, Colorado, Connecticut, Utah, Oregon, Texas, or another state with a privacy law, you have rights to know, correct, delete, and opt out, and to appeal our decisions about your requests. We do not sell or share personal information for cross-context behavioral advertising.
Private replies are visible only to the people in the thread, and we do not use what you post or reply to profile you or to infer anything about you.
Some records remain after an account is deleted, or after we delete a person who never signed in:
If OkMaybe is sold or handed to a new owner or operator, we will tell you at least 30 days before the new owner can use your information, in the app, on this page, and in a notice at the top of every OkMaybe page you open, and you can delete your account, or ask us to delete your number, before then. The new owner must keep the promises in this policy. If something happens to OkMaybe's founder, a person he has named keeps OkMaybe running on the same terms while a new owner is found, and the 30 days' notice still comes before any new owner takes over.
OkMaybe accounts are for people 13 or older, and people under 18 need a parent's or guardian's permission. OkMaybe is not for children under 13. We do not knowingly collect information from them, and if we learn that we have, we delete it. If you believe a child under 13 has given us information, email hello@okmaybe.app and we will delete it.
Your data is processed and stored primarily in the United States by our service providers.
We may update this policy from time to time. We will tell you about changes in the app and on this page, not by text. If we want to use data we already hold in a materially different way, we will ask you first. Other changes take effect after notice in the app and on this page.
Email hello@okmaybe.app, or write to OKMAYBE, LLC, 1929 SW Carter Lane, Portland, OR 97201. We aim to respond within 48 hours.