Privacy

• No advertising. MaybeOS carries no ads and never will. Nothing here is funded by attention.
• No analytics or tracking. There is no Google Analytics, no tag manager, no Meta pixel, no session recorder, no heatmap tool, no product-analytics SDK. Not configured off — not present.
• No selling or sharing. We do not sell, rent, license or trade member data, and we do not share it with anyone for their own purposes.
• No tracking cookies. MaybeOS sets no advertising or analytics cookies. Signing in stores a session token in your browser so you stay signed in; that is all it is for.
• No IP addresses sent anywhere. Your network address is not passed to any third party, including our error-reporting service — not merely unused, but explicitly refused on every report, so nobody downstream can resolve it to a location.
• No cross-co-op profiles. Co-ops are walled off from one another in the database itself. Belonging to two co-ops does not merge you into one profile, and what you tell one is not visible to the other.

MaybeOS is software your co-op runs. Its organizers can see what they need to run it: who is a member, what people have booked and signed up for, what is owed. That is the ordinary business of a membership organization.

Other members see far less. A member cannot see another member's email address, phone number, billing details or subscription status. Being in the same co-op does not hand you the membership list. Only admins and staff see contact details, because contacting members is their job.

Search works the same way: you cannot search by email address, because that would answer “is this person a member here?” for anyone holding a list of addresses to try.

Some co-ops measure whether their work is doing what they hoped. If yours does, two rules hold:

• Answering is optional, always. Every demographic field can be skipped individually, and “prefer not to say” is a real answer that is counted separately from silence. You can delete your profile at any time and the figures recompute without it.
• Organizers never see individual answers. They see aggregates only — and any group smaller than five people is suppressed automatically, so a small category cannot be narrowed down to a person. That suppression is not a setting anyone can switch off.

Demographics are attached to your membership of one co-op, not to you as a person. Telling one co-op something is not telling another.

MaybeOS cannot run without a few specialist companies, and pretending otherwise would be the dishonest part of a privacy policy. Each one sees only what its job requires:

• Supabase — hosts the database. Everything stored lives there.
• Netlify — hosts and serves the application.
• Stripe — processes payments. Sees what it needs to take a payment: name, email, payment details. MaybeOS never sees or stores your card number.
• Postmark — delivers email. Sees the address and the message, because that is what sending email is.
• Sentry — receives error reports when something breaks. A report identifies you by an internal account ID, never your name or email address, and is cleared when you sign out. No IP address is sent, and none is inferred: we explicitly refuse the network address on every report, so error reporting cannot be used to locate anyone. Web addresses and the trail of actions leading to an error are stripped of sign-in links and tokens before they are sent.
• Google Calendar — only if your co-op connects a room calendar, and only for that room's bookings.

MaybeOS is open source under the Apache 2.0 license. You can read exactly what it does with your data, and a co-op that wants to can host it itself, on its own infrastructure, with no involvement from us at all. A privacy promise you can verify is worth more than one you cannot.

Ask and we will tell you what is held about you, correct it, or delete it. Deleting a demographic profile takes effect immediately and removes it from every figure it fed. If your co-op leaves MaybeOS, its data goes with it.

Questions, or anything here that does not match what you have seen: c@maybeitsfate.com.

If this statement changes in a way that affects what is collected or who sees it, we will say so rather than quietly reissuing the page with a new date.