Legal

Privacy policy

This page explains what information One question daily collects, why, and how the distinction between public and private answers actually works under the hood.

Last updated: this policy is reviewed periodically as the product evolves.

Overview

One question daily is a small, independent daily-journaling application. This policy describes the personal data processed when you use the site, whether or not you create an account, and applies to every page of the service.

What data we collect

Depending on how you use One question daily, we may process the following categories of data:

Account dataEmail address and password, managed securely through our authentication provider (Supabase Auth). We never see or store your raw password.
Profile dataUsername, full name and avatar URL, which you can edit at any time from your profile page.
OAuth dataIf you sign in with Google or GitHub, we receive the basic profile information those providers share (typically your email and display name).
ContentThe text of the answers you submit, together with the visibility setting (public or private) you chose for each one.
Interaction dataWhich public answers you have liked, so we can show your like state and the total like count.
Technical dataSession cookies required to keep you signed in, and standard server logs (such as error messages) used to keep the service running.

How we use this data

We use the data described above strictly to operate the service:

  • To authenticate you and keep your session active across visits.
  • To display your username and avatar next to your public answers.
  • To show you your own answer history, including private answers, on your personal pages.
  • To calculate and display like counts on public answers.
  • To detect and prevent abuse, such as spam submissions.
  • To communicate essential service information, such as confirming a new account.

Public vs. private answers

Every answer you submit carries a visibility setting that you choose before posting. Public answers are stored with a reference to your account and are shown, together with your username, on the corresponding question page to any visitor. Private answers are stored in exactly the same database table, but our application code never returns them to any user other than their author.

Because visibility is enforced by our application logic and, where applicable, by database-level access rules, marking an answer as private means it is not exposed through the public pages or the public API surface of the site.

Cookies

One question daily uses a small number of strictly necessary cookies set by our authentication provider to keep you signed in between requests. These cookies are read and refreshed by the site itself on every page load; we do not use third-party advertising or cross-site tracking cookies.

Third-party services

We rely on a small number of infrastructure providers to run One question daily:

  • Supabase — hosts our database and handles authentication, including optional sign-in with Google or GitHub.
  • Google and GitHub — only if you explicitly choose to sign in using one of these providers.
  • Our hosting provider — serves the application and may keep standard technical access logs.

Data retention

We retain your account data and answers for as long as your account remains active. If you delete your account, your profile information and private answers are removed; public answers may be anonymized rather than deleted outright where doing so would break the context of an existing public conversation.

Your rights

Depending on where you live, you may have some or all of the following rights over your data:

  • Access the personal data we hold about you.
  • Correct inaccurate profile information directly from your profile page.
  • Request deletion of your account and associated data.
  • Object to or restrict certain kinds of processing.
  • Request a copy of your data in a portable format.

Children's privacy

One question daily is not directed at children, and we do not knowingly collect personal data from children under the age required by applicable law in their jurisdiction. If you believe a minor has created an account, please contact us so we can remove it.

Changes to this policy

We may update this policy from time to time as the product changes. Material changes will be reflected by updating the date at the top of this page.

We encourage you to review this page periodically to stay informed about how we handle your data.

Contact

If you have questions about this policy or wish to exercise any of your rights, please reach out through the contact channel listed on our site.