This notice explains how Reprisio processes personal data through the public website and founding pilot. It describes the processing actually performed by the application form.
1. Data controller
Reprisio is the controller for marketing-site and pilot-application data. Reprisio is operated from Belgium. Legal identification details for commercial agreements will be completed before general contracting.
Privacy requests may be sent to privacy@reprisio.com.
2. Data we collect
- Professional contact details: name, work email, organisation and website.
- Transaction profile: role, analysis frequency and typical deal size.
- Optional information: CBE/KBO/BCE number of a target and description of the use case.
- Consent evidence: notice version, acceptance timestamp and optional marketing choice.
- Pseudonymised technical data: HMAC hashes of IP address, user agent and session. Raw IP addresses are never retained.
- Limited campaign data: referrer and bounded UTM parameters.
3. Purposes and legal bases
The qualification score prioritises human review. It does not automatically reject an applicant or create SaaS access.
- Assess the application and take steps requested by the applicant before a possible pilot agreement.
- Select and manage design partners under Reprisio’s legitimate interest in developing and securing its professional service.
- Prevent abuse, apply rate limits and protect infrastructure under a legitimate security interest.
- Send product information only where optional marketing consent has been given.
4. Recipients and processors
Access is limited to authorised people evaluating the pilot. Vercel provides application hosting and Supabase provides private storage. A transactional email provider may notify the Reprisio team when an application is recorded.
Application data is stored in a private schema separated from operational M&A data and is not accessible to anonymous or ordinary authenticated roles.
5. Retention
- Pilot profiles and submissions: 24 months after the last submission, unless a commercial relationship or legal obligation requires another period.
- Pseudonymised conversion and security events: 13 months.
- Technical rate-limit counters: only as long as required for the security window and operational cleanup.
6. Security
- HTTPS encryption in transit.
- Private storage with enabled and forced Row-Level Security.
- Write RPCs executable only by service_role, not anon or authenticated.
- HMAC pseudonymisation of network identifiers.
- Atomic limits per pseudonymised IP and email.
- Audit evidence for consent, submission and notification outcome.
7. Your rights
Subject to GDPR conditions, you may request access, correction, deletion, restriction, portability or object to certain processing. You may withdraw marketing consent at any time without affecting earlier lawful processing.
You may also lodge a complaint with the Belgian Data Protection Authority.
8. Changes
This notice may change as the pilot, processors or features evolve. The version displayed at submission is stored with the consent evidence.