Skip to content
Gridzo
  • Home
  • Pricing
  • Support

Privacy Policy

Effective [TODO: effective date]

On this page

  1. The short version
  2. Who we are
  3. What we collect
  4. What we don’t collect
  5. How we use it
  6. Who can see your information
  7. Service providers
  8. Children’s information
  9. How long we keep it
  10. Your choices and rights
  11. Security
  12. Where your data is stored
  13. Changes to this policy
  14. Contact

1. The short version

  • We collect what Gridzo needs to run a dance school’s classes: names, email addresses, optional phone numbers, students’ details, schedules, fee and payment records and chat messages.
  • We don’t sell your information, show ads, or use analytics or advertising trackers in the app.
  • Information is shared only with the people in your school who need it, and with the service providers that run Gridzo for us.
  • Parents control their children’s information and can edit or delete it at any time.
  • You can delete your account in the app. See Delete your account.

2. Who we are

Gridzo is provided by [TODO: legal entity name], [TODO: registered address] (“we”, “us”). This policy covers the Gridzo app for iOS and Android and the website at gridzo.app.

Teachers decide what their school records about its students and families. For that school information we act on the school’s behalf, and the school is also responsible for how it uses it. For account information and for running the Service, we are responsible.

3. What we collect

Information you give us

WhatDetails
AccountYour email address (used to sign in with a one-time code), your name, and optionally your phone number. Your role at each school you belong to (teacher, parent or student).
SchoolThe school’s name, and optionally its address, phone number and email, and the currency it charges in.
Batches and classesBatch names, levels, descriptions and fees; class days, times, durations, locations and notes; cancelled sessions and the reason given.
StudentsAdded by a parent: the student’s full name, and optionally their date of birth and notes for the teacher. If the student has their own login, which account it is linked to and when.
EnrollmentsRequests to join a batch, whether they were approved or declined, by whom and when.
Fees and paymentsFees due (period, amount, due date) and payment records: amount, date, method chosen from a list (cash, bank transfer, UPI, card or other), an optional reference and note, and who recorded and confirmed it. These are records only. We never receive card or bank details for class fees.
MessagesMessages posted in the school announcement channel and batch chats, who sent them and when, and when you last read each chat (to show unread counts).
SupportAnything you send us when you email us.

Information collected automatically

  • Push notification token. If you allow notifications on a real device, the app stores a push token from Expo and your device platform (iOS or Android) so we can send you notifications. You can turn notifications off in your phone’s settings at any time.
  • Sign-in and security logs. Our hosting provider keeps standard logs when you sign in or use the app, which can include your IP address, device or browser details and the time of the request. These are used for security and to fix problems.

School plan purchases

If a teacher buys a school plan, Apple or Google handles the payment. We don’t receive card details. We receive and store which school the plan is for, the store (Apple or Google), the product bought, the store’s transaction identifier, when the current period ends, whether it will renew, whether it is a trial, and which Gridzo account bought it. Our server checks each purchase with Apple or Google before recording it.

4. What we don’t collect

The app doesn’t use your location, contacts, photos, camera or microphone. It doesn’t include advertising, analytics or crash-reporting SDKs, and we don’t track you across other companies’ apps or websites. This website does not use cookies or analytics.

5. How we use it

  • To provide the Service: sign you in, show schedules, fees and messages to the right people, and let schools approve students.
  • To send notifications you’d expect, such as new messages, join requests, approvals, and payments reported or confirmed.
  • To email you sign-in codes and reply to support requests.
  • To check and apply school plan purchases and their student limits.
  • To keep the Service secure, prevent misuse and fix problems.
  • To meet legal obligations.

Where the law requires a legal basis (for example in the UK or EU), we rely on: performing our contract with you (running the Service), our legitimate interests (security and improving the Service, balanced against your rights), your consent (push notifications, which you can withdraw in your phone’s settings), and legal obligations.

We don’t sell or rent personal information, and we don’t use it for advertising or profiling.

6. Who can see your information

Access is enforced on our servers, so the app can only show each person what they are allowed to see:

  • Teachers can see everything in their own school: its batches and classes, the students in it with their details, enrollments, fees and payments, and the name and contact details of parents and students in the school.
  • Parents see their own children, the batches those children are in, their own fees and payments, and the school’s contact details. Other parents can’t see your phone number or email address.
  • Students with their own login see their own schedule and fees and the chats of their batches. Their parent manages their details, enrollments and payments.
  • Chats. Messages in a batch chat and the sender’s name are visible to that batch’s teacher and approved families and students. School announcements are visible to everyone in the school. Message text and the sender’s name can appear in push notifications on recipients’ phones.

