Last updated · 10 July 2026

Privacy policy

This policy describes how Rewinity Labs (“Rewinity”, “we”, “us”) processes personal data when you use the Rewinity mobile apps, website, and related services. It is written to be readable; where law requires more formality, the substance below still applies.

Who we are

Rewinity Labs operates the Rewinity platform from Bengaluru, India. For privacy questions or to exercise your rights, contact [email protected].

What Rewinity does

Rewinity helps you search your extended professional and personal network by skills and intent — not by browsing phone numbers. Introductions travel through people who know you, with consent at each step. Optional features include matrimony matching, referrals, in-app chat, quick asks to direct contacts, bounty broadcasts, a consented rolodex (“saved people”), ratings, a points wallet, and reward redemptions.

What we collect

Phone number & account identity — verified by one-time passcode (OTP) via our SMS provider. Your number is your login. It is not shown in search results and is shared with another user only after you accept an introduction and choose how to connect.
Profile — display name, city, bio, professional tags, languages, years of experience, service area (including optional map pins you choose), pricing tier, connection-channel preferences, UI language, and an optional profile photo stored in private object storage.
Contacts (hashed) — when you sync your address book, phone numbers are hashed on your device using HMAC-SHA256 with a server-side secret (“pepper”) before transmission. We do not store raw numbers from your address book. We store hashes, match results, and your per-contact discoverability choices.
Network graph & discoverability — which synced contacts you mark discoverable, your master searchable toggle, discoverability reach (how many hops away you may appear), presence pause, and blocks or mutes you set.
Searches & saved searches — queries, filters, tags, hop limits, and saved-search fingerprints used to run and improve network search. A search-query log (query text, parsed tags, result counts — reviewed by our team for quality and abuse) is kept for a limited window, auto-purged on a rolling basis, and deleted immediately when you request account deletion.
Quick asks & replies — the ask text you post to direct contacts and replies you send, including a contact suggestion if you make one. Automatically deleted 24 hours after posting.
Bounty broadcasts — the need you broadcast, which is shown together with your first name to recipients up to three hops away — an identity disclosure you explicitly consent to when posting.
Saved people (Circle) — rolodex entries created only with the saved person’s consent, plus private notes visible only to you. Deleted when either account is deleted, and removable by the saved person at any time.
Introductions — briefs you write, hop distance, price paid, chain length (not other users’ identities in exports), state (pending, accepted, declined, etc.), and outcomes you record.
In-app chat — messages and attachments in threads opened after an accepted introduction. Threads have a message cap; attachments are stored in private object storage.
Matrimony (optional) — only if you opt in: gender, date of birth (used to derive an age band shown in search, not your exact birth date to others), marital status, height, diet, profession, location, preferences, optional note, and optional photos (shown only if you enable photo sharing and only after mutual introduction acceptance). Enabling matrimony records explicit consent.
Referrals & invites — invite links, contact hashes for people you invite, invite status, and referral rewards. We do not send messages to your contacts without your action.
Ratings — scores and optional feedback you give or receive after connections.
Payments, wallet & points — intro fees processed by our payment partner (we receive order IDs and amounts, not card numbers); wallet top-ups; points earned and spent; redemption requests and delivery details you provide (e.g. email for gift-card fulfilment or fields for custom rewards).
Device & technical data — push-notification token, an app-generated device identifier used for session security (we do not fingerprint your hardware), app version and platform, your signed-in device list, and security/audit logs (searches, intros, profile changes) for abuse prevention and product operation.
Device integrity & app verification — to protect payments and prevent fraud, the app reports basic integrity signals (whether the device appears rooted/jailbroken, is an emulator, or runs tampering tools) and may run hardware verification: on Android a Google Play Integrity token is verified with Google, and on iOS an Apple App Attest attestation is verified using Apple’s certificates. We store the resulting verdict and signals (not your hardware identity) for up to 90 days after last activity; a failed or absent verification may limit payments and redemptions, never basic browsing.
Crash & error reports — if the app crashes or errors, a report (stack trace, device model, OS version, app version, and your account ID — never your phone number, name, or message content; request URLs are stripped of query text) is sent to our error-reporting provider so we can fix bugs.
Consents — records of which policy version you agreed to for age, terms, privacy, contact processing, and matrimony (when applicable).

How we use your data

