← Home

Privacy

Privacy Policy

This policy describes the information the current service collects, why it is used, and the choices available to you.

Last updated: 20 August 2026

Creator information

We collect the display name or nickname you enter, your public slug, a securely hashed creator-access token, profile settings, first-party acquisition or referral attribution, and Razorpay payment and order identifiers. We use these to create and protect your profile, operate sharing and attribution, show your dashboard, and verify paid access.

Respondent information

We store questionnaire answers and any optional written message submitted to a profile. The 18+ confirmation is kept in the respondent’s local browser for the age-gating experience rather than used as an identity check.

Anonymous experience and its limits

The respondent flow does not ask for an account or display a respondent identity to the creator. No internet service can promise absolute anonymity: necessary infrastructure and security logs may contain limited technical information, and legal or security circumstances may require investigation. Avoid including identifying or sensitive personal information in written responses.

Payments and providers

Razorpay processes payments. We store payment and order identifiers needed to verify and reconcile access, but we do not store card numbers, UPI credentials, or other payment credentials handled by Razorpay. Supabase provides database infrastructure. The deployed hosting provider may process necessary request and security logs. We do not claim or add providers that are not used by the deployed service.

How information is used

Information is used to provide profiles and insights, prevent unauthorized creator access, operate response controls, attribute first-party referrals, verify purchases, troubleshoot failures, protect the service, and respond to support, privacy, abuse, or legal requests.

We do not sell personal information.

Retention and security

We retain profile, response, operational, and payment-reference data while needed to provide the service, resolve disputes, prevent abuse, meet legitimate business or legal needs, and maintain records. Retention may vary by category. We use access controls, token hashing, restricted database structures, and server-side payment verification, but no security measure eliminates all risk.

Controls and requests

Creators can disable optional written responses and hide or report individual messages. To ask about access, correction, deletion, a privacy concern, or an abusive response, use the Contact page. We may need enough information to verify that a request relates to the relevant creator profile; respondent anonymity can limit our ability to locate a particular submission.