Privacy Policy

How SayYes handles your info

Last updated: August 2026

SayYes is a small, independent project that helps people — mostly lovers, crushes, and people working up the nerve to ask someone out — send a fun interactive invite and get a clear yes or no back. It isn't a big company product, and it doesn't try to collect more about you than it needs to run that one job. This page explains, plainly, what that actually involves.

Who runs SayYes

SayYes is built and run by a single independent developer, under the working name Malti (short for "Multiple Category"). Malti is not a registered company — it's a personal/working name for this one-person project, not a legal entity.

What we collect

  • If you sign in with Google (needed to publish a request and see your dashboard): your name, email address, and profile picture, provided by Google. That's only used to know which requests belong to you — we never see or ask for your Google password.
  • When you create a request: the title, your name, the recipient's name, and whatever content you put into each stage (questions, choices, images, notes).
  • When someone responds: their answer to each stage, and whether they accepted or declined.

Names are not verified — on purpose

"Your name" and "recipient name" are just text boxes. We don't check IDs, verify emails for the recipient, or confirm anyone is who they say they are. This keeps the app simple and low-friction — but it also means you shouldn't treat anything in SayYes as a verified record of someone's identity.

Live Pulse — names are hidden

The public "Live Pulse" feed on the homepage and dashboard shows real accept/decline activity, but never a name in full. Names are partially masked with asterisks at random positions (e.g. Claire might show as Cl***e), and a request that was merely sent is never shown there at all — only a final accepted or declined outcome, after the fact.

How your data is used

Solely to run the invite: building it, generating your private share link, delivering the stages to whoever opens that link, recording their response, and showing you the result on your dashboard. We don't sell your data or share it with marketers. The services involved in running SayYes are Google (for sign-in) and Cloudflare (who host the site and store the data).

Advertising (not yet, but planned)

SayYes does not show ads today. To help cover hosting costs, ads may be added in a few places — for example, near the top of the request builder page, or below the live preview — in the future. If that happens, the ad slots will likely be served by a third-party ad network (such as Google AdSense), which may use cookies or similar technology of their own to show and measure ads. We'll update this policy when ads actually go live, including which network is used and what that means for you.

🕐 Your data will not stay forever — please read this part

SayYes runs on free-tier hosting with limited storage. To stay within that limit, the database is cleared out periodically — this could happen every month, or sooner, without individual notice. In practice: once your invite has been answered (or some time has passed), assume the data is temporary and will eventually be deleted for good.

Please don't treat SayYes as a permanent record of anything sentimental. If a response matters to you, take a screenshot — we can't promise it'll still be there later.

Keeping your link safe

Each invite is protected by a private, hard-to-guess link rather than a public listing — it isn't searchable or browsable. That said, anyone who has the link can open and respond to that invite, so treat it like you would any private message: don't post it somewhere public.

Local storage & cookies

SayYes uses your browser's local storage to remember your sign-in session and cache your requests so pages load quickly. This stays on your device — clearing your browser data clears it too.

Age

SayYes isn't directed at children and shouldn't be used by anyone under the minimum age required to create a Google Account in their country.

Changes to this policy

This is a small, evolving project, so this page may change as SayYes changes. The "Last updated" date at the top will reflect the latest version.

See also: Terms & Conditions