Privacy policy

GLP-1 Friends is a small, member-run community. It is operated by Dodo Media LLC, a California limited liability company, at 6770 Stanford Ranch Rd. #1006, Roseville, CA 95678. For privacy questions, a copy of your data, or a deletion request, email contact@glp1friends.com — a real person reads it.

Your account and everything you write live in a Postgres database hosted by Supabase, which also runs the sign-in system. Specifically:

• Sign-in details. Your email address and password, held by Supabase Auth. We never see your password. If you sign in with Google or Apple instead, we receive your email address from them and never see that account’s password either.
• Your profile. Username, display name, bio, avatar, medication, journey stage, and the date you joined. Everything except the username is optional and can be cleared in Settings.
• What you post. Posts, replies, and any photo attached to a post.
• What you do. Upvotes, the spaces you join, the members you follow, and the dates your account was active.
• Direct messages you send and receive.
• Reports you file about content, including the reason and any detail you type.
• Your email preferences — which notification emails you want.

Most of this site is readable by anyone on the internet — signed in or not, with no account at all. That is deliberate: a community that helps people has to be findable. But it means the following are public, and you should write as though a stranger, a colleague, or a family member could read them, because they can:

• Your posts and replies, once published.
• Your profile page: username, display name, bio, avatar, journey stage, badge, and the date you joined.
• Which spaces you have joined, and who you follow.
• Which posts and comments you upvoted.
• Photos you attach to a post — see “Photos” below.

These pages are public and crawlable: anything that fetches a page can read them, including search-engine crawlers and archiving services. Once something has been copied off the site we cannot unpublish it from wherever it landed.

We do ask search engines to index the community — spaces and published discussions are listed in a sitemap, because a community that helps people has to be findable. Your profile page is the exception. We ask search engines to leave it out of their results, so that searching your name should not surface your GLP-1 history in one place. That is a request, which every mainstream search engine honours but nothing can technically enforce, and it does not hide the page from anyone who visits it directly. Individual discussions you take part in can still be indexed.

• Your email address and password.
• Your direct messages — see below for exactly who can read them.
• Your email notification preferences.
• The record of which dates your account was active.
• Reports you file: only moderators see them, including who filed them.
• Posts and replies held for review or removed: readable by you and by moderators, not by other members. The photo attached to one is the exception — see below.

Your medication is off by default and stays off until you turn it on. With the switch on, it appears in four places: your profile, the member directory, member search results, and under your name on any post you write. With it off, it appears in none of them.

The switch is enforced in the database, not just on the page. With it off, our own data layer cannot read your medication back — the value is withheld before it ever reaches a page, an API response, or a search result. The one exception is you: you can always see your own value in Settings, which is how the form knows what to show you. (This was not always true. Until 26 July 2026 the switch was applied only where a page was drawn, and the value was readable through our public data layer whether it was on or off. That is fixed, and we would rather say so than quietly rewrite the history.)

What the switch still does not do: it does not delete the value. We keep what you typed, and people with direct database access — us — can read it. If you want your medication not to be held at all, clear the field itself in Settings; that removes the value, not just the display.

Your journey stage is always public when you set one, in those same four places. The medication switch does not cover it. Leave it blank if you would rather not say.

Photos you attach to a post are stored in a public storage bucket. Each file gets a random, unguessable name, and the path also contains your account’s internal ID. Two consequences worth being clear about:

• Anyone who has the URL can open the image, with no account and no permission check. If you share the link, or someone copies it, it works for them.
• This includes photos on posts that are held for review or removed. Taking the post down hides the post; the image file behind it stays fetchable at its original URL. If a photo is sensitive and needs to be gone, ask a moderator to delete the file, not just the post.

Before-and-after photos, injection-site photos, prescription labels and pharmacy receipts are the ones to think twice about. A label or receipt usually carries your full name, and sometimes your address and prescriber.

Direct messages are private from other members: the database only ever returns a conversation to the two people in it, and message bodies cannot be edited after sending.

They are not end-to-end encrypted. They are stored as ordinary text in the database, which means anyone with database access — that is us, and Supabase as the host — can read them, and they would be exposed by a breach or produced under a valid legal order. Do not treat a DM as confidential. Anything you would not want read by a third party does not belong in one.

Every post and reply is checked automatically against a list of patterns before it goes live — this is how the no-selling-and-no-sourcing rule is enforced. Nothing leaves the site during that check and no third-party service sees your draft; it is a text match inside our own database. If nothing matches, your post publishes immediately. If something matches, the post is held and a moderator reads it.

