Skip to content

Privacy policy

What Clubync collects, why it collects it, and what it will not do with it.

Last updated 10 September 2026

Who this covers

Clubync is operated by [REGISTERED ENTITY NAME] ("Clubync", "we"). This policy covers the Clubync mobile app and this website.

Two different relationships run through the product. When a club uses Clubync to manage its members, the club decides what to collect and why — the club is the data fiduciary and we process that data on its instructions. For the club's own account with us, and for this website, we are the fiduciary.

What we collect

We collect what the product needs to work, and stop there.

  • Identity: name and mobile number. A member's profile photo, if the club captures one.
  • Authentication: your mobile number and the fact that an OTP was verified. We never store passwords, because there are none.
  • Membership: the club you belong to, your plan, its dates, and your role.
  • Attendance: the time and date of each check-in, and which club recorded it.
  • Payments: amount, date, method, status and the reference issued by Razorpay.
  • Diagnostics: crash and error reports, with identifying fields removed before they are sent.

What we do not collect

We do not collect card numbers, UPI PINs or bank credentials. Payments are processed by Razorpay, and those details go to Razorpay directly without passing through Clubync.

We do not track your location, read your contacts, or use your camera for anything other than scanning a member's QR code at the front desk.

Our application logs carry no phone numbers, no OTPs, no payment payloads and no raw QR contents. Identifiers are redacted before anything is written to a log or sent to error tracking.

Why we process it

To let a member sign in and prove their membership; to let a club record attendance and collect payment; to produce the invoices and reports a club needs to run; to keep the service secure and diagnose failures; and to meet tax and accounting obligations.

Who else sees it

Your club's staff, in the roles the club has granted them. Members of one club can never be seen by another club — separation is enforced in the database, not by the app.

  • Supabase, which hosts the database and authentication.
  • Razorpay, which processes payments.
  • Sentry, which receives error reports with identifying fields scrubbed.
  • An SMS provider, which delivers one-time passcodes.

Where it is stored

Records are held in a managed Postgres database with row-level security, so every query is scoped to a single club. A copy of pending attendance check-ins may sit briefly on the front desk's own device when the network is down, and is cleared once it syncs.

[CONFIRM AND STATE YOUR DATABASE REGION HERE.]

How long we keep it

For as long as the club's account is open, because attendance and payment history is the club's operating record. If a club closes its account we retain its data for [RETENTION PERIOD] so it can be exported, then delete it, except where tax law requires us to keep transaction records for longer.

Your rights

Under the Digital Personal Data Protection Act, 2023 you can ask for access to your data, correction of anything wrong, and erasure where we are not required to keep it. You can also nominate someone to exercise these rights on your behalf.

If you are a member of a club, start with the club — they decide what is held about you. If they cannot help, write to us at hello@clubync.com.

Children

Clubync is not intended for anyone under 18 to hold their own account. Where a club enrols a minor, the club is responsible for obtaining verifiable parental consent, as the Act requires of it.

Changes

If we change this policy we will update the date at the top and, for anything material, tell account holders in the app before it takes effect.

Contact

Write to hello@clubync.com, or to [REGISTERED ENTITY NAME], [REGISTERED ADDRESS]. Grievance Officer: [NAME], reachable at the same address.