InternROIINTERNSHIP MANAGEMENT PLATFORM

Privacy notice

Last updated 22 November 2026

1. Who this is about

InternROI (the Internship ROI, "the Service") is operated by Opportunities Nearby FZE, Sharjah Research Technology and Innovation Park (SRTIP), Sharjah, United Arab Emirates — Licence No. 11131 ("we").

Different relationships matter here, and they carry different duties:

This split follows the controller and processor definitions in the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021 — the "PDPL"), which applies to us as an SRTIP establishment, and it holds: we are controller for account holders, and processor for the people an employer adds and for what a school records about its students. Because the PDPL requires a processor to act on the controller's documented instructions, we put a written data-processing agreement in place with each customer — if your organisation does not have one yet, ask at the address in section 10 and we will provide it. Where another regime also applies to a customer — the GDPR, or the DIFC or ADGM data-protection laws — that agreement is where its requirements are addressed.

2. What the Service stores

Everything the Service holds falls into these groups.

Analytics. With your consent, the Service uses Google Analytics (GA4) to understand how its pages are used. Nothing from Google loads until you actively accept a banner shown on first visit; declining, or leaving it unanswered, leaves the Service exactly as before — no Google script runs, and no cookie is set beyond the one that keeps you signed in. The Service sets no advertising or profiling cookie of any kind, and analytics data is never sold.

Page performance. Separately, and for every visitor, Cloudflare — which already serves the Service (section 3) — measures how quickly pages load, with a small script of its own (Cloudflare Web Analytics). It reports which page was loaded and the page before it, how long it took, and the browser, operating system, device type and country. It sets no cookie and stores nothing on your device, and Cloudflare discards the internet address the report comes from rather than storing it. We see only counts and averages, never a single visit.

3. Where it is stored, and who else touches it

The database and uploaded files are hosted on Supabase in the eu-central-2 region (Zurich, Switzerland). The application itself is served by Cloudflare from its global edge network, and a nightly copy of uploaded files is kept by Cloudflare in the European Union. This means personal data about people in the United Arab Emirates is stored outside the UAE.

Switzerland was chosen for this reason. It holds an adequacy decision from the European Commission and appears on the lists of adequate jurisdictions published by the ADGM and the DIFC, and its own Federal Act on Data Protection applies to the data while it is there.

The UAE Data Office has not yet published the PDPL's executive regulations or an adequacy list of its own. Until it does, we rely on Article 23 of the PDPL, which permits a transfer out of the UAE under a contract holding the recipient to the PDPL's standard of protection: Supabase's data-processing addendum, which incorporates the EU standard contractual clauses, is that contract, and Swiss data-protection law applies to the data while it is in Zurich. If the Data Office publishes rules that ask for more, we will comply and update this notice.

Our processors are:

Consent is the basis for this transfer, and it suffices: Article 23 of the PDPL permits a transfer made with the data subject's express consent, and nothing is sent to Google unless a visitor actively accepts the banner. For visitors protected by the GDPR, Google LLC is additionally certified under the EU–U.S. Data Privacy Framework, which the European Commission has found adequate. Declining the banner keeps this paragraph from applying to you at all.

We do not sell personal data, and we do not share it for anyone else's marketing.

4. Who can see what

Access is enforced in the database itself, not only in the interface, so a person cannot reach data by guessing a web address:

Schools. A school sees a student only after the student has named the school (it then sees the name and email address they gave) and the school has confirmed them. It then sees facts about the student's current or latest placement: the company, programme, department and dates; planned hours; tasks assigned, accepted and overdue; work reviewed, and when work was last submitted; weekly reflections counted, not their words, and when the last was written; whether their final report is in; and whether the placement is complete. It never sees pay or company figures. Only if the student switches on "Share my supervisors' ratings and whether they would work with me again" when linking (and at any time after) does the school also see the average of the supervisors' ratings and each supervisor's answer to "Would you work with this intern again?", with that supervisor's name. Switching it off stops both at once — except in a completion report already issued, which keeps what it said, and in any notice already sent. A school never sees check-ins, written feedback or endorsements.

An intern's own record. An intern can share a verified record of their completed placements by link or QR code. A separate switch on their profile, "Share my supervisors' ratings and endorsements on my CV and record", decides whether that record, and the certificate printed from it, also show the supervisors' ratings, their answers to "Would you work with this intern again?" with their names, the skills they endorsed with their names, and the school that confirmed the intern during the placement. Anyone holding a live link sees the record; with a withdrawn or expired link they see only the intern's name and the date it ended. Supervisors: your name appears beside your answer and your endorsements wherever the intern shares them.

A supervisor, once a placement is complete, sees the list of skills on the intern's own profile, so they can endorse the ones they saw at work. Nothing else on the profile is shown to anyone but the intern, except to a company the intern applies to, as below.

A company an intern applies to. Applying to an opening shares these facts with that company while the application stands: the intern's name, email address, education (level and institution), emirate, skills, languages and summary, and whether they are under 18 — never their date of birth or a guardian's details. The apply page says so before the intern applies. The company's admins are told of each application by a notice naming the opening and the applicant. The company may decline the application, which the intern sees as closed, or accept them onto one of its programmes, which invites them by email to join it. If it accepts them, it keeps seeing those facts only while the place it offered is open — while its invitation can still be accepted, or once the intern has joined that programme. An intern can withdraw an application at any time until they join the programme: the company then still sees that an application was made and withdrawn, but none of the facts, and an invitation it sent is cancelled. Two records stay with the company, as its own: the notices its admins were sent about the application, which name the applicant and the opening; and, if it had accepted them onto a programme that had already handed out its tasks, their place on that roster, switched off, with the name and email address the invitation went to (on a programme that has since finished, the place is left as it was). A place whose invitation expires stays on the roster until an administrator removes it or the intern withdraws the application. A declined application cannot be withdrawn; nor can one whose programme the intern has joined — to leave that programme, they ask the company to remove them. A company never sees an application to another company's opening.

