Privacy policy.

Public community activity

Community posts store your display name, message, submission time, and a keyed hash of your IP address for abuse prevention. Posts are public: do not include private or sensitive information. Public Twitch and Kick chat may appear with its platform, username, message, and timestamp.

Reactions and game votes use a hash of a random browser-session identifier so you can update your choice. Totals are public. Daily totals reset at midnight UTC; earlier records may remain stored.

Community accounts & remembered sign-in

Twitch and Kick sign-in stores a website account ID, display name, provider account ID and username, and an avatar URL where provided. Linked identities let you use connected providers for the same account. Your provider handles your password; we do not request it. Provider access and refresh tokens are encrypted in server-side session storage to maintain and validate access.

Eligible customer sign-ins use an essential cookie to remember access for up to 30 days. Provider revocation, blocking, expiry, or clearing cookies can require another sign-in. Sign out on shared devices. Recent signed-in activity is briefly recorded for the administrator's active-customer view; it is separate from public community activity.

Private business inquiries

Guests provide a full name, email address, project type, and project description. Budget and timeline are optional. We temporarily store the draft while you verify your email, then store the inquiry and its messages when submitted. Community members can use their existing account without guest email verification.

We use inquiry details to discuss your project, answer questions, and manage the conversation. Only the authorized conversation owner and authorized administrators can access private threads. Administrators may record private project notes, stage, priority, and inquiry source where project management is enabled. Message timestamps and read state help operate the inbox. Do not send passwords, payment card details, provider tokens, or unnecessary sensitive information.

Guest verification & email notifications

Guest access and recovery require an eight-digit email code entered in the browser where it was requested. Codes expire after 20 minutes, can be used once, and have limited attempts. Only a hash of the code is stored in the verification database. The email address, request identifiers, expiry, and temporary draft support verification and duplicate prevention. The temporary database draft is cleared when the code is successfully used; expired verification records are removed when the cleanup worker runs.

Verified guest access lasts up to 24 hours within the browser session. Recover inquiry access by verifying the same email again. Email verification never grants access to conversations owned by a separate community account.

When enabled, transactional emails deliver verification codes, inquiry confirmations, and developer-reply notifications. Reply notifications do not include private message text or access codes; open the private inbox to read replies. Delivery status is recorded for retries. Administrator notifications are controlled separately. Development and staging use private email captures for testing instead of real delivery.

Security & session records

We use form protections, rate limits, request identifiers, and IP hashes to prevent spam, duplicate submissions, and unauthorized access. Customer security records include account ID, provider, sign-in time, blocked attempts, and administrative moderation actions. If sign-in IP tracking is enabled, the server-observed IP address is included and visible only to authorized administrators. These records do not include passwords or provider tokens. Security events older than 90 days are removed on the next recorded event.

For legacy email and complimentary movie accounts, private session records include a hashed session reference, estimated browser and operating system, first and last visits, expiry where applicable, latest connection IP address, and explicit sign-out. Full browser user-agent strings are not stored in these records. Records inactive for over 30 days are removed when account management is opened. We use reasonable safeguards, but no online service can guarantee absolute security.

Cookies & external services

Our essential cookies maintain sign-in, verified guest sessions, form security, and administrator access. Blocking or deleting them may sign you out or interrupt verification. These website session cookies are not advertising cookies.

Sign-in providers, embedded streams, movie players, metadata services, and external links operate under their own privacy policies. Loading external content can disclose your IP address, browser information, and request details to the provider. Providers may use their own cookies, advertising, tracking, or redirects; we do not control those practices. You can avoid loading external content and review your browser's privacy controls. Providers may process information outside your country.

Historical accounts & payments

Website checkout and paid Movie Lounge passes have been retired. Existing email-account records may contain email addresses, hashed single-use login tokens, account status, historical pass expiry, and payment references. Historical payment records may relate to Buy Me a Coffee or Whop. We do not store payment card details. Payment providers process information under their own policies; existing supporter acknowledgements may include display names and amounts.

Relevant historical records may remain necessary for account assistance, transaction disputes, fraud prevention, or legal obligations. Retirement of checkout does not automatically delete them. Contact support about the records associated with you.

Retention & access to information

Closed inquiries and messages become eligible for deletion 12 months after closure through the retention process. Removal depends on running that process; a documented legal hold may require longer retention. A verified deletion request may permit earlier removal. Account deletion includes linked conversations unless a legal hold requires restricted retention detached from normal account access. Private project notes follow the conversation's retention rules.

Guest deletion and recovery requests require proof of ownership, not just knowledge of an email address. Other account, community, and operational records are retained as needed for their feature, security, dispute handling, or applicable obligations. Contact us about a specific record rather than assuming that signing out deletes it.

Authorized administrators access private records for support, moderation, and project communication. Hosting and email services process information needed to operate the website and deliver messages. Information may also need to be disclosed where required by law or to handle a lawful request.

Your choices & privacy requests

Contact us to request access, correction, deletion or blocking, to object to processing, or to exercise other applicable data privacy rights. Availability depends on the circumstances and applicable law; some records may need to be retained for legal obligations or disputes. We may ask for proportionate verification before disclosing or changing private records. Do not send passwords or verification codes to support.

You may also raise a concern with the Philippine National Privacy Commission. Its data subject rights guidance explains applicable rights and complaint options. Choosing not to supply required account or inquiry information can prevent us from providing that feature.

Ask A2Prince guest chat

When you open Ask A2Prince, an essential, signed, HttpOnly cookie identifies your browser without requiring a name, email, or sign-in. We derive a pseudonymous identifier using a server-side HMAC and use it to restrict access to your chat. Questions, saved replies, status, and timestamps are stored in Supabase and available to the site owner for review and answering. This chat does not read your private business inquiries or social login details.

The site owner may use the connected ChatGPT integration to review pending questions and save responses when requested. ChatGPT does not automatically monitor the queue, and new replies may take time. The owner can explicitly approve general, non-personal answers for reuse as public FAQs. Matching questions may receive those saved answers immediately; other visitors cannot browse your conversation. Approved FAQ matches do not add another question record to Supabase. These reused replies stay in memory on the current page and disappear when you reload the page. Do not submit passwords, verification codes, financial details, or sensitive personal information. Supabase and any answering service used by the owner may process information outside your country under their own policies.

Guest history and cookies normally last up to 30 days; the site owner can configure the retention period. Older questions are hidden immediately by the retention filter and become eligible for deletion by the cleanup worker. Physical deletion depends on that worker being scheduled; restricted backups may last longer. Clearing cookies, expiry, or a security-key change may make previous chats inaccessible and does not itself delete the stored records. We use IP hashes and counters for chat abuse controls; this feature does not send IP addresses or social account IDs to Supabase.

Contact support about access or deletion while you still have the browser cookie and relevant question context. We need proportionate proof of ownership before disclosing or deleting records. The current guest chat does not support email recovery.

Contact & policy updates

For privacy questions or requests, email [email protected]. Identify the relevant account or inquiry without including sensitive credentials. Material changes to this policy will be reflected in the updated date. See also our terms of use.