We may also disclose information if the law requires it, to protect someone’s safety, or as part of a sale or reorganisation of our business, in which case this policy will continue to apply to your information.

7. Service providers

We use these providers to run Gridzo. They process information only to provide their service to us.

ProviderWhat for
SupabaseDatabase, sign-in and server functions. Stores all of the app’s data.
Expo (650 Industries)Delivering push notifications. Receives your push token and the notification’s title and text.
Apple and GoogleDelivering push notifications to devices, app distribution, and selling and verifying school plan subscriptions.
[TODO: email provider for sign-in codes]Sending sign-in code emails.
NetlifyHosting this website. Keeps standard request logs, such as IP address and browser details.

8. Children’s information

Many students on Gridzo are children. We take extra care with their information:

  • Parents add children. A child’s details are entered by their parent or guardian, who chooses what to add. Only the student’s name is required; date of birth and notes are optional.
  • Who sees it. A child’s details, enrollments and fee records are visible to their parent and to the teachers of the school whose batches the parent has asked to join. They aren’t visible to other parents. In batch chats, other members can see messages the child posts and the child’s name.
  • Student logins need a parent. A child can have their own login only by entering a one-time code their parent creates in the app, which is how the parent gives permission. The child signs in with their own email address. A linked student can see their schedule, their own fees and their batch chats, and can post in batch chats. The parent can remove the login at any time.
  • Parents stay in control. Parents can view, correct and delete their children’s information in the app, remove a child from a batch, and delete a child’s student record, which also deletes their enrollments and fee records. Parents can also contact us to review or delete their child’s information.
  • No advertising or tracking. We don’t use children’s information for advertising, profiling or any purpose other than running the Service for their school and family.
  • Children shouldn’t create their own Gridzo account without a code from their parent. If you believe a child has given us information without their parent’s permission, email hello@gridzo.app and we will delete it.

9. How long we keep it

  • We keep your information while your account is active.
  • When you delete your account, we delete your profile, contact details and push tokens; if you’re a parent, the students you added and their enrollments, fees and payments; and if you’re a school’s only teacher, the school and everything in it. Messages you posted stay in their chat without your name. See Delete your account for the details.
  • Removing a student or deleting a school deletes the related records in the same way. When a parent leaves a school, the school can keep its records of that family’s past enrollments, fees and payments.
  • Backups and logs kept by our hosting provider are deleted on their normal schedule, within [TODO: backup and log retention period, from your Supabase plan].
  • Subscription records are kept while the school exists, and as long as we need them for tax and accounting.

10. Your choices and rights

  • Edit your name and phone number, and your students’ details, in the app.
  • Turn push notifications off in your phone’s settings.
  • Leave a school, remove a student, or delete your account in the app.
  • Ask us for a copy of your information, to correct or delete it, or to object to or restrict how we use it, by emailing hello@gridzo.app. We may need to confirm it’s you first. Depending on where you live you may have further rights, including to complain to your local data protection authority.

If your request is about information a school recorded (for example, fee records), we may involve the school in answering it.

11. Security

Data is encrypted in transit between the app and our servers, and our hosting provider encrypts it at rest. Access rules in our database limit what each signed-in person can read or change. Sign-in uses one-time codes, so there are no passwords to leak. No system is perfectly secure, so please tell us at hello@gridzo.app if you notice anything wrong.

12. Where your data is stored

The app’s data is stored with Supabase in [TODO: hosting region]. Some service providers, such as Expo, Apple and Google, may process information in other countries, including the United States. Where the law requires, we rely on appropriate safeguards for these transfers, such as standard contractual clauses.

13. Changes to this policy

We’ll update this policy if what we collect or how we use it changes. If the change is significant, we’ll tell you in the app or by email before it takes effect. The effective date at the top shows when it last changed.

14. Contact

Questions or requests about privacy: hello@gridzo.app
[TODO: legal entity name], [TODO: registered address]

Gridzo
  • Pricing
  • Support
  • Terms of Use
  • Privacy Policy
  • Delete your account
  • hello@gridzo.app

Apple and the Apple logo are trademarks of Apple Inc. App Store is a service mark of Apple Inc. Google Play and the Google Play logo are trademarks of Google LLC.