Privacy Policy
This policy explains how Gatehier ("Gatehier", "we") handles personal data in Kontour. It's written to meet Malaysia's Personal Data Protection Act 2010 (PDPA) and the EU and UK General Data Protection Regulation (GDPR).
1. Who is responsible
- For the personal data organizations put into Kontour about their people (for example staff and students), the organization is responsible (the "controller", or "data user" under the PDPA), and Gatehier processes it on the organization's behalf. Questions about that data are best sent to the organization first; we'll help them answer.
- For data about people who register an organization, contact us, or visit our website, Gatehier is responsible.
Contact: [privacy email] · Gatehier, [registered business address].
2. What we collect
| Data | Examples | From |
|---|---|---|
| Account details | Name, email address, password (stored only as a salted hash), role, teams | You or your organization's Admin |
| Organization details | Organization name and type, country, size, phone, website, the registering person's job title, verified domains | The person registering the organization |
| Agreements | Which version of these terms and policy was accepted, and when | You |
| Security data | Sign-in attempts (email and IP address), session records, verification and reset codes (stored only as hashes) | Your use of Kontour |
| Email delivery data | Whether an email we sent was delivered | Our email provider |
| Enquiries | Name, work email, organization, size and message from the contact form | You |
| Kontour Research submissions | Name, email, university, team, role, what you send about your research or product, links, and messages with us | You |
| Attendance (when available and switched on) | Check-in and clock-in times and places, check-in method, working hours, leave and timesheet changes | Gatehier Edge or your phone |
| Face templates (only with explicit consent, when available) | A mathematical template used to recognise your face at check-in. Never photos or raw video | You, with your consent |
We don't use advertising or tracking cookies, and we don't buy personal data from others.
3. Why we use it, and our legal bases
- To provide Kontour: creating accounts, signing in, organizations, teams, emails you need (such as verification and password reset). Basis: performing our contract with your organization, and our legitimate interest in providing the service to its people.
- To keep Kontour secure: limiting sign-in attempts, checking new passwords against known breaches, investigating misuse. Basis: legitimate interests and legal obligations.
- To bill and run the business: plans, trials, invoices, keeping records. Basis: contract and legal obligations.
- To answer enquiries sent through our contact form. Basis: legitimate interests, or steps before a contract.
- To review Kontour Research submissions, talk to the team that sent them and, if both sides want, agree a pilot or terms. Basis: legitimate interests, or steps before a contract.
- Face-based check-in, only if your organization switches it on and you give explicit consent. Basis: explicit consent, which you can withdraw at any time.
We don't sell personal data, use it for advertising, or make decisions with legal or similarly significant effects about you by automated means alone.
4. Face features and attendance
When attendance features become available: face-based check-in is optional for each organization and off by default. A face template is created only after you give explicit consent in Kontour, and for students under 18 also their parent's or guardian's consent. You can withdraw consent at any time, and your template is then deleted. You can always use phone check-in instead. Raw video from cameras is processed on the Gatehier Edge device and is never stored; only check-in results are kept. Alerts always go to a person for review.
5. Children
Only education organizations can add people under 18, and they confirm they have the consent of each student's parent or guardian where required. Children can't register on their own. Parents and guardians can contact the school, or us, about their child's data.
6. Who we share it with
We share personal data only with service providers that help us run Kontour, under contracts that require them to protect it and use it only on our instructions:
- Cloudflare, Inc.: hosting, database and network security.
- Brevo (Sendinblue SAS): sending emails such as verification codes, invitations and password resets.
- Stripe: taking payments for gigs and paying sellers. Stripe collects card or bank details itself (we never see them), checks sellers' identity for payouts, and keeps its own records under its privacy policy. We share the buyer's email address and what was bought, and the seller's email address when they set up payouts.
- Have I Been Pwned: checking whether a new password has appeared in a known data breach. Only the first five characters of a one-way hash of the password are sent, never the password or any personal data.
Within an organization, Admins can see the names, email addresses, roles and teams of people in their organization. We may also disclose data where the law requires it, or to protect people's safety or our rights. If Gatehier is involved in a merger or sale, data may transfer to the new owner under this policy.
7. International transfers
Our providers may process data outside Malaysia, including in the European Union and the United States. Where we do, we make sure the transfer is allowed under the PDPA (section 129) and the GDPR, using safeguards such as the providers' data processing agreements and standard contractual clauses.
8. How long we keep it
- Account and organization data: while the organization's subscription is active, then 30 days for export, then deleted (backups follow their normal schedule).
- Sessions: up to 30 days. Verification codes and links: up to 24 hours. Password reset links: 1 hour. One-time passwords: 7 days.
- Records of failed sign-ins: cleared after a successful sign-in and, in any case, kept no longer than needed for security.
- Records of accepted terms: for as long as the account exists and as needed to show what was agreed.
- Contact form enquiries: up to 24 months.
- Kontour Research submissions: while they're open; declined or withdrawn ones are erased 3 years after they close; agreed ones are kept with the agreement.
- Invoices and billing records: as long as tax law requires (in Malaysia, generally 7 years).
9. How we protect it
Each organization's data is kept separate. Passwords are stored only as salted hashes; codes and links are single-use and stored only as hashes; connections are encrypted; and access is limited to people who need it. Read more on our Security & privacy page.
Gatehier staff access. Gatehier staff may access account information to run and support Kontour, and, when investigating abuse, safety or security issues or responding to a legal request, private messages. Access to messages is limited to specific staff, needs a recorded reason each time, lasts no longer than needed, and every access is recorded in a log that can't be changed.
How Kontour is used. We record which days and hours you use Kontour and on what kind of device, to understand how it's used overall. Gatehier staff only see totals. This is kept while your account exists.
Assignments and grades. Teachers in a Space see the work you hand in there and grade it; your organization's admins with permission can see grades. If your account is deleted, work you handed in stays with the assignment for its teachers, shown as from a deleted account.
Signing in with Google or Microsoft. If you choose to, Google or Microsoft tells Kontour your name, email address and an account number for you there; they don't share your password or anything else. Kontour keeps that account number and email to recognise you next time, and you can unlink it in your settings.
Attendance. Leaders of a course, class or team see who checked in to each session and mark attendance; you see your own. If a session asks you to be at a place, your device is asked where you are only when you check in (never in the background). The exact spot where you checked in is shown to you and to that course, class or team's leaders on a map, and is erased after 30 days; after that only whether you were inside the place and how far away you were is kept. Online classes never ask where you are. Admins can see the places set up for your organization. When an admin searches the map to add a place, the words they type are sent from Kontour (not from their device) to OpenStreetMap's search service, with only a nearby area to prefer, never who is searching.
Checking it's really you, there. Some check-ins ask you to scan a code shown on your teacher's or manager's screen, which changes every 10 seconds. To spot faked locations and one phone checking in several people, Kontour keeps, with each check-in or clock-in, a scrambled form of a random number your browser makes for itself (not anything that identifies your phone to others), and a note if the location looks faked (for example impossibly exact, typed in, or too far from your last check-in for the time between). Your teachers, managers and admins can see these notes.
Visitors. If you sign in as a visitor at an organization's gate or reception, it keeps your name, the phone number or email you give, your company, why you came, whom you visited and when you arrived and left, for its visitor records. The person you visit is told you've arrived. These details are erased after the organization's chosen time (90 days unless it chooses otherwise, between 7 and 365) and aren't used for anything else.
Passkeys. If you add a passkey, we keep only its public key, a name for it (like "iPhone"), when it was added and last used. Your face, fingerprint or screen lock never leave your device and we never see them.
Birthdays and work anniversaries. If you choose to share your birthday, we keep only its day and month (never the year) and show it to people in your organization under Celebrations around that day. You can stop sharing it any time in Settings. Work anniversaries come from the date you joined your organization on Kontour.
Wellbeing check-ins. If you answer "How are you today?", your answer (a number from 1 to 5), any note you add, and whether you asked to talk to someone are kept for 90 days. Only the people your organization chose to handle safe reports (and its Owner) can see them: daily averages without names, and by name only the check-ins where you chose "Not good" or asked to talk. Answering is always up to you.
Safe reports. If you report a concern (such as bullying or harassment) you choose how. Anonymous: we don't store who sent it; you get a secret code, shown once, and anyone with that code can read the replies, so keep it safe (we can't recover it). Confidential: your name is kept with the report and shown only to the people your organization chose to handle reports, so they can reply to you. Only those people can read reports; each time one of them opens a report is logged and they can see that log. Reports stay until the organization or account is erased. We look at reports ourselves only if the law requires it.
Careers. If your organization has the Careers board on, you can apply for jobs that organizations post. Applying shares with the people who post jobs at that organization: your profile as the public would see it (even if your profile isn't public), your email address, and the note you write. They can see this while your application stands; withdrawing stops them opening your profile. If you say you're open to work, what you're looking for is shown to people who post jobs (and, if you choose, to everyone who can see your profile), and employers can find you only if your profile is public or they're in your organization. Following someone or endorsing their skills is visible to them and counted on their profile. We don't sell this to anyone or use it for ads.
Gigs. When you sell or buy a gig we keep the gig, the order (what was asked for and delivered, messages between you, the amount, the fee, refunds and payouts), reviews, and, for sellers, the ID of your Stripe account and whether Stripe can pay you. Payments are handled by Stripe (see who we share it with). If there's a dispute, Gatehier staff read the order and its messages to settle it. We keep orders for 7 years for tax and accounting, even if a gig is removed.
Sponsored posts. Ads on Home are chosen only by the kind of organization you're in (for example a university or a company) and whether your organization allows ads. We never use what you post, message, study or your grades to choose ads, and advertisers never learn who you are: they see only how many people saw and clicked their ad, by day. We keep which ads you hid or reported, and count a view once per person per day (that record is kept for 90 days). If you advertise, we keep your ad, its budget and results, and Stripe takes the payment.
Receipts. For every payment, refund and payout on Kontour we keep a receipt (what it was for, the amount, the fee, the date, and the email it was sent to) and email it to you; Stripe also emails its own receipt. People who manage your organization's settings see receipts for what the organization paid for. We keep receipts for 7 years for tax and accounting.
Live meetings. Video, audio and screen sharing in meetings travel through Cloudflare's network (Cloudflare Realtime) between the people in the meeting; we don't record them unless a leader starts a recording, which everyone is shown; a recording is saved to that leader's Kontour Drive. When a leader turns captions on, your browser sends a few seconds of your own microphone at a time (never while you're muted) to Cloudflare Workers AI to be turned into text; the audio isn't kept, and the captions are shown to everyone in the meeting and kept as its transcript, which people in that course, class or team can download. We keep who joined and left a meeting and when (to take attendance for meetings a leader starts), raised hands while it runs, and the meeting chat, which the people in that course, class or team can see. In meetings, leaders can see, for each person, how long they were in it, how many times they raised a hand, how many chat messages and poll answers they sent (and quiz answers they got right), and whether they answered "Are you still there?" checks. Whiteboard drawings and polls are kept with the meeting. Your browser asks before using your camera, microphone or screen.
Meetings with a code, and guests. Anyone in an organization can start a meeting, which gets a code and a link; each person also has their own room with a code that doesn't change. People who join with a code from outside the organization (including guests without an account) wait in a lobby until the host lets them in. For a guest we keep only the name they give and a temporary account for that meeting, which we erase a day after the meeting ends; guests see the meeting's video, chat and people while they are in it, like anyone else in it. When someone schedules a meeting and invites you (or a course, class or team you're in), you're notified and the meeting is added to your personal calendar, which you can remove like any other event.
Live streams. Organizations can broadcast live through Cloudflare Stream to the public, to their own people, or to chosen courses, classes or teams (schools only to the public when an admin allows it). Hosting sends your camera, microphone or screen (or the stream from software like OBS) to Cloudflare Stream; Cloudflare keeps a recording so the stream can be watched again by the same audience. We keep the stream's title, who hosted it, its live chat (hosts can hide messages) and, while it runs, a random id for each viewer to count who's watching (the most at once is kept). Signed-out people can watch public streams but can't chat.
Parents (schools). A parent's account is linked to a student only when both the school and the parent agree: the school invites the parent by email (we then email them a link to accept, or to set up an account), or the student makes a family code that the parent enters and the school approves. We keep who is linked to whom, how (Mother, Father, Guardian and so on), who approved it and when. A linked parent can see that child's attendance, the grades their teachers have returned, the school's announcements (posts to everyone, and teachers' posts in the child's courses, classes and teams) and the school and class calendars; never the child's messages, files, posts or personal calendars. The student can see who is linked to them. The parent or the school can remove a link at any time. Parent accounts made only for one school are erased with that school.
Parents and teachers. A linked parent and their child's teachers (and the school's people managers) can write to each other about that child; we keep those messages, who sent them and when, and who has read them. When a parent excuses an absence or a class ahead, we record it in the attendance register with their name, relationship and reason, and the class's teachers are told. When a school asks for consent (for example for a trip), we keep each child's answer, which parent gave it, any note they add and when; the teachers who asked (and the school's people managers) can see the answers.
Your devices. For each device you're signed in on, we keep which browser and system it is (from what your browser tells every website), the city and country your connection appears to come from (from Cloudflare; never a precise location), and when it was last used, so you can see them in Settings → Your devices and sign any of them out. This goes when that device is signed out or the sign-in expires.
Profile insights and recommendations. When someone opens your profile we count it for you: one view a day for each signed-in person, and each visit by someone signed out, plus which kinds of link people open on it (for example "LinkedIn" or a Featured item, never the address). Only you see these numbers. You see the names of people in your organization who looked only if they turned on "Show my name when I look at other profiles" (off unless they turn it on); nobody else's name is ever shown. Views and link counts are deleted after 90 days. Colleagues can write you a recommendation; it shows on your profile only after you approve it, with their name, and you can hide it at any time; the person who wrote it can delete it.
Certificates. When an organization gives you a certificate (for finishing a course, class or team, for an event, or an award), we keep its title, your name as printed, who gave it and when, and a code. Anyone with the code (it is printed on the certificate as a QR code) can check it at our verification page, which shows your name as printed, the title, the organization, who gave it, when, and whether it was revoked; and a link to your profile only if your profile is public. You choose whether each certificate shows on your profile. The organization can revoke a certificate with a reason, which the verification page then shows.
Clocking in and out. If your organization has your role clock in for work, Kontour keeps when you clocked in and out each day, the hours you were expected to work, any leave marked for you, and requests you make to correct a day. If clocking in needs you to be at a workplace, your device is asked where you are only when you clock in; the exact spot is kept for 30 days and then only the distance from the workplace stays. You see your own timesheet; people your organization allows to manage attendance see everyone's, can change a day only with a reason, and every change is logged.
My Drive. Files in your Drive are seen only by you and the people you share them with. Things you delete stay in your Trash for 30 days, then they're erased. If your account is deleted, your Drive is erased, except files and folders you shared with others: those stay for them, shown as from a deleted account, until nobody they're shared with is left.
10. Your rights
Depending on where you are, you have the right to:
- access the personal data we hold about you, and get a copy;
- correct data that's wrong or incomplete;
- ask us to delete it, or to limit how we use it;
- receive it in a portable format;
- object to processing based on legitimate interests;
- withdraw consent at any time (for example for face features), without affecting what happened before;
- complain to a data protection authority: in Malaysia, the Personal Data Protection Commissioner; in the EU or UK, your local supervisory authority.
If your data is in Kontour because of your organization, contact your organization's Admin first; we'll support them. Otherwise email [privacy email]. We'll reply within 21 days (PDPA) and in any case within one month. We may need to confirm your identity first.
Under the PDPA, giving us your account details is necessary for us to provide Kontour; if you don't, you won't be able to use it.
11. Cookies
Kontour uses one essential cookie to keep you signed in. It's secure, can't be read by scripts, and expires after 30 days or when you sign out. We don't use analytics, advertising or tracking cookies.
12. Changes to this policy
We'll update this policy when our practices change. Each version has a date at the top of this page. If a change is significant, we'll tell organizations in advance and people may be asked to read the new version when they next sign in.
13. Contact us
Gatehier, [registered business address]. Email [privacy email].