Data processing agreement (DPA)
Agreement under Article 28 GDPR between the Customer (controller) and Refleko (processor). It is incorporated into the terms of use when you create the account; if you need a signed copy, write to privacy@refleko.com.
1. Purpose and duration
The Customer instructs Refleko to process personal data on its behalf to provide the service described in the terms of use. It lasts as long as the service is provided.
2. Nature and purpose
Hosting the directory and questionnaires, sending invitations and reminders, collecting responses, computing reports applying the anonymity rules, publishing them to whom the Customer or the assessed person decides, and exporting aggregate figures.
3. Data and data subjects
- Data: identification and contact details (name, email, job title, language, reporting line), evaluation responses and comments, context notes on each assessment, participation status, development plan (focus areas with their goal, why now, what others should notice, who helps and their review date, actions, check-ins, sessions and professionals' private notes), consented links, change and access logs, and technical usage data.
- Data subjects: people in the directory, assessed people, raters, people who ask for an evaluation through the Customer's form and account members.
- Special categories of data are not expected to be processed. The Customer will not request them in questionnaires nor write them in the development plan or in private session notes, which are not clinical records.
4. Refleko's obligations
- Process data only on the Customer's documented instructions (the terms of use and the configuration it sets in the service), and tell it if an instruction infringes the rules.
- Ensure confidentiality of those who access the data.
- Apply the security measures in the annex.
- Assist the Customer in answering data subjects' rights and, reasonably, in impact assessments and consultations with the authority.
- Notify the Customer without undue delay of any security breach affecting its data.
- Not use the data for its own purposes, except aggregate usage metrics without personal data. The optional survey a rater answers when they finish is not part of this agreement: Refleko collects it, anonymously and for itself (see the privacy policy).
- Make available to the Customer the information needed to demonstrate compliance and allow reasonable audits, with notice and at the Customer's cost.
5. Individual responses
The service is designed so that neither the Customer nor Refleko accesses raters' individual responses. Refleko does not offer and will not honour requests to extract them, except where legally required.
6. Sub-processors
The Customer gives general authorisation for the following sub-processors, with whom Refleko has a processing contract: Vercel (web hosting), Railway (API hosting), Supabase (database) and Resend (email). Sentry (technical errors, also from the application's browser) receives only technical data. Location: database in Frankfurt (Germany, EU) and API in the Netherlands (EU); the web app and API requests pass in transit through Vercel's global network; Resend and Sentry are US-based (safeguards in section 7). Refleko will give reasonable notice of changes and the Customer may object; if no agreement is reached, it may close its account.
7. International transfers
Any transfer outside the European Economic Area will rely on appropriate GDPR safeguards (an adequacy decision or standard contractual clauses).
8. End of service
When it ends, Refleko will delete the Customer's data (or return it, for example with the figures CSV) within a reasonable time and delete copies, unless the law requires keeping them. Individual responses are deleted earlier, according to the period set for each cycle (or kept if the Customer so chose).
Annex · Security measures
- Encryption in transit (HTTPS) across the application.
- Passwords stored only as a hash; session in an
httpOnlycookie. - Rater links and shared-report links stored only as a hash; the rater's draft encrypted with their link.
- Per-account data isolation, row-level security in the database and role-based authorisation on every route.
- Minimisation: responses do not record when they were submitted, and are linked to their author only when the rater is identified.
- Rate limiting, logs without secrets and scheduled purging of responses.