Authenticate you and operate your account.
Match hashed contacts to existing members and build your introduction graph.
Run tag- and intent-based search and show masked candidate cards with social proof.
Deliver, bill, and settle introduction requests; credit points to bridges in the chain.
Enable chat, notifications, ratings, referrals, matrimony search, and reward fulfilment.
Detect abuse, enforce rate limits, and comply with law.
Keep the platform and your money safe: verify app/device integrity, restrict sensitive actions on compromised devices, require minimum app versions after security fixes, and diagnose crashes.

What we never do

Sell or rent your contact graph or address book to advertisers or data brokers.
Show phone numbers in search results or to intermediaries in the chain.
Run display advertising or use your network for ad targeting.
Store raw phone numbers from your synced address book.
Make contacts discoverable by default — every contact starts off.
Message people on your behalf without your explicit action (e.g. you tap share/send).

Who can see what

Searchers see masked cards: first name, city, tags, social proof (e.g. who referred the match), and a price quote — not phone numbers and not the full identity of people in the chain. Bridges see that they helped connect a tag match, not your full brief unless you choose to share more. After you accept an introduction, you choose channels to share (in-app chat, phone, WhatsApp, email). See our privacy posture for the five consent gates and visibility matrix.

Sub-processors

We share the minimum necessary with vetted providers, each for a defined purpose:

Twilio — OTP and transactional SMS.
Razorpay — payment processing (card data stays with Razorpay).
Tremendous — digital gift-card fulfilment for eligible rewards.
AWS S3 — private storage for profile photos, chat attachments, matrimony photos, and reward images.
Expo — push-notification delivery to your device.
Sentry — crash and error reporting (scrubbed as described above).
Google Analytics — anonymised website traffic on rewinity.com (IP anonymisation enabled).
Google (Play Integrity API) — Android app/device verification; Google processes the integrity token.
Apple (App Attest) — iOS app/device verification via Apple-issued attestations.
Email (SMTP) — transactional email (account notices, deletion confirmations).
Hosting infrastructure — databases and caches that store the data described above at rest.

Some providers may process data outside India. We use contractual safeguards appropriate to the transfer and limit what we send to what each provider needs.

Your rights

Under India’s Digital Personal Data Protection Act, 2023 (DPDP) and, where applicable, GDPR-style rights for international users:

Access & portability — download a JSON export from Settings → Privacy (profile, intros, wallet, points, consent records, and contact-sync counts).
Correction — edit profile, tags, discoverability, and settings in the app.
Erasure — request account deletion in Settings → Privacy. Your profile is hidden and the account deactivated immediately; personal data is erased after a 30-day grace window (email us before then to cancel).
Withdraw consent — pause presence, toggle discoverability per contact, disable matrimony, decline or revoke Circle membership, turn off notifications, or delete your account at any time.
Manage devices — see every signed-in device and sign out everywhere else in Settings → Signed-in devices.
Grievance — email [email protected]. We aim to respond within 7 working days.

Retention

Active account — data kept while your account is active and as needed to provide the service.
Deletion — on request, immediate deactivation and graph hiding; erasure or anonymisation within 30 days except where law requires retention.
Financial records — payment, points, and redemption records may be kept in anonymised form after deletion for tax and accounting obligations.
Security & audit logs — typically up to ~1 year, then purged.
Error logs — typically ~30 days; crash reports at our error-reporting provider ~90 days.
Quick asks & replies — deleted automatically 24 hours after posting.
Search-query log — rolling auto-purge; deleted immediately on a deletion request.
Device-integrity records — up to 90 days after the device was last seen; detached from your account immediately on a deletion request.
Sessions & ephemeral data — short TTLs (notifications, OTP, search sessions, cached reach summaries).

Security

Traffic is encrypted in transit (TLS, with certificate pinning in the app). Data the app stores on your device is encrypted at rest with a key held in your phone’s secure keystore. Session tokens are stored server-side only as cryptographic hashes. Object storage is private; files are served through authenticated, access-controlled URLs. Contact hashes use a server-held pepper. Payment webhooks are signature-verified. The app blocks screen capture on sensitive screens where the platform allows it, and app/device integrity is verified as described above. Access to production data is restricted and audited. Abuse-sensitive actions are rate-limited.

Children

Rewinity is for users aged 18 and above. We do not knowingly collect data from children. Matrimony and general use require age confirmation at signup.

Changes

We will notify you in-app and, where appropriate, by email at least 30 days before changes that materially expand collection or use. Continued use after the effective date constitutes acceptance where permitted by law. Consent records reference a policy version (currently 2026-07).

Contact

Privacy: [email protected]
Legal: [email protected]

Plain language, real commitments