Privacy Policy

1.Who we are, and what this policy covers

KemeTrip is a platform operated by [[LEGAL_ENTITY_NAME]]. It introduces schools to licensed travel agencies and gives them the tools to agree a school trip, build a roster, and collect guardian consent.

This policy explains what personal data we hold, why we hold it, who can see it, and how you can have it removed. It is written to be read by a parent or a school principal, not only by a lawyer.

The most important part of this policy is the next section, because it is about children.

2.We process children's data — plainly stated

Yes. To run a school trip on this platform we hold personal data about the students taking part.

For each student we hold: their full name, their class or grade, and their guardian's name, phone number, and email address where the school provides them. We also hold what that student's trip is, its dates, whether their guardian approved or declined, and the amount recorded as due for them.

We do not ask for and do not hold a student's national ID number, date of birth, address, photograph, medical information, religion, exam results, or any other school record. If a school enters such information into a free-text field anyway, it should not — and we ask schools not to.

The data is entered by the school, not by us. The school is responsible for having the authority to enter it.

3.Our lawful basis: the guardian's explicit consent

For a student's participation in a trip, the lawful basis is the explicit consent of that student's parent or guardian, given through the consent link the school sends them.

When a guardian makes a decision we record: the decision itself (approved or declined), the date and time it was recorded, the IP address the decision came from, and the version of the consent text that was shown on screen at that moment.

We record the version of the text so that the record cannot be quietly rewritten later. If we change the wording of the consent page, past decisions keep the version they were actually given against. That is what makes it a record and not a claim.

The IP address is kept as part of the audit trail of the decision. It is never used to identify a person, to locate them, to profile them, or to decide anything about them.

For school staff and agency staff who hold accounts, our basis is the contract and our legitimate interest in operating the platform they asked to use — not consent.

A guardian who withholds consent simply has no participation record created for their child beyond the roster entry the school made. Consent can be withdrawn at any time by telling the school.

4.The parent link

A guardian does not need an account and does not need a password. The school sends them a private link, and holding that link is what opens their child's page.

Because holding the link is what grants access, the link should not be forwarded — not to a family group, not to another parent. Anyone who has it can see that child's trip details and record a decision.

We never store the link itself. We store only a one-way cryptographic hash of it, so the link cannot be reconstructed from our database by us or by anyone who obtained a copy of it. This also means we cannot resend a link we have already issued: we can only issue a new one.

A school can issue a new link at any time — for example if the old one was lost or shared by mistake. Issuing a new link immediately stops the old one from working. A decision already recorded is kept.

The consent page is built so that opening it does not send the link to anyone else: it makes no requests to third-party services, it asks search engines not to index it, and it instructs the browser not to pass the address on to any site the guardian visits next.

WhatsApp messages to guardians are sent by the school from the school's own phone. KemeTrip does not send WhatsApp messages to guardians and has no access to the school's WhatsApp account.

5.Who can see a child's data

Three parties, and no one else:

• The child's own school — the staff at that school who hold accounts on the platform.

• The agency awarded that child's trip — because it has to know who is travelling in order to run the trip. An agency sees the roster only for a trip it has actually been awarded.

• KemeTrip's administrators — a small number of people who operate and support the platform.

Not other schools. Not agencies that were not awarded the trip, including agencies that bid for it and lost. Not other parents. Not the public.

This separation is enforced in the database itself, not only in what each screen chooses to display. We do not sell personal data, we do not share it for advertising, and we do not use it to train any AI model.

6.Data about school and agency users

For a person who holds an account — a school coordinator, a school administrator, or an agency owner — we hold their name, email address, phone number, the institution or agency they belong to, and their role.

For an institution or an agency we hold the information given in its application, including its official contact details and, for an agency, its tourism licence number. An agency's licence number is held for verification and is never shown to schools or to the public; schools are shown only that an agency is licensed.

We also keep ordinary technical records generated by using the service, such as security and error logs.

7.No location tracking

The trip tracker does not track anyone's location. We say this explicitly because it is the first thing parents ask.

The platform records checkpoints — for example departed, arrived, on the way back, back at school. A checkpoint is a status marked by a person accompanying the trip, together with the time it was marked.

We do not collect GPS coordinates. We do not follow a vehicle. We do not access any student's or any guardian's device location. There is no live map of where a group is, and no such data exists to be requested, leaked, or handed over.

8.Payment data

KemeTrip does not collect or store card numbers, and never has.

