01 Quick summary
We're Edyantra, and we make Pynk, an app for organizing school life. Here's the short version, with the full detail below if you want it.
What we collect: your name and email from sign-in, plus whatever you put into the app — timetable, notes, pack lists, projects, board pins.
Do we sell it? No. We don't have an ad business, and we've never sold user data to anyone.
Do we use AI? Yes, for one specific thing: turning scanned timetable text into a structured schedule. You see and can edit the result before it saves.
Who else sees your stuff? Nobody outside your account, unless you invite them in. Family you add can see the family board. Friends you add can see boards and projects you share. Nobody else, and there's no public directory to find you.
Can you delete everything? Yes, from Settings, any time. It's a real delete, not a deactivation.
02 Interpretation and definitions
A few terms come up repeatedly, so let's define them once instead of re-explaining each time.
"Service" means the Pynk app and anything we run to support it, including our API and database. "Personal data" means any information that identifies you or could reasonably be linked to you, like your name, your email, or content you've written. "We," "us," and "our" refer to Edyantra, the company behind Pynk. "You" means the person using the app, whether as a student or a parent account.
03 What information we collect
We collect three kinds of information: what you give us directly, what the app generates as you use it, and a small amount of technical data our servers need to function. We don't collect location, contacts, microphone audio, payment details, or advertising IDs, because none of those are part of the product.
Account information
When you sign in with Google, Apple, or an email link, we get your name and email from that provider. We also create an account ID, store which role you've picked (student or parent), and, if you join a family circle, a household ID linking you to it.
The content you create
This is most of what Pynk stores, and it's the reason the app is useful: your timetable (subjects, times, rooms, week pattern), which classes you've marked done, your pack list items and whether they're checked off, notes tied to a subject or due date, group projects with their tasks and comments, and anything you pin to a family or friends board. All of it is written by you or, in the case of shared projects and boards, by people you've invited in.
Parent–child link records
If a parent links to a student's account, we store that link, the permission it grants (view or edit), and when it was created. Where in-app consent is captured for that link, we log the method, the timestamp, and the IP address it came from. This exists purely as an audit trail for the consent itself, nothing else.
Technical data from using the Service
Our servers log the basics needed to keep the app running and secure: IP address, request timing, and app version. We don't run a separate analytics or ad-tracking SDK, so this data stays in ordinary server logs rather than feeding any profile of you.
What we ask permission for on your device
Pynk requests access to your photo library, so you can pick a timetable photo to scan. That photo is processed on your phone using Apple's on-device text recognition and is never uploaded to us; only the text comes off your device. Camera access is also declared for the same purpose, though picking an existing photo is the main way people scan today. We don't ask for location, contacts, microphone, or Bluetooth access, because Pynk has no use for them.
04 How we use your information
We use what we collect to run the product: creating your account, syncing your timetable and other content across your devices, structuring a scanned timetable into something usable, showing your shared content to the people you've actually invited, and supporting the parent–child link and its consent record. We also use technical logs to catch bugs, stop abuse, and keep the service secure. That's the list. We don't use your information for advertising, and we don't build behavioral profiles from it.
05 Whether we use AI to process your data
We use one AI provider, Mistral AI, for one job. When you scan a timetable, the text pulled from that photo (not the photo itself) gets sent to Mistral to arrange into rows: subject, day, time, room. You review the result and can fix anything before you save it. Nothing else you type or write in Pynk goes through Mistral or any other AI service.
If your timetable photo happens to include personal information beyond a normal school schedule, that text would get processed the same way. If you'd rather it didn't, don't scan that document, or edit the result afterward.
07 Whether your information is transferred internationally
Some of the providers above run infrastructure outside your own country, so your data may be processed in a different location than where you are. We rely on those providers' own security and contractual safeguards for anything that crosses borders. [confirm and list the specific Railway and Firebase/Google Cloud hosting regions here].
08 How long we keep your information
Your account and everything in it, timetable, notes, pack lists, projects, boards, sticks around until you delete it or delete your account. Parent–child link codes are short-lived and get removed once used or expired. Circle invite codes expire roughly a day after you create them. Consent records stay as an audit trail until the account they belong to is deleted. Sign-in sessions expire after seven days by default. Server logs follow our hosting provider's standard retention.
One honest caveat: we don't currently run an automatic job that sweeps up stale, unused invite codes ahead of their normal expiry. It's on our list, and this is the kind of thing we'd rather disclose than gloss over.
09 Whether we collect information from minors
Pynk is built around school timetables, so we expect plenty of our users to be school-age. A student account holds the same kind of information as any account: name, email, and whatever school-life content that person adds.
Minimum age to hold an account: [insert minimum age policy, e.g. 13, plus how younger users are handled — decide with counsel].
Where a parent links to a child's account, they can see what that link's permission allows, currently timetable and pack status, and we log the consent for that link as described in Section 3. If you think a child has given us personal information without proper parental consent, email us at privacy@edyantra.com and we'll look into removing it.
10 Your privacy rights
You can see and download everything in your account: open Settings and choose "View my data" for a summary and an exportable file. You can fix your display name yourself in Settings, and reach us for anything you can't change on your own. Deleting your account, also in Settings, permanently removes it along with the content it owns: timetable, notes, pack items, consent records, link codes. There's no undo, so we mean it when we say permanent.
A couple of limits worth knowing about. If a project teammate left a comment before you left the project, that comment can stay behind, since it's their content, not yours to delete. And while deleting your Pynk account removes your data from our systems, occasional re-authentication issues can prevent the linked Firebase identity from clearing automatically on our side, so reach out if you want that confirmed.
If a law where you live gives you additional rights, correction, objection, grievance redressal, or anything else under a framework like India's DPDP Act, those apply on top of what's written here. Email privacy@edyantra.com and we'll respond in reasonable time.
12 How we keep your information safe
All production traffic runs over HTTPS. Sign-in tokens are verified against Firebase and checked by our backend on every request, and your session token lives in your device's Keychain rather than plain storage. Access to our database and servers is limited to what's needed to run the product.
No system is bulletproof, and we won't pretend otherwise. If we ever learn of a breach that affects your information, we'll tell you and any authority the law requires us to tell.
13 Updates to this policy
We'll update this page as Pynk changes. If a change is significant, we'll bump the date at the top and try to flag it in the app itself. Using Pynk after an update means you're fine with the new version.
14 How to contact us
Questions, requests, or something that just doesn't sit right, email privacy@edyantra.com. Postal address: [insert registered business address].