Moderators can read held and removed content, and the reports filed about it, including who filed them. When a moderator acts on your content you get a notification saying what happened, but not which moderator did it. Reporters are never shown to the person they reported.

Administrators can see aggregate figures about the community — how many people signed up, how many were active, how many posts were written. That view is counts, not a log of what any individual read.

We use two cookies, both first-party:

• Supabase authentication cookies, which keep you signed in. Without them you would be logged out on every page.
• steady_seen, which records that today has already been counted for your account so we do not write the same row on every page you open. It holds today’s date and a short fragment of your account ID, and it expires within a day.

Your browser also stores your light/dark theme choice locally. That never leaves your device.

There are no advertising cookies, no third-party trackers, and no analytics scripts on this site. Nothing here follows you to other websites. That is why you have not been shown a cookie banner: the two cookies above are what make signing in work.

We record the dates your account was active — one row per account per day — so we can tell whether the community is alive. It records that you were here, not what you looked at — we keep no page-by-page browsing history of our own, though our host’s ordinary server logs see requests as they are served. Only you can read your own activity rows.

The site is built to email you when someone replies to you or sends you a direct message, and you control both in Settings. Notification email is switched on: replies and direct messages are emailed to you unless you turn them off, either in Settings or from the unsubscribe link at the bottom of any one of them.

When an email does go out, it is delivered through Resend. Your address is passed to them with that one message and is not stored in a mailing list or audience on their side; there is no marketing list to be added to. Reply emails contain the name of the person who replied and the title of your own post. Message emails tell you that someone wrote and how many times — never the text of the message. Every email carries a one-click unsubscribe link for that type of email.

Our error logs record account IDs when something fails, and email addresses are stripped out of any error text before it is written.

• Supabase — hosts the database, files and sign-in system. Everything above sits there.
• Vercel — hosts the site itself and receives ordinary request information, such as IP addresses, in the course of serving pages.
• Resend — receives your email address at the moment a notification email is sent, and nothing else.
• Google or Apple — only if you choose to sign in with them.

We do not sell your information, and we do not share it with advertisers or data brokers. There is no advertising on this site. These providers store data in the United States and Canada: your account, posts, messages and uploaded photos live in the database in Canada, and email delivery and error monitoring run in the United States. GLP-1 Friends is intended for members in the United States, but wherever you live, you can ask us for a copy of your data or ask us to erase it, and we will do it.

You can close your account yourself in Settings. Be clear about what that does, because it is not a full erasure:

• Cleared: your display name, bio, avatar, medication and journey stage. Your profile page stops being reachable and you are signed out on every device.
• Kept: the posts, replies, votes and direct messages you wrote. They stay where they are, attributed to a deleted member, because deleting them would gut conversations other people are still part of.
• Kept: your username, which is not released for anyone else to register. It still appears in old links and bylines, and letting a stranger inherit it would let them speak under your history.
• Kept: your sign-in record, so the address cannot be silently re-registered over a closed account.

If you want a specific post, photo or message gone before you close your account, delete it or ask a moderator first — afterwards you will no longer be able to sign in and point at it.

How long things are kept: closing your account anonymises your profile straight away, and that is not reversible. Posts and comments you left behind stay, shown as written by a deleted member, because removing them would tear holes in conversations other people are part of. Your username is never released for someone else to take. Content held for review that no moderator has acted on is cleared with the rest of your account. Database backups run on a short rolling window — seven days today — and are overwritten as it moves, so a closed account disappears from those within a week. If you want everything gone rather than anonymised, including posts we would otherwise keep, email contact@glp1friends.com and ask.

You can see and change most of what we hold from Settings: your profile, your medication switch, your email address, your password, your email preferences, and closing your account. For anything beyond that — a copy of your data, or erasure of content we would otherwise keep — email contact@glp1friends.com and we will answer within 30 days.

Dodo Media LLC is a California company, and we handle access and deletion requests the way California’s privacy law describes them — whether or not we are large enough to be covered by it. We are not going to use our own size as a reason to refuse someone their data. If you think we have handled a request badly, you can complain to the California Attorney General. Wherever you live, the same route and the same 30 days apply.

GLP-1 Friends is for adults. You must be 18 or older to create an account. We do not ask for or verify a date of birth, so this is a condition of use rather than something the site checks — we are telling you the rule and the limit of how it is enforced. If we learn an account belongs to someone under 18, we will close it.

This is a draft and it will change, starting with the highlighted gaps above. When it changes materially we will say so rather than quietly editing the page, and the “last updated” date at the top will move.