Payment for a school trip is currently arranged directly between the school, the agency, and guardians. Where that happens outside the platform, we hold no payment data about it at all beyond what the school records as owed and received.

Where online payment through the platform is enabled, card details are entered on the payment provider's own hosted page and are handled under its security standards. We receive only the outcome — an amount, a reference, and whether it succeeded — and never the card details.

9.Service providers we use

We rely on a small number of providers to run the platform. Each processes data only as needed to deliver its service:

• Supabase — database, authentication, and file storage.

• Vercel — hosting and delivery of the website.

• Resend — transactional email, such as an award notification or a status message.

• Upstash — rate limiting, which protects the platform against abuse.

• Kashier — payment processing, when online payment for school trips is enabled. Kashier is not processing payments for school trips at the date shown at the top of this page.

We do not use analytics products, advertising networks, or tracking pixels, and we do not send any student's or guardian's data to an AI service.

10.How long we keep it, and how to have it removed

A participant record — a student, their guardian's contact details, and their consent decision — is kept while the trip is being arranged and delivered, and for [[RETENTION_PERIOD_AFTER_TRIP]] after the trip ends, so that the school and the agency have a record of who travelled and on whose permission. After that period it is deleted or irreversibly anonymised.

Records we are required to keep for longer by Egyptian law — for example accounting records — are kept for the period the law requires, and for no other purpose.

An account holder's data is kept while the account is open, and for the period above after it is closed.

A guardian may ask for a copy of what we hold about their child, or ask for it to be corrected or deleted, by contacting their school, or by contacting us directly at info@kemetrip.com. Where the request comes to us we will verify that it comes from that child's guardian before acting on it. We may need to keep a minimal record that a student travelled where the school or the agency is required to hold it.

Deleting a consent record does not undo a trip that already happened, and a school may be required by its own rules to keep proof that permission was given.

11.Your rights

We handle personal data in line with the Egyptian Personal Data Protection Law (Law No. 151 of 2020) and other applicable regulations.

You have the right to know what we hold about you or about your child, to have it corrected, to have it deleted, to withdraw a consent you gave, and to object to how it is being used. To exercise any of these rights, contact us using the details at the end of this policy. We do not charge for this.

If you are not satisfied with how we have handled a request, you may complain to the competent Egyptian data protection authority.

12.Security

Access to data is restricted at the database level according to who you are: a school can reach only its own students, an agency only the trips it was awarded, and a guardian only the child whose link they hold.

Consent links are stored only as one-way hashes. Connections to the platform are encrypted. Administrative access is limited to the people who need it to operate the service.

No system is perfect. If a breach occurs that affects personal data we hold, we will notify the affected schools and, where required, the competent authority, in accordance with Law No. 151 of 2020.

13.Cookies

KemeTrip uses only essential cookies, to keep an account holder signed in and to secure their session. We do not use third-party analytics or advertising trackers.

The consent page a guardian opens does not require them to sign in and does not set any tracking cookie.

You can control cookies through your browser settings, though disabling essential cookies will prevent signing in.

14.Individual traveller marketplace

This section applies only where KemeTrip's individual traveller marketplace is available to you. That marketplace is currently not open to the public; this section is kept here so that it is accurate if and when it is enabled, and it does not apply to school trips or to students' data.

For an individual traveller we collect the information they provide directly, including full name, email address, and phone (WhatsApp) number when they create an account. For each booking we collect a national ID number to verify the traveller's identity and to obtain the security permits that some trips require. We also collect trip preferences, search history on the platform, and the messages exchanged with agencies, along with limited technical data.

In that marketplace, payments are processed by Paymob, which handles card details under its own security standards; card information never passes through or is retained by KemeTrip. The AI travel assistant is powered by Google Gemini, and no payment data is ever sent to it.

Booking details are shared with a travel agency only for a trip actually booked with that agency, and only to the extent needed to deliver that trip.

National ID numbers are kept for the retention period of the associated booking record, for identity verification and accounting purposes, and a traveller may request deletion of that data by contacting us.

15.Changes to this policy

We may update this policy. The date of the latest revision is shown at the top of this page.

If a change affects what a guardian is agreeing to, the consent text is versioned separately, and decisions already recorded keep the version they were given against.

16.Contact us

For any question about this policy, about what we hold, or to make a request about your data or your child's data, contact us at info@kemetrip.com, or on WhatsApp at +2 01226692062.

If your question is about a specific student or a specific trip, contacting the school first is usually faster — the school holds the record and can act on it directly.