BackGrinzu
Draft for review, not an effective launch notice. Operator identity, public contacts, retention details and applicable legal review must be completed before publication.

Privacy Policy

Last updated 10 November 2026

Version 2026-11-10-draft-2

Draft version 2026-11-10-draft-2. Reviewed 10 November 2026. Effective date: [TO COMPLETE: PUBLICATION DATE AFTER REVIEW].

Who is responsible for your information

Grinzu is operated by [TO COMPLETE: PROPRIETOR'S FULL LEGAL NAME], an individual business owner trading as Grinzu in India, at [TO COMPLETE: PUBLIC BUSINESS ADDRESS AND STATE]. That operator is responsible for the processing described here and acts as controller or the corresponding responsible person under applicable law.

Privacy contact: [TO COMPLETE: VERIFIED PUBLIC PRIVACY EMAIL]. Grievance Officer: [TO COMPLETE: NAME AND WORKING CONTACT DETAILS]. Applicable overseas representative details, if required: [TO COMPLETE: EU AND UK REPRESENTATIVE ASSESSMENT AND DETAILS]. These fields must be completed before this draft is published as an effective notice.

This policy applies to the current adult random video, audio and text chat service, its account and profile features, and its support, feedback and safety processes. A sign-in account is not anonymous to Grinzu, even when you use a display name with other participants.

The main points

Information you give us

Account information includes your email address, account identifier, authentication/session information and sign-in events. If Google sign-in is enabled and you choose it, we receive the account information and identity-provider details that Google supplies for that sign-in, such as name, email and provider identifier. Access to your Gmail messages or contacts is not part of the current sign-in feature. We also keep when you accepted the Terms and your account role (for example, whether an account belongs to our moderation team).

Profile information includes your display name, date of birth, selected interests and languages. Your birth date is used for the adult eligibility check and account integrity; it is not displayed to your matched participant. The current check uses a supplied date of birth and is not an identity-document or biometric verification process. Your date of birth can't be changed after onboarding. If it is wrong, reach us through Contact; we may ask you to delete your account and create a new one.

Support and feedback information includes what you write, your account reference, our replies and case status. A bug report may include the relevant page path, screen size and browser/user-agent information to help diagnose the problem. Do not include one-time codes, payment details, government identity documents or unrelated sensitive information. You can send bug reports and ideas from the Feedback page, where you also see our replies. Feedback is deleted when you delete your account. It is not a channel for safety reports or legal complaints; use Report in the app or the routes in the Safety and Complaints Policy.

Safety information includes reports, reasons and descriptions, related participant identifiers, call references, blocks, moderation outcomes, suspension records, reviewer information and appeal correspondence. Someone else may submit a report about you. A report can contain allegations or sensitive information; an allegation is not automatically treated as an established fact.

Information processed during use

To connect a conversation, we and our media provider process video, audio and in-call text transiently, together with connection/signaling data. What you show can include your face, voice, surroundings and information about others. Our current service does not use your face or voice to create a biometric identity template, a facial recognition database or an AI training dataset.

Every match starts with both videos blurred. The blur is applied on your device before your video is sent, so only a heavily pixelated image leaves it, and it is applied again on your partner's screen. Video is shown only after both of you tap Show video, and every new match starts blurred again. Audio and text work while video is blurred. The blur reduces the whole picture; it does not detect or analyse faces.

We keep call metadata such as the matched account identifiers, room/call identifier, start and end times, end reason, who ended the session, shared interests, and whether and when both participants chose to show video. These are records about a connection, not an audio/video recording or saved chat transcript. To run matching we also keep short-lived records of who you were recently matched with (so you are not matched again too soon) and the accounts you have blocked or that have blocked you.

Grins and trust

After a call that lasted at least a minute, or where both people showed video, either person can send the other an anonymous grin. We store who sent it, who received it and for which call. Your grins set your level (🌱 New here, 😊 Friendly, 😁 Good vibes, 🌟 Legend), which your call partners can see. They never see who sent a grin, and grins that look gamed (for example, many from the same person) do not count. Your Home page also shows your good-chat streak: the number of days in a row (India time) on which you had a call of at least a minute or one where both people showed video. It is calculated from your call records and only you see it. Moderators reviewing a report can see your level, trust signal and the counts behind it.

We also calculate an internal trust signal from the last 90 days. Grins and calls where both people showed video raise it; reports lower it (most when a moderator confirmed them, not at all when a moderator dismissed them), and blocks lower it slightly. It is never shown as a number. If it is low, you appear as 🌱 New here to others, you are matched only with people in the same situation, and your Home page tells you so; reports from accounts with low trust also count less. Automatic suspensions still require reports from several different people and are reviewed by a moderator. You can ask about this or object through Contact.

Technical information can include IP addresses, browser/device characteristics, requested URLs, timestamps, authentication and security events, rate-limit events, connection quality information and error diagnostics. Infrastructure and security providers may generate their own operational logs. Cookies and similar storage are described in our Cookies and Device Storage Notice.

We receive limited information from authentication providers, infrastructure/security providers, other participants, people who report harm and authorities making a legally valid request. We do not intentionally obtain contact lists or precise device geolocation through the current app.

Why we process information

We do not treat acceptance of our Terms as consent to unrelated marketing or every form of processing. When applicable law requires consent for a particular activity, we must obtain appropriate consent before that activity. Declining an optional purpose must not be disguised as acceptance of the entire service.

For users protected by the EU or UK GDPR, processing that is objectively necessary for the requested account and communication service is generally based on performing our agreement. Security, abuse prevention, proportionate moderation and service reliability may rely on legitimate interests after assessing necessity, impacts and safeguards. A specific legal obligation may require particular records or disclosures. Consent applies when legally required for an optional purpose; protecting vital interests is reserved for a qualifying emergency.

We do not automatically treat every safety disclosure as legally required, every operational choice as necessary for a contract, or every incident as an emergency. If a report contains special-category or criminal-offence information, we must identify the additional applicable legal condition and safeguards. We do not ask you to supply sensitive details simply because a free-text field exists.

Indian privacy obligations apply according to their current scope and commencement. The Digital Personal Data Protection framework has phased commencement; this policy does not represent that every future provision is already in force. We will honor applicable rights and maintain the required contact and grievance arrangements.

Who receives information

Your matched participant receives your live contributions, display name and the interests/languages relevant to the match. Technical room/participant identifiers may also be exposed through the communication software. We do not intentionally display your sign-in email or birth date to them. A participant may be in another country.

We use these providers: Amazon Web Services in Mumbai, India (ap-south-1) for our servers and short-lived matching data; Supabase in Mumbai for sign-in and our database; Vercel to host the website (its server-side code runs in Mumbai and pages are served from its global network); LiveKit Cloud to relay live video, audio and in-call text through the nearest of its global servers, so a call may be routed outside India; SendGrid (United States) to send sign-in codes and service email to your email address; Cloudflare for Turnstile bot checks; and Sentry for server error diagnostics and performance traces (which requests were made and how long they took, never call content), where enabled.

Providers process information under the role and terms applicable to their service. Some are processors for customer data and may act independently for specified security, billing or account purposes. We must put appropriate contractual, access and transfer safeguards in place; a provider's brand name alone is not proof that an agreement has been executed.

Access to support and moderation records is restricted to authorized people who need it to handle the matter. We may disclose information when a valid legal obligation requires it or when another identified legal basis permits a necessary and proportionate safety disclosure. We assess the request, disclose only the information appropriate to it, and preserve records where lawfully required.

If the service is transferred, information may be transferred with it subject to applicable law, safeguards and required notice. We do not use a business transfer as permission to disregard this policy or materially change a purpose without the required basis and notice.

No routine recording and the limits of that statement

No routine Grinzu call recording means we do not maintain a replay library or saved in-call chat history. It does not mean that no data about a call exists, that a complaint contains no description of it, or that routing providers do not process packets and connection diagnostics. Information you separately submit in a report or feedback message is stored as part of that case.

Grinzu does not record calls, so moderators cannot replay one. Staff may investigate the information actually available. Do not assume a report allows us to replay the incident. We do not promise end-to-end encryption; transport encryption is different from a design in which infrastructure providers cannot access content.

Never secretly capture another person. We prohibit unauthorized recording and disclosure but cannot prevent every capture made by another participant, an operating system or an external device. Consider anything you voluntarily show as visible to that participant in real time.

International processing and connections

Grinzu is operated from India, uses international infrastructure and is intended to connect adults across countries. Your information may be processed outside your country, and your chosen live contribution may be delivered to a participant abroad. Laws and access rights may differ by country.

Where a transfer mechanism is required, we must establish an applicable mechanism, such as an adequacy decision, appropriate contractual safeguards and any required supplementary protections. A reference to global availability, your acceptance of Terms or general privacy-policy consent does not by itself authorize a restricted international transfer. Repeated transfers cannot simply be justified as an exceptional one-off transfer.

[TO COMPLETE BEFORE PUBLICATION: VERIFY PRODUCTION COUNTRIES, VENDOR AGREEMENTS, EU/UK TRANSFER MECHANISMS, OTHER APPLICABLE LOCAL MECHANISMS, AND ANY REQUIRED REPRESENTATIVES. State the applicable safeguards and how users can obtain information about them.]

Retention and account deletion

We retain information only for a defined service, safety, legal or dispute-handling purpose and restrict any information retained after an account closes. We must reconcile deletion with applicable duties, including Indian intermediary rules concerning registration information after cancellation and information/associated records preserved after specified removals. Legal holds and statutory child-protection preservation can require different periods.

Account deletion can remove the active sign-in account, profile, blocks and feedback. Call metadata, reports and suspension records are separate records and are not automatically removed by that action in the current implementation. Limited copies may also remain in backups and provider records until their applicable retention cycles end. We cannot promise that every copy is erased immediately.

[TO COMPLETE BEFORE PUBLICATION: INSERT THE APPROVED DATA-CATEGORY RETENTION SCHEDULE, REQUIRED LEGAL ARCHIVE, CALL/MODERATION CLEANUP PERIODS, PROVIDER LOG/BACKUP PERIODS AND LEGAL-HOLD RULES, AND IMPLEMENT THEM. The accompanying operations document contains proposed values; they are not implemented deletion promises.]

Where law requires a record to be preserved, a deletion request does not override that duty. We will explain an applicable exception and retain only what is appropriate. Unnecessary information must not be kept indefinitely merely because it might someday be useful.

Your rights and choices

You can keep your video blurred (by not tapping Show video, or by choosing Not yet), leave a call, mute your microphone, turn off your camera, change browser permissions, sign out, use block/report controls, and request account deletion through Home or the public contact route. Blocking is applied to accounts; it cannot guarantee that a person will never return using another identity.

Depending on applicable law, you may request access to information, correction, deletion, portability, restriction, withdrawal of consent, or an objection to particular processing. Where a decision is solely automated and has a legally significant or similarly significant effect, applicable law may provide additional safeguards. We provide an appeal route for account restrictions; we do not assume a report threshold proves misconduct.

Send a request to [TO COMPLETE: VERIFIED PRIVACY CONTACT]. We may ask for proportionate information to verify your identity and protect other people's records. Do not send identity documents unless a necessary, secure process is specifically explained. We may redact other people's information and must explain a lawful reason for declining a request. Applicable response periods and extension rules take priority; for EU/UK GDPR requests the normal period is one month, subject to lawful extensions with timely notice.

You can complain to the privacy authority that has jurisdiction, including your local supervisory authority where applicable, without first being required to waive another remedy. India's applicable grievance and Board routes depend on commencement and legal scope. [TO COMPLETE: RELEVANT OVERSEAS REPRESENTATIVE AND REGULATOR CONTACT INFORMATION IF REQUIRED.]

Children and age information

Grinzu is not offered to minors. If you believe a minor has used the service, leave the call and report the concern without requesting sexual proof, an identity document or additional images. A parent, guardian or other concerned person can contact the public safety contact without an account.

When we learn of a likely minor, we must restrict inappropriate access, investigate appropriately, and delete or restrict data subject to applicable reporting, safety and preservation obligations. A profile's stated age does not remove those obligations. Any future age-assurance supplier or biometric process needs a specific assessment and a clear notice before introduction.

If you are under 18, stop using Grinzu and do not submit more information. You or a parent or guardian may contact the public safety route for help with an existing account or information already submitted.

Reporting a security concern

Contact the public privacy or legal-request channel in the Safety and Complaints Policy if you discover a possible security or privacy flaw. Describe the affected feature and the minimum steps needed to explain it. Use harmless examples; do not send passwords, access tokens, other users' records or intimate material. Do not access another person's account, disrupt the service or continue exploiting a flaw. This reporting route does not grant testing authorization or promise a reward or legal immunity.

Security and changes

We use reasonable technical and organizational safeguards appropriate to the information and risk, including access controls and protected communications. No system can be guaranteed perfectly secure. We must investigate incidents, preserve necessary evidence and notify authorities or affected people when applicable law requires it. We do not promise a single worldwide breach-notification deadline because laws differ.

If we change this policy materially, we will provide appropriate notice and obtain additional consent when required before a new consent-based purpose. An updated policy cannot retrospectively turn a prohibited or undisclosed use into a lawful one.