Privacy Policy
ZapFee is fee billing and collection software for education and training businesses. This policy explains what personal information ZapFee handles, why, who helps us, and what you can ask of us.
It is written in plain words on purpose. It describes what the software does today, and it will change when the software does.
1. Who we are and what this policy covers
In this policy "ZapFee", "we" and "us" mean the business that provides the ZapFee software and runs this website.
This policy covers three groups of people:
- Visitors to the website at zapfee.in.
- Staff of an institute who sign in to ZapFee: owners, managers, accountants and front-desk staff.
- People whose details an institute keeps in ZapFee, such as learners, parents, guardians and other payers.
If you are a parent, guardian, learner or payer, the institute that bills you decides what is collected about you and why. Its own Privacy Notice, linked at the foot of the pages it sends you, is the one written for you. A general copy is linked at the foot of this page.
2. Our two roles
For the website and for staff sign-in accounts, ZapFee decides how personal information is used, and this policy is our statement of it.
For the records an institute keeps in ZapFee — learners, families, fees, invoices, receipts and messages — the institute decides what is collected and why. ZapFee stores and processes those records on the institute’s behalf and on its instructions, to provide the software to it.
3. What we collect
When you visit the website
The website has no advertising trackers and no analytics scripts. It has no sign-up form. If you write to us by email, we receive your email address and whatever you choose to tell us.
Like any website, the servers that deliver our pages keep technical records of requests, such as the network (IP) address, the browser type and the time.
When you sign in as staff
- Your name and email address, the institute you belong to and your role there.
- When you were invited, when you accepted, and when you last signed in.
- A record of the changes you make in ZapFee, with your name and the time, in the institute’s activity log.
- If you sign in with Google, the Google account details described in the next section.
Passwords and one-time sign-in codes are handled by our sign-in provider, which keeps a password only in hashed form. ZapFee’s application does not store it.
What an institute records
An institute may record learners’ and payers’ names and contact details, details it needs for admission and safety, fees, invoices, receipts, payments and the messages it sends. The institute’s own Privacy Notice lists these for its families.
4. Google user data
Staff may choose “Sign in with Google” instead of a password or an emailed code. This section says exactly what ZapFee does with the information Google provides.
What we access
ZapFee asks Google only for basic sign-in information (the “openid”, “email” and “profile” permissions). Google then tells us:
- your email address, and whether Google has verified it;
- your name;
- the web address of your profile picture;
- the identifier Google uses for your account.
ZapFee does not ask for, and cannot read, your Gmail, Google Drive, Calendar, contacts or any other Google data. It does not ask Google for ongoing (“offline”) access to your account.
How we use it
- To confirm who you are and sign you in.
- To match you to a ZapFee account that already exists for you. Accounts are created by invitation from an institute’s owner, or by ZapFee; signing in with Google never creates one.
- In some cases, to label your account with the name on your Google account.
If there is no ZapFee account for you, the sign-in is refused, you are signed out, and the sign-in record that attempt created is deleted.
ZapFee does not display or otherwise use your profile picture. We do not use Google user data for advertising, we do not sell it, and we do not use it to develop, improve or train artificial-intelligence or machine-learning models.
How we store it
The sign-in itself is completed by our sign-in provider, which keeps a sign-in record for your account: your Google account identifier, email address, name and profile-picture address. ZapFee’s own database keeps your email address and name against your staff account. ZapFee’s application does not keep Google’s sign-in tokens once the sign-in has finished; a short-lived cookie that carries one sign-in attempt is cleared when the attempt ends and expires by itself after ten minutes.
Who we share it with
Google user data is passed only to the service providers that run sign-in and hosting for us, listed under “Who helps us”, and only so that they can provide that service. We do not transfer it to anyone else, except where the law requires it. Nobody at ZapFee reads it except where that is needed to keep the service secure, to help you when you ask for support, or to meet a legal duty.
Limited use
ZapFee’s use of information received from Google APIs, and any transfer of it to another app, will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
Removing it
You can stop using Google sign-in at any time and remove ZapFee’s access from the security settings of your Google Account. To have the sign-in record for your account deleted, ask your institute’s owner to remove your staff account, or write to us at hello@zapfee.in.
5. How we use information
- To provide ZapFee to the institute that uses it: its catalogue, admissions, invoices, receipts, statements and reminders.
- To sign staff in and keep sessions safe, including signing out a session that has been left idle.
- To send the emails the service needs, such as sign-in codes and staff invitations, and the emails an institute sends its families.
- To keep a record of who changed what, for the institute.
- To answer you when you write to us, and to fix faults.
- To meet a legal duty.
We do not sell personal information, and we do not use it for advertising.
7. Who helps us
We use other companies to run ZapFee. Each receives only what it needs for its part:
- Supabase: the database that holds the records, and staff sign-in.
- Vercel: the servers that run the application and deliver this website.
- Resend: delivery of email.
- Google: sign-in, only if you choose “Sign in with Google”.
- Razorpay: online payments, only where an institute has connected its own Razorpay account. The payment is between the payer, the institute and Razorpay.
- An AI provider (Google or Anthropic): an optional reader for payment screenshots. It works only in an institute’s Test Mode, never on live records, and only where it has been switched on.
- A scheduling service that calls ZapFee on a timer. It receives no personal information.
An institute may also connect another application to its ZapFee records. That application then receives what the institute has agreed to share with it.
Some of these providers may store or process information on servers outside India.
We also disclose information where the law requires us to.
8. How long we keep it
We keep a staff account’s details for as long as the account exists. We keep an institute’s records for as long as the institute uses ZapFee; invoices, receipts and other financial records are kept rather than deleted, because the institute is required to keep them.
This policy does not promise fixed deletion periods, because the software does not yet enforce one for every kind of information. Where it does, the institute’s Privacy Notice states the period.
9. How we protect it
- Each member of staff has a role, and sees and does only what that role allows.
- Sensitive changes, such as bank details, need the password again.
- A session left idle is signed out.
- Changes are recorded in an activity log with a name and a time.
- The keys an institute gives ZapFee for its payment gateway are stored encrypted.
- A family’s link opens that family’s own account or document and nothing else.
No system is perfectly secure. ZapFee does not hold a security certification and does not claim one.
10. What you can ask
- If you visited the website or wrote to us: you can ask what we hold about you and ask us to correct or delete it, by writing to hello@zapfee.in.
- If you are a member of staff: your institute’s owner can correct your details or remove your account. You can also write to us.
- If you are a parent, guardian, learner or payer: please ask the institute that bills you first. It decides how your information is used, and we act on its instructions.
Some records cannot be deleted on request — an invoice or a receipt an institute must keep, for example. If that applies, we or the institute will tell you.
11. Children
This website and staff accounts are for adults who run or work for a business. We do not knowingly collect a child’s information through them.
Institutes do record information about children who are their learners. The institute is responsible for telling the child’s parent or guardian and for obtaining any consent the law requires. ZapFee processes that information for the institute.
12. Questions and complaints
Write to us at hello@zapfee.in. Please say which institute you deal with, if any, so that we can find the right records. The name of a grievance officer is not yet published here; it is part of the legal review this page is under.
13. Changes to this policy
When this policy changes we will publish the new version on this page and change the date at the top. This page is under legal review, so its wording may change when that review is complete.