Know exactly what we touch,
and how to switch it off.

Exactly what we read,
and nothing more.

1. Your public schedule. We read the public schedule page of your booking platform (Momence, Mindbody, or Mariana Tek): class names, start times, instructor names, substitutes, cancellations, spots left where the page shows them, and the instructor photos your booking profiles already display. It is the same information anyone sees when they open your booking page. We never log in to your booking platform, and we never ask for credentials to it.

2. Your brand. Your accent color (proposed from your website, confirmed by you), your logo, your typeface choice, the design you picked, up to twenty brand photos if you send them, the short class names you set, your booking line, and the other settings shown on the Home page.

3. Your Instagram connection. When you connect Instagram, you approve the connection on Instagram's own screens through the official API, and Meta issues an account id and an access token that authorize publishing stories to your account. At launch those two items are held by our posting rail, upload-post, on our behalf. We hold your Instagram handle, the connection status, and the reference that ties your studio to its profile at the rail. The token is never in our website code, never in your browser, and never in an email.

4. Your account, each night's story, and billing. Your studio name, your time zone, your contact email, and, if you add one, a second address that receives previews (the front desk). For each night: the schedule as it stood at preview time, the two rendered images (today, then tomorrow), what happened (previewed, approved, held, posted, skipped, or failed), and the rail's reference for each published frame. For billing: your Stripe customer id, subscription id, plan, and billing status. Card numbers go to Stripe and never touch our systems.

5. Email between us. The emails we send you, including the preview images inside them, and what you send us. Every email we send replies to stop@dayposter.com. Our software reads the sender, subject, and body of each message to that address to find a STOP, START, or PAUSE, and records who sent it and when. Everything else you write to us lands in our support inbox, where a person reads it.

That is the whole list. We hold no client lists, no member records, no bookings, and none of your clients' payment details.

What we can never do.

• Read your messages, comments, or followers. The connection covers publishing and basic account identity only. Your inbox, comments, and follower data are outside it entirely.
• Post anything except your schedule story. The only thing Dayposter is built to publish is the daily schedule story you were shown. There is no other content path: no captions, no feed posts, no reels.
• Change your profile, bio, or settings. Not part of the connection.
• See your Instagram password. The connection happens on Instagram's screens, not ours. Your password is never shared with us.
• Log in to your booking platform. We read the public page, nothing behind it.
• Post a day you were never shown. Nothing posts without a preview having gone out first. If you choose Auto for overnight changes, an updated story can post on top of a preview you already received; if you choose Hold for me, it waits for your tap.
• Guess. A cancelled class is always removed. An empty day never posts. A schedule page we cannot read never posts. When we hold a story and hear nothing, the day skips.
• Keep posting after you say stop. The stop flag is read again in the moment before each publish. Stop means stopped.

How every night runs,
step by step.

1. 8:00 pm, your time. We read your public schedule page, build today's story with tomorrow's as a second frame, in your brand, and send the preview by email with four links: Looks good, Skip, Pause, Stop. Do nothing and it posts on time. Reply in plain English to change something.
2. 12:00 am, your time, or the time you set. We read your schedule page again. If nothing changed, the story posts. If a class was cancelled, it is removed and the story posts. If anything else changed, your setting decides. Hold for me: we send the updated story and wait for your tap; no answer by the cut-off (six hours after your post time unless you set otherwise) and the day skips. Auto: the updated story posts on time. You choose between the two during setup; neither is chosen for you.
3. Every night, without exception. The second read always runs; it is not a switch you can leave off. Days off never post. Empty days never post. A broken feed never posts.

Stop means stop. Instantly.

The stop link is in every email we send, and every email we send replies to stop@dayposter.com. Either one sets the stop flag on your account before anything else happens, and you get a confirmation email every time. Our software reads that flag again in the moment before each publish, and if it cannot read the flag, that counts as stopped. If a stop arrives from an address that looks like yours but is not the one on file, we stop first and check with you afterwards. Wrongly paused beats wrongly posted. Resume with the link in the confirmation email, or reply START from your account address.

Switch it off yourself,
without asking us.

Stop posting. Tap the stop link in any email, reply STOP to any email, or write to stop@dayposter.com. Posting halts at once. Your designs, settings, and history stay exactly where they are, and you can resume whenever you like.

Pause. Tap Pause in the preview. No previews and no posts until you resume. Everything stays where it is.

Revoke the Instagram connection. In the Instagram app, open Settings, then Website permissions, then Apps and websites, and remove the Dayposter connection. The access token dies immediately and we can no longer post.

Close the account. One email closes your account and deletes everything. The steps are on the data deletion page; it is done within 7 days, and we confirm by email when it is.

Where your data lives,
and who can reach it.

• Everything runs on Cloudflare: Workers for the software, D1 for the database, R2 for images, Browser Rendering for the pictures, and Email Routing for inbound mail. Data moves over HTTPS and is encrypted at rest by Cloudflare.
• Rendered stories live in a private bucket with no public address. The preview rides inside your email, and the posting rail receives the image directly. There is no public image host.
• There is no dashboard, no login, and no password. Every link in our emails is signed and acts only for your account, only for the action it names, and only until it expires. Anyone who can open your inbox can act on those links, so treat your email account as the key it is.
• Secrets live in a managed vault, never in code. Access to production is limited to the people who run Dayposter and protected by two-factor authentication.
• We are a small company. We do not hold a SOC 2 audit today, and we will not claim badges we don't hold. What we offer instead is this short list, a working off switch, and a person who answers.

Who else touches
your data.

We update this table before adding anyone to it. No one on it may use your data for anything except the service named.

Found something?
Tell a person.

Write to hello@dayposter.com with the subject "Security". A person reads it and replies within two business days. If you report a real vulnerability, we will credit you here if you'd like.