Privacy Policy

Last updated: 7 September 2026

What SeenDicate collects, why, who else sees it, and what you can do about it. Written to match what the platform actually does rather than to cover every eventuality.

Who we are

SeenDicate is an education hosting platform and content studio. Teachers build and publish courses on it; students enrol in them and study.

Xentawan Technology developments Solution whose registered company is at 46b lumley road freetown. The legal entity operating SeenDicate, its registered address, and the country whose data-protection law governs this policy.

For anything in this policy, write to alvinmoore817@gmail.com.

What we collect

Only what the platform needs to do its job. In practice that is:

Your account: the name, email address and profile photo from the Google account or email address you sign in with, and the role you chose — student, teacher, or both.
Your profile: a biography and the subjects you teach or want to learn, if you enter them. A teacher profile is public.
What you make: courses, lessons, notes, quizzes, flashcards, assignments and the files, images, videos and voice recordings you upload.
What you do: which courses you are enrolled in, how far through each one you are, quiz scores, time spent studying, assignments you submit and the revision history of written work, and certificates awarded to you.
Messages: what you write or record in a course room, including voice notes.
Payments: what you bought and when. Card and mobile-money details are entered with our payment provider and never reach us.
Your device, if you allow notifications: a push token, so a reminder can find you. No advertising identifiers are collected.

What we do not do

We do not sell your personal information, and we do not share it with anyone for advertising.
We do not run third-party advertising or tracking pixels on the platform.
We do not build profiles of you for anything other than showing you courses that match the interests you chose.

Google user data: what we access

A teacher may connect their own Google account so that the classes they schedule on SeenDicate appear on their Google Calendar and can be held on Google Meet. Connecting is optional. Students never connect a Google account for this, and every other part of the platform works without it.

When a teacher connects, SeenDicate requests exactly two OAuth scopes and no others:

https://www.googleapis.com/auth/calendar.events — permission to create, update and delete calendar events. SeenDicate uses it only for the class events it creates itself. It does not read, list or copy your existing events, and it does not access any other calendar you own.
https://www.googleapis.com/auth/meetings.space.created — permission to create a Google Meet space and to read the participation record of spaces this app created. It gives SeenDicate no access to any meeting created outside SeenDicate.

Google user data: how we use it

The two permissions above are used for these purposes and no others:

Creating a calendar event on the teacher's Google Calendar when they schedule a class in SeenDicate, updating that event when the class is rescheduled, and deleting it when the class is cancelled.
Adding the students enrolled on that course to the event as guests, so the class appears on their calendar too.
Creating a Google Meet space for an online class and attaching its joining link to the class, the reminder notifications and the class page.
After an online class has ended, reading the participation record of that Meet space — the display names Google reports and how long each was present — so the lecturer has an attendance register for their own class.

Google user data: what we do not do with it

We do not read, index or store the contents of your existing calendar.
We do not sell Google user data, and we do not transfer it to anyone for advertising, credit assessment, lending or any similar purpose.
We do not use Google user data to develop, improve or train generalised artificial-intelligence or machine-learning models. Google Workspace data is never sent to our AI provider.
We do not allow humans to read Google user data, except where you have given explicit permission for a specific support request, where it is necessary for security purposes such as investigating abuse, or where we are required to by law.

Google user data: who we share it with

SeenDicate does not sell, rent or trade Google user data, and does not share it with any third party for that party's own purposes. It is disclosed only in these ways, all of which follow from the feature you asked for:

To Google itself, when we call the Google Calendar API and the Google Meet API on your behalf to carry out the actions listed above.
To the students enrolled on your course, who are added as guests to the calendar event you created and therefore see its title, time and Meet link. This is the point of scheduling the class.
To Google Cloud Platform and Firebase, which host SeenDicate and therefore process this data as our infrastructure provider under Google's own terms. They act on our instructions and for no independent purpose.
To no one else. In particular, an attendance register derived from a Meet space is shown only to the lecturer who held that class and to the student it concerns.

Google user data: how we protect it

All traffic between SeenDicate, your device and Google's APIs travels over TLS-encrypted connections.
The long-lived authorisation Google issues when you connect (the refresh token) is stored in a single private record that no client application can read — not the web app, not the mobile app, and not your own signed-in session. Our database rules deny every client read and write of it. It is readable only by our server code.
Short-lived access tokens are requested when a specific action needs one and are never written to storage or to logs.
We hold the narrowest permissions that make the feature work. We do not ask for read access to your calendar, for access to meetings we did not create, or for any Gmail, Drive, Contacts or profile scope.
Access to production systems is limited to the operator of SeenDicate and is protected by Google account authentication.

Google user data: how long we keep it, and how it is deleted

