Privacy Policy
Effective 26 August 2026 · Applies to the BeeSync mobile app and the BeeSync school portal.
BeeSync is school software. Almost everything in it — a child's grades, their attendance, a message to a teacher — belongs to the school that entered it, not to us. This page explains what the software stores, who can see it, and what happens when you want it gone.
Who we are
BeeSync is operated by Adnan Fares, a sole trader based in Lebanon. For anything on this page, write to [email protected].
Who controls the data
Each school decides what to record about its students and staff, who may see it, and how long to keep it. In data-protection terms the school is the controller and BeeSync is the processor: we hold and transmit the data on the school's instructions and do not decide what goes in.
This matters for you as a parent or teacher: if you want a record corrected or removed, your school can usually do it immediately, and it is the faster route. We will always act on a request sent to us, but for content the school entered we may need to confirm with them first.
What BeeSync stores
Set out honestly, because a vague version of this table would not be worth reading.
| Category | What it includes | Where it comes from |
|---|---|---|
| Account | Name, email address or BeeSync username, role at each school, language preference, profile photo, account status. Passwords are stored only as salted hashes and are never visible to us or to your school. | Created by a school administrator; you can edit your own name, photo and language. |
| Student record | Name, date of birth, gender, home address, home language, number of siblings, school start date, class, photo, weekly schedule, and guardian contact details. | Entered by school staff. |
| Health and dietary information | Allergies, intolerances, dietary requirements, illnesses, general health notes, and a doctor's name and contact number. | Entered by school staff, usually from what a parent tells the school at enrolment. |
| Attendance | Daily present/absent records, absence reports filed by parents, and planned early checkouts. | Staff record attendance; parents file absences and checkout plans. |
| Academic | Grades, term grades, generated report cards, homework, and class materials. | Entered by teachers and administrators. |
| Communication | Direct messages between parents and staff, school news posts, notices, survey responses, and short daily notes parents send to the class team. | Written by whoever sends them. |
| Payments | Records of school fees due and paid, and who recorded each payment. BeeSync does not process payments and never sees a card or bank number. | Entered by school administrators. |
| Technical | A push-notification token per device and whether it is iOS or Android, so alerts reach the right phone. Plus ordinary server logs (timestamps, error records) kept for a short period to keep the service running. | Generated automatically. |
BeeSync contains no advertising, no analytics SDKs and no third-party trackers. We do not build advertising profiles, we do not sell data, and we do not share it with anyone except the service providers listed below.
Children's information
BeeSync is used by adults — parents, teachers and school administrators. Children do not have their own accounts and are not asked to provide anything directly.
Information about a child is entered by their school under the school's own enrolment agreement with the family. If you are a parent and want to know exactly what your child's school has recorded, ask the school; every field is visible to them, and most of it is visible to you in the app.
Health and dietary information is treated as the most sensitive category in the system. It is visible only to staff at the child's own school and to that child's linked guardians. It is never used for anything but the care of that child.
Who can see what
Access is enforced by the database itself, on every single request, rather than by the app screens. In practice:
- A parent sees only their own linked children, and only at the schools those children attend.
- A teacher sees only the classes they are assigned to.
- An administrator sees only their own school.
- Nobody at one school can see data belonging to another school, even when the same person works at both.
We do not browse school data. A small number of operational actions — restoring a backup, diagnosing a fault a school has reported — require technical access to the database, and we limit those to what the task needs.
Service providers
BeeSync runs on infrastructure we do not own. These providers process data strictly on our instructions:
| Provider | What it does | What it sees |
|---|---|---|
| Supabase | Database, file storage, sign-in | All stored data, encrypted at rest and in transit |
| Cloudflare | Serves this website and the school portal | Ordinary web request data |
| Expo | Delivers push notifications to phones | The notification's title and short body, and the device token |
| Apple, Google | Distribute the mobile app; deliver notifications to the device | Standard app-store and push-delivery data |
| Email provider | Sends password resets and notification emails | Recipient address and message content |
Data may be stored on servers outside Lebanon, because these providers operate globally.
How long data is kept
- School records — for as long as the school keeps its BeeSync account, because a student's history is the point of the product. Schools can delete individual records at any time.
- In-app notifications — removed automatically once read and older than 90 days, and in all cases after one year.
- Deleted records — when a school deletes something, a copy is kept briefly in a restricted internal archive so an accidental deletion can be reversed. It is not reachable from the app and is not used for anything else.
- Server logs — a short rolling window, then discarded.
If a school closes its account, its data is deleted on the timetable set out in the Terms.
Your rights
Lebanon has no single comprehensive data-protection statute, so we have written these commitments into the product rather than relying on one. Whoever you are, you may:
- See what is held about you or your child — most of it is already visible in the app; ask us or your school for the rest.
- Correct anything wrong — your school can fix it directly, and that is usually same-day.
- Ask for deletion — see Delete your data.
- Get a copy of your data in a machine-readable format.
- Turn off notifications by category, in the app's settings, at any time.
Write to [email protected]. We aim to reply within 30 days. Where the request concerns records a school entered, we will coordinate with the school and tell you that we have.
Security
Data is encrypted in transit and at rest. Access rules are enforced in the database on every request, not in the app, so a bug in a screen cannot expose another school's records. Accounts are protected by passwords that we never see in readable form. Backups are taken daily.
No system is perfect. If we discover a breach affecting your data, we will notify the affected schools promptly and tell them what happened, what was affected, and what we are doing about it.
Changes to this policy
If we change something that materially affects how data is handled, we will update the date at the top of this page and notify schools through the portal before the change takes effect.
Contact
Write to [email protected] for anything on this page — privacy requests, corrections, or deletion.