Legal
Privacy Policy
Effective Date: November 1, 2025
Table of Contents
1. Controller and Processor Roles2. Categories of Personal Data3. Legal Bases of Processing (GDPR Art. 6)4. Automated Decision-Making & Profiling (Art. 22)5. International Transfers6. Data Retention7. Subprocessors8. Security Measures9. Cookies & Marketing10. Children's Data11. Updates & Versioning12. Contact
This Privacy Policy explains how Princep Pte. Ltd. ("Flowmingo"), registered at 966 Hougang Ave 9 #12-596, Singapore 530966, collects, processes, and protects personal data in compliance with the EU General Data Protection Regulation (GDPR).
1. Controller and Processor Roles
For candidate data provided to recruiters (such as CVs, pre-screening responses, interview responses, videos, and other related materials), Flowmingo acts both as a processor (on behalf of recruiters) and as a controller of its own copy of that data which it retains for platform operation and compliance purposes.
In its processor role, Flowmingo processes candidate data strictly on recruiter instructions.
In its controller role, Flowmingo may retain and process its own copy of candidate data for limited and clearly defined purposes (e.g., platform security, quality assurance, legal compliance) and will honor candidate requests under GDPR for that copy.
Where recruiters are the controllers (e.g., evaluation reports generated for recruiters), Flowmingo will forward Data Subject Access Requests (DSARs) and enforce follow-up through internal escalation if recruiters fail to act.
In limited cases where Flowmingo and recruiters may jointly determine specific purposes, such as co-developing interview models, the parties may act as joint controllers. Where this applies, Flowmingo will ensure that the essence of the arrangement under Art. 26 GDPR is accessible to candidates upon request. In most other cases, Flowmingo's roles as controller (for its own copy of data) and processor (for recruiter-owned data) are clearly separated as described above.
For candidate-paid services (evaluation reports or assessment tests purchased directly by candidates), Flowmingo acts as a controller.
For recruiter account and billing data, Flowmingo acts as a controller to manage accounts, billing, and service provision.
DCP controller split (important). For recruiter‑run interviews, Flowmingo generally processes candidate data on behalf of the recruiting organization to provide the recruitment service (i.e., as a processor, where applicable). By contrast, if a candidate opts in to the DCP, Flowmingo processes the DCP dataset for a separate, consent‑based controller purpose with separate access controls. Recruiters cannot view who opted in. Recruiter deletion/DSAR instructions do not automatically delete DCP datasets unless the candidate also withdraws (and vice versa).
2. Categories of Personal Data
Candidate Data (examples include, but are not limited to):
- CV details (name, email, work/education history, contact details)
- Pre-screening question responses
- Written and video/audio interview responses
- AI evaluation reports/assessment test results purchased directly by candidates (Flowmingo is the controller)
- AI evaluation reports generated for recruiters (Flowmingo is a processor; recruiter is the controller)
- Other information voluntarily provided by candidates during interviews or assessments (e.g., references, portfolio links, or additional documentation)
Recruiter Data (examples include, but are not limited to):
- Account details and login credentials
- Billing and payment information
- Recruiter AI evaluation activity logs
- Candidate CVs or information uploaded directly by recruiters
- Stored interview questions and interview sets created by recruiters
Technical Data (examples include, but are not limited to):
- Device information, IP addresses, browser/device identifiers, cookies, cache, and diagnostic logs
Optional Data Contribution Program (Consent‑Based)
This is optional and separate from recruitment. Flowmingo may offer candidates an optional "Data Contribution Program" ("DCP"). If a candidate opts in, Flowmingo (as an independent controller for DCP purposes) will create a de‑identified / pseudonymised dataset derived from the candidate's interview responses and may share that dataset with trusted organizations that use data to develop and evaluate AI systems. Opting in is not required to complete an interview or to be considered for a role, and the hiring company is not shown whether a candidate opts in.
Data categories included (DCP)
- Interview recordings (audio and video, where recorded/collected) and corresponding transcripts (where generated).
- Limited technical/quality metadata (e.g., duration, language label, quality metrics).
- Generic question context (e.g., competency tags, paraphrases, or template identifiers) that does not identify the hiring company.
Purposes
- AI training, AI evaluation, benchmarking, quality assurance, safety testing, and related research and development.
- Creation of derived artifacts that do not identify individuals (e.g., aggregate statistics, evaluation results, model improvements).
Lawful basis
DCP processing is based on consent. Where required by law (e.g., higher‑risk categories), we rely on explicit consent. Refusal or withdrawal does not affect the candidate's job application.
Sharing, onward transfers, and international transfers
DCP datasets may be shared with trusted organizations globally. We require contractual restrictions designed to prevent attempts to identify individuals, prohibit using the data to make decisions about any individual (e.g., employment/credit/insurance/housing), and restrict onward transfer/resale except with Flowmingo's written authorization. International transfers are handled using appropriate safeguards where required (e.g., contractual clauses and security measures).
Retention, release versioning, and withdrawal
- Retention: we retain DCP datasets only as long as reasonably necessary for the purposes above, subject to legal obligations and documented retention schedules.
- Versioning: DCP datasets may be released in versions. Verified withdrawals apply to future releases after withdrawal is processed.
- Withdrawal: candidates can withdraw consent at any time through the method described in the DCP screens or by contacting us. After verified withdrawal, we stop including the candidate's contribution in future DCP dataset releases. Practical limits: if a dataset version has already been shared and used to develop models or other derived artifacts, it may not be feasible to remove its influence from already‑developed models or artifacts.
De‑identification is risk‑based
"De‑identified / pseudonymised" means we take reasonable steps to remove or reduce direct identifiers (e.g., names, emails, phone numbers, addresses, government IDs) and limit linkability. De‑identification reduces risk but may not eliminate it completely, especially for audio (and video, if enabled). We apply technical and organizational safeguards and exclude certain content from DCP releases (including direct identifiers and categories of sensitive information) unless we obtain explicit consent and can justify inclusion.
3. Legal Bases of Processing (GDPR Art. 6)
| Processing Activity | Legal Basis |
|---|---|
| Candidate account creation & services | Contract (6(1)(b)) |
| Candidate-paid evaluation reports/tests | Contract (6(1)(b)) |
| Recruiter account management | Contract (6(1)(b)) |
| Recruiter AI evaluation features | Legitimate interest (6(1)(f)) with published LIA summaries |
| Recruiter billing & payment processing | Legal obligation (6(1)(c)) |
| Platform security, QA, AI improvement | Legitimate interest (6(1)(f)) with published LIA summaries |
| Marketing & non-essential cookies | Consent (6(1)(a)) |
| Optional Data Contribution Program (DCP): creation and sharing of de‑identified / pseudonymised datasets | Consent (Art. 6(1)(a)); explicit consent where required |
4. Automated Decision-Making & Profiling (Art. 22)
AI-generated reports may be used by recruiters, but final hiring decisions rest with humans.
Candidates have rights to:
Request human intervention by contacting Flowmingo at compliance@flowmingo.ai. Flowmingo will escalate internally if recruiters fail to respond to forwarded DSARs.
Express their views or contest automated assessments (requests will be forwarded and tracked).
Opt-out of AI model improvement uses.
5. International Transfers
Personal data may be transferred outside the EEA (e.g., GCP, Cloudflare, Stripe, HitPay).
Transfers rely on Standard Contractual Clauses (SCCs) and Transfer Impact Assessments (TIAs).
Flowmingo publishes summaries of TIAs and safeguards.
Supplementary safeguards include encryption in transit and at rest, access minimisation, and regional split-processing.
6. Data Retention
Recruiter-owned candidate data: Flowmingo acts as a processor. Data is retained as long as required by the recruiter (controller) and will be deleted when instructed by the recruiter or when the recruiter account is closed and inactive for more than 2 years. Flowmingo's controller copy of candidate data (limited to security, QA, and compliance purposes) will be deleted in accordance with statutory obligations or upon validated data subject request.
Candidate-paid reports/tests: retained for 2 years by default, unless renewed or deleted at the candidate's request.
Recruiter accounts: retained for 2 years post-closure.
Billing/payment records: retained up to 7 years (legal obligation).
7. Subprocessors
Flowmingo uses trusted service providers for hosting, payment, and analytics.
Current examples: GCP, Cloudflare, Stripe, HitPay, Google Analytics.
Flowmingo ensures subprocessors are bound by contractual agreements that require GDPR compliance. Material changes will be communicated where appropriate, and clients may raise objections consistent with Art. 28.
8. Security Measures
Encryption and pseudonymisation of sensitive data.
Role-based access limited to minimum necessary (CEO, CTO, designated engineers, QA/support).
Access is logged and reviewed quarterly.
Regular penetration testing and monitoring.
Breach notifications to authorities within 72 hours where required (Art. 33).
De‑identification standard (summary). For DCP releases, we maintain a documented de‑identification standard (risk‑based), including: (i) removal/suppression of direct identifiers from transcripts where feasible; (ii) exclusion rules for sensitive content; (iii) QA sampling; and (iv) contractual restrictions for recipients (including prohibitions on re‑identification and onward resale). A short summary may be provided on request.
10. Children's Data
Flowmingo services are not directed at children under 16.
While we do not actively collect age information at signup, users are required to confirm eligibility through acceptance of the Terms of Service, which include an age restriction clause. For higher-risk services, Flowmingo may apply additional verification measures to comply with Art. 8 GDPR.
11. Updates & Versioning
This Policy may be updated.
Material changes will be notified via email or in-app.
Flowmingo will maintain an archive of prior versions for accountability (Art. 5(2)).
12. Contact
For any privacy inquiries or to exercise GDPR rights:
Email: compliance@flowmingo.ai
Address: 966 Hougang Ave 9 #12-596, Singapore 530966