The refresh token is kept only while your Google account is connected. Disconnecting deletes it immediately.
When you disconnect, SeenDicate also asks Google to revoke the authorisation, so the grant is withdrawn at Google as well as deleted here. You can confirm this, or withdraw it yourself at any time, at https://myaccount.google.com/permissions.
If Google tells us an authorisation is no longer valid — because you revoked it, or it expired — we delete our copy at that moment rather than keeping a token that no longer works.
Calendar events we created remain in your Google Calendar after you disconnect, because they are yours. Delete them in Google Calendar if you want them gone.
A Meet attendance register is kept as part of the class record for as long as the course record exists, because it is the register for a class that took place. It holds the participation times and the names Google reported, not any other Google data.
Deleting your SeenDicate account deletes the stored authorisation with it. You can also ask us to delete all Google-derived data we hold about you by writing to alvinmoore817@gmail.com, and we will do so.

Limited Use

SeenDicate's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Attendance at a class

When you tap Join on a class, we record that you did, along with your name and email, so the lecturer knows who attended. For a class held on Google Meet we also read from Google when each participant arrived and left.

Google reports a display name for each participant, never an email address. We match those to enrolled students only where the name is unambiguous, and anyone we cannot confidently identify is shown to the lecturer as an unnamed guest rather than guessed at.

A class register is visible to the student it concerns and to the lecturer who held the class. Other students cannot see it.

Artificial intelligence features

Some tools draft material for you: turning a photograph of your notes into a quiz, or generating a first version of a document. When you use one, the text or image you supply is sent to our AI provider to produce that draft.

We do not send your personal information, your messages, or other people’s work to these services, and drafts are shown to you for editing before they become part of a course.

The provider is Meta AI, which SeenDicate calls over its API. Google Workspace data — your calendar, your Meet spaces and anything derived from them — is never sent to it, and is never used to develop, improve or train any AI or machine-learning model.

Who else processes your data

We use these services to run the platform. Each one only receives what it needs to do its part:

Google Firebase — accounts and sign-in, the database, server functions, and push notifications.
Cloudflare — storage for the files, images, videos and recordings uploaded to the platform, and video streaming.
Monime — payments. You enter payment details with them; we receive only confirmation that a payment succeeded.
Google Calendar and Google Meet — only for teachers who connect them, as described above.
Meta AI — only the text or image you supply to an AI drafting tool, as described above.

Who can see what

Your teacher profile — name, photo, biography, subjects and published courses — is public, so students can find you before signing in.
A published course, and the syndicate that hosts it, are public.
Your enrolments, progress, quiz scores and submitted work are visible to you and to the lecturer of that course. Other students cannot see them.
A course room is shared with the whole class. Anything you write or record there is seen by everyone enrolled.
A certificate carries a verification code, and anyone holding that code can confirm it was issued, to whom, and for what.
If you belong to a syndicate, its staff can see your work within that institution, in the same way a school sees a pupil’s.

How long we keep it

Your account and what you made stay while your account exists.

Learning records — enrolments, progress and certificates — outlive the course they belong to. A course being withdrawn or unpublished does not erase the record that you studied it, because a certificate has to remain verifiable.

«five years» after the course ends, because a certificate has to stay verifiable and an institution has to be able to confirm what a student studied. Payment records are kept for «seven years» to meet «Sierra Leonean» tax and accounting requirements.after an account is deleted, and any period required by law where the operator is established.

Your choices

You can edit your profile, and change or remove your biography and photo, at any time.
A teacher can disconnect Google Calendar at any time from the Calendar tab. Disconnecting deletes the stored authorisation immediately and asks Google to revoke it. Classes already in your Google Calendar stay there; remove them from Google if you want them gone.
You can turn off push notifications in your device settings.
You can ask for a copy of your data, or ask us to delete your account, by writing to alvinmoore817@gmail.com.
You can ask us for a copy of your data, ask us to correct it, ask us to delete it, or object to a particular use. Write to alvinmoore817@gmail.com and we will answer within «30» days. If you are in «Sierra Leone, EU or the UK» these are your rights under «the GDPR», and you may complain to «your national data protection authority» if our answer does not satisfy you.
rectification, erasure, portability, objection — and the response time you commit to.

Security

Data is held on Google and Cloudflare infrastructure and travels encrypted.

Some things are deliberately unreachable even to us through the app: a teacher’s Google authorisation is stored where no client can read it, including the teacher’s own, and is used only by our servers to act on the classes they schedule.

No system is perfect. If we discover a breach affecting you, we will tell you.

Children

SeenDicate is used in schools, so some students are minors.

[TO CONFIRM] The minimum age for holding an account directly, whether an institution may create accounts for pupils below it, and what parental consent is required where the operator is established. This section must be settled with legal advice — the answer differs materially between jurisdictions.

Changes

If we change this policy in a way that affects you, we will say so in the app before the change takes effect. The date at the top is always the date of the current version.