Privacy notice
Effective October 30, 2026 · Version 2026-10-30.2
Operator: Zoetic Ally pty ltd, Australia. Contact: weloveyes@zoetic.ai.
1. The current service
YesOrNo lets adults create public yes/no questions and voluntarily respond. Zoetic Ally pty ltd determines how the service’s account, security, response and reporting data is used. A publisher chooses the question and who sees the shared link. Do not include anyone’s personal, sensitive or confidential information in a question or description.
The current beta does not enable paid checkout or collect launch-notification emails. We do not install advertising pixels, sell personal information, share it for cross-context behavioural advertising, run targeted advertising, or make automated decisions about eligibility for employment, credit, housing or other essential services. Public questions may be copied by visitors; public does not mean free of privacy or intellectual-property rights.
2. What we collect and why
| Data | Purpose and basis where GDPR/UK GDPR applies |
|---|---|
| Workspace identifier, a one-way recovery-key hash, creation/last-use times and publishing terms acceptance | Provide and secure the workspace you request; performance of the publishing service and legitimate interests in security. We do not store your raw recovery key. |
| Question, description, optional offer price, theme, status and publishing time | Publish and manage the content you expressly choose to make public; provide the service. You must have lawful grounds and permissions for your content. |
| Yes/no response, time, a pseudonymous browser-cookie hash and a fixed source label | Record the requested vote, prevent duplicates and show aggregate results. Legitimate interests in service integrity and security. The hash is personal data where it can be linked to a person; it is not claimed to be anonymous. |
| A keyed IP hash and short-lived rate-limit counters | Reduce abusive requests and protect availability; legitimate interests in security. The application does not store a raw IP address in its voting or workspace tables. |
| Report details, campaign reference, time, issue category, good-faith statement and optional name/reply email | Investigate privacy, safety and legal concerns, communicate a response and maintain necessary evidence; legitimate interests and applicable legal obligations. Do not put sensitive documents in reports. |
| Support messages and contact details you choose to email | Answer your request, handle complaints or comply with applicable duties. Our support mailbox and its provider process these messages. |
| Hosting request/security logs | Hostinger and its infrastructure providers may process IP addresses, browser/request information, URL paths, security events and necessary security cookies to deliver and protect the service. |
We collect information from you, your browser, publishers who supply public content, and our hosting/security providers. A fixed source such as “newsletter” or “producthunt” is a response label, not verified identity or a record of all your browsing. Unknown/custom labels are reduced to “other”. We do not build advertising profiles or use questions and votes to train an AI model.
3. Device storage
Browsing the landing page or guides does not cause our application to start a workspace session or write a new voter cookie. Security/session storage starts when you request an interactive function. A voter cookie starts when you submit a vote. A draft is saved on your device only if you turn on the optional save-draft control. See the cookie inventory for purposes, durations, legacy-cookie handling and clearing instructions. Hostinger can use separate security measures.
4. Who receives information
Public question content and aggregate results are visible to anyone with the link. A creator receives response totals and source counts, not the voter cookie or IP hash. Permitted result downloads contain aggregate counts, not individual response timestamps or visitor identifiers. Authorised operator personnel and necessary hosting/support providers can access records for the purposes above. We can disclose limited data when required by a valid legal obligation, to protect rights/safety, or in a genuine business transfer subject to applicable safeguards and notice. We do not grant a general licence to unrelated advertisers.
Current provider: Hostinger, for hosting, security, application storage and backups. Hostinger’s data-processing addendum and privacy policy describe its processing and sub-processors. Stripe and an email-delivery provider will receive transaction or notification data only if the corresponding features are activated after a separate readiness review and updated collection notice. No card data is collected by this application now.
5. International processing
The operator is in Australia. The hosting panel currently identifies the application server as Singapore and its backup location as Mumbai, India. Support and infrastructure processing can involve other countries listed by the relevant providers. These countries may have different data-protection laws. Hostinger’s published DPA includes EU standard contractual clauses and a UK transfer addendum where applicable; the applicability and any additional safeguards depend on the processing and law. Contact us for information about the safeguards relevant to your data. We do not claim that using a provider’s DPA alone establishes compliance in every country.
6. How long records remain
| Record | Application rule |
|---|---|
| Security session | Browser-session cookie; server-side session expires after two hours of inactivity and is removed by cleanup. |
| Voter cookie | Up to 30 days after issue/renewal; you can clear it sooner. A legacy beta cookie is shortened when it next reaches the application. |
| Optional draft | Up to 14 days on the device; expired drafts are discarded on the next builder use, or immediately when you remove them. |
| Rate-limit counters | Expiry is no more than one day after creation; expired counters are removed on cleanup. |
| Questions and their responses | Removed after 180 days without a new response, or sooner through workspace deletion, subject to a documented legal hold. |
| Inactive empty workspace | Removed after 365 days without use, unless linked active plans or a documented hold require review. |
| Content reports | 90 days unless necessary for a documented investigation or legal hold. Restricted access; not public. |
| Notification records if later enabled | Unconfirmed requests expire after 24 hours; confirmed entries are removed after 180 days or earlier withdrawal, subject to necessary compliance evidence. |
| Minimal financial references if payments later open | Up to seven years for company financial records, or longer only where law or a documented dispute requires it. Deleting a workspace separates its content from retained financial references. |
| Deletion audit hashes | 400 days; contain a keyed subject hash, record type and date, without question text, email or recovery secret. |
Application cleanup runs during service activity and can be run by the operator. Long-lived pre-existing records have a 30-day transition period from installation of this release before automatic expiry applies. Provider logs, support mail and backup copies have separate retention controls; deletion from the live database does not immediately erase provider backups. Those copies must remain restricted and expire under provider retention, and relevant deletions must be reapplied after a restore. Ask us about a specific record or backup; do not rely on the beta as permanent storage.
7. Your choices and rights
Privacy controls let you download/delete votes linked to this browser, export an open workspace, delete a workspace with its recovery key, remove saved drafts and clear application cookies. Deletion can change aggregate vote totals. Clearing a cookie first can prevent us from automatically matching older votes. We do not use invasive fingerprinting to rebuild a deleted identifier.
Email our contact above for access, correction, erasure, objection, restriction, portability, withdrawal, an appeal or a complaint. The rights available and exceptions depend on applicable law. We offer these request routes to visitors globally and do not discriminate for exercising rights. We use proportionate verification and do not request government identity documents by default. We aim to respond within 30 days and follow shorter legal deadlines where they apply; any lawful extension, refusal or permitted fee will be explained.
You may complain directly to your local supervisory authority, including the OAIC in Australia, the ICO in the UK, or your local EU/EEA or other regulator. You do not need to contact us first. We do not sell/share data for cross-context advertising, so there is no advertising sale/share to opt out of; Global Privacy Control does not cause us to introduce tracking.
8. Children, security and changes
The service is for adults 18 or older and is not directed to children. We ask for an adult declaration rather than a birth date or identity document. If you believe a child supplied personal information or appears in a question, contact us so we can restrict and investigate it. A declaration does not substitute for the operator’s duty to assess actual child access and applicable safety law.
We use HTTPS, limited access, one-way key hashes, protected application storage and request controls. No online system can promise perfect security. If a breach occurs, we will investigate, mitigate and make notifications required by the applicable law. Material changes will be identified with a new effective date and, where required, a notice before the change or fresh consent. We do not treat a privacy notice as blanket consent to new purposes.