Programme activity. Administrators always see a programme's recent activity — who submitted work, who reviewed it, and who joined. An administrator may choose to show it to supervisors and interns as well: a supervisor then sees it for the interns assigned to them, and an intern for their own work only. It is off unless an administrator switches it on, and it never shows a cost or return figure.

Uploaded files are held in private storage with no public address. When a file is opened, the Service issues a link that expires after five minutes.

5. Report share links

An administrator can create a link that shows a generated report to someone without an account. Anyone holding that link can read the report until it expires or is withdrawn, so it should be treated as confidential.

A shared report contains programme-level figures — cost, return, delivery counts and KPI results. It does not name individual interns and does not include their submissions, feedback or individual ratings. The Service records when a link is opened and how many times, and keeps that record after the link is withdrawn.

An administrator can also have the Service email a share link to one address they type in. That address is used only to send the email: the Service does not store it, and our email processor keeps its usual delivery record.

6. How long it is kept — and what cannot be deleted

Some records in the Service are deliberately permanent. Submissions, reviews, ratings, KPI measurements, saved ROI snapshots and the audit log are append-only: the software refuses to delete or rewrite them, so that a performance record cannot be quietly altered after the fact and a report can always be reproduced from what was true when it was generated.

Weekly reflections, supervisors' check-ins, their answers to "Would you work with this intern again?", skill endorsements and a school's completion reports are append-only too. A completion report is a frozen document: it cannot be altered to remove a name. It is the school's record, so an erasure request that reaches one goes to the school; if the school instructs it, the request is met by deleting the school's account in full, which is the only way the Service can remove a report.

That protection has a cost, and we would rather state it than hide it: a request to erase an individual's assessment history cannot be satisfied by deleting those rows. Where erasure is required by law, it would have to be met by removing the identifying fields that link a record to a person, or by deleting the organisation's account in full.

Retention periods are:

Erasure requests go to the address in section 10 and are executed by us within 30 days: for the append-only records above, by removing the fields that link a record to a person (a completion report excepted, as above); for everything else, by deletion. Where an employer or a school is the controller, we act on its instruction.

7. Your rights

Subject to the law that applies to you, you may ask for a copy of your data, ask for inaccurate data to be corrected, object to or restrict how it is used, or ask for it to be deleted — bearing section 6 in mind. If an employer or a school entered your data, please ask them first; we will help them respond.

You can correct your own name at any time on the My account screen. An intern with their own account corrects their profile — date of birth, guardian, education (level and school), emirate, skills, languages and summary — on the My profile screen.

8. Young people

Interns are often students and may be under 18. An intern who creates their own account is asked for their date of birth, and must give it before applying to an opening, linking to a school, downloading their CV or creating a link to their verified record, so that the Service can apply one rule: an intern under 18 must have a parent or guardian on their profile, and the profile cannot be saved without one. The guardian's name and email are kept only while they serve that purpose — until 30 days after the intern's 18th birthday — and are then cleared automatically.

A minor's profile is read by them alone, with two exceptions: once a placement is complete, their supervisor sees the list of skills on it, to endorse the ones they saw at work; and a company they apply to sees the facts listed in section 4 while the application stands, or while the place it accepted them onto is open, including that they are under 18 — never their date of birth or their guardian's details. A school they have linked to reads facts about their progress, never the profile, and only after the school has confirmed them. A minor's verified record leaves the Service only through a link they choose to create, and they can withdraw it at any time.

Where an employer adds an intern, the employer remains responsible for having a lawful basis to record their work. For UAE programmes, the Labour Law (Federal Decree-Law No. 33 of 2021) requires an employer taking on anyone aged 15 to 17 to hold a juvenile work permit and the written consent of the person's guardian, and that consent must cover the recording of the intern's work and performance that the programme involves. We hold no more data about a minor than about any other intern, and every protection in this notice applies equally. An employer — or a school — operating under another jurisdiction's rules on children's data is responsible for meeting them before adding or linking a minor.

9. Security

Access rules are enforced by the database on every read and write. Files are private by default and reachable only through short-lived links. Passwords are stored as hashes. Administrative actions are written to an append-only audit log.

No system is perfectly secure. If a breach affects your data, we will act on the notification duties that apply to us. If a breach is likely to prejudice your privacy or the security of your data, we will notify the UAE Data Office and — where the risk to you is serious — you directly, without undue delay and in any event within 72 hours of becoming aware of it. The PDPL sets no numeric deadline until its executive regulations are published; 72 hours is the strictest standard among the regimes that touch this Service, so it is the one we adopt. Where we hold data as an employer's processor, we notify the employer without undue delay so it can meet its own duties.

10. Contact and changes

Questions about this notice or a request about your data: support@internroi.com, Block B, B55-200, Sharjah Research Technology and Innovation Park (SRTIP), Sharjah, United Arab Emirates. A Data Protection Officer is not currently required, and none is appointed: the PDPL requires one only for high-risk processing — large-scale or systematic evaluation of sensitive personal data, or novel technologies — and performance records are not sensitive data as the PDPL defines it, nor is our scale large. Privacy questions sent to the address above reach the people who operate the Service directly. We will revisit this when the executive regulations are published or if what we process changes.

If we change this notice, we will update the date at the top and, where the change is significant, tell account holders directly.

InternROI · Privacy · Terms