GDPR Compliance
Complete GDPR compliance guide for whistleblowing platforms. Data subject rights, retention policies, audit trails, and privacy by design for EU data protection regulations.
Evaluating software vendors? Start with the commercial buyer page for GDPR-conscious whistleblowing software, then use this documentation for implementation detail.
How Disclosurely helps you meet General Data Protection Regulation requirements.
Regulatory context (brief)
GDPR applies to organisations established in the EU and to many organisations outside the EU that offer services to, or monitor, EU data subjects. Whistleblowing platforms process sensitive personal data—reporter identity, investigation subjects, and often special-category allegations—so controller/processor roles, retention, and access control matter as much as channel design.
Cross-border programmes commonly use GDPR’s one-stop-shop / lead supervisory authority model where main establishment sits in the EEA. Buyers comparing vendors should also use GDPR questions to ask before buying whistleblowing software.
Further Reading
- GDPR Questions To Ask Before Buying Whistleblowing Software expands the procurement checklist for legal, privacy, and compliance teams.
Overview
Disclosurely is designed to support GDPR-aware handling:
- Privacy by design: GDPR principles built-in
- Data minimization: Collect only what's needed
- Purpose limitation: Use data only for investigations
- Storage limitation: your organisation sets and applies its own retention decisions
- Integrity and confidentiality: Strong encryption controls
- Accountability: Comprehensive audit trails
GDPR Principles in Disclosurely
Lawfulness, Fairness, and Transparency
Lawful Basis:
- Legitimate interest: Conducting workplace investigations
- Legal obligation: Compliance with whistleblowing laws
- Consent: Where required (confidential reports)
- Public interest: Preventing crime and misconduct
Transparency:
- Clear privacy notices
- Explain data processing
- Inform data subjects of their rights
- Document legal basis
Fairness:
- No hidden processing
- Expected use of data
- Balanced interests
- Proportionate collection
Purpose Limitation
Data Used Only For:
- Investigating reported allegations
- Communicating with reporters
- Compliance with legal obligations
- Statistical analysis (anonymized)
- Improving investigation processes
Not Used For:
- Marketing
- Unrelated purposes
- Profiling
- Automated decision-making (except AI assistance with human oversight)
Data Minimization
Collect Only:
- Information necessary for investigation
- Reporter identity (confidential reports only)
- Relevant evidence
- Communication history
- Investigation notes
Do Not Collect:
- Unnecessary personal details
- Special category data (unless relevant)
- Disproportionate information
- Irrelevant background
Anonymous Reports:
- No reporter account required for anonymous submissions
- Maximum data minimization
- Tracking ID only identifier
- Reporter identity depends on what is included in report content and follow-up
Accuracy
Ensuring Accuracy:
- Reporters control their information
- Can update via secure messaging
- Investigators verify facts
- Corrections logged in audit trail
- Outdated data flagged
Update Mechanisms:
- Reporter can correct information
- Subject can dispute allegations
- Evidence must be verified
- Interview transcripts verified
Storage Limitation
- Disclosurely does not enforce retention schedules, delete reports automatically or provide legal holds
- Org Admins can archive, unarchive and soft delete reports
- Your organisation decides how long to keep reports, using the law that applies to you
- Deleting your organisation's data is a manual request to Disclosurely support
Integrity and Confidentiality
Encryption:
- Encrypted storage controls
- Encrypted transport for data in transit
- Server-side encryption controls
- Encryption in transit and at rest
- Encrypted backups
Access Controls:
- Role-based permissions
- Least privilege principle
- Account access controls
- Session management
- Access logged in audit trail
Security Measures:
- security posture information available on request
- SOC 2 reporting is not currently available
- Security review processes
- Operational monitoring
- Vulnerability management practices
Accountability
Demonstrate Compliance:
- Data processing records
- Privacy impact assessments
- Data protection policies
- Audit trails
- Compliance reports
- Training records
Data Subject Rights
Right of Access (Article 15)
What Data Subjects Can Request:
- Copy of their personal data
- How data is being processed
- Who has accessed their data
- Retention period
- Rights to rectify or erase
Disclosurely Features:
Reporters do not have Disclosurely accounts. Requests from reporters, subjects or other individuals are handled by your organisation as controller, outside Disclosurely's self-service tools. Settings › Data lets a signed-in team member delete their own account; it does not process requests from reporters or subjects. Self-service personal data export is unavailable; to request a copy of their personal data, a team member emails privacy@disclosurely.com. Requests are handled within the timeframe required by data protection law, subject to lawful extensions and exceptions.
For Anonymous Reporters:
- The reporting form does not ask for a name or email address, so the organisation may be unable to link a request to a report
- Reports may still contain personal data in the text or attachments; review these carefully
For Subjects of Investigation:
- Submit data access request
- Verify identity
- Receive data held about them
- Subject to exemptions (investigation in progress)
Timeline: 1 month to respond
Exemptions:
- Ongoing investigation may delay response
- Cannot disclose reporter identity
- Cannot compromise investigation
- Document exemption reasoning
Right to Rectification (Article 16)
What Can Be Corrected:
- Factual errors in report
- Personal details
- Evidence annotations
- Contact information
How to Request:
Reporters:
- Send a message through secure messaging using their tracking ID and access secret
- Specify what needs correction
- A case handler reviews the request and records the outcome in the case
Subjects:
- Submit rectification request
- Provide correct information
- Investigator reviews
- Update if appropriate
- Note in case file if disputed
Not Applicable To:
- Opinions (subject can dispute)
- Allegations themselves
- Investigation findings
- Subjective assessments
Right to Erasure / "Right to be Forgotten" (Article 17)
When Erasure Required:
- Data no longer necessary
- Consent withdrawn (if consent was basis)
- Objection and no overriding legitimate interest
- Processed unlawfully
- Legal obligation to erase
When Erasure NOT Required:
- Compliance with legal obligation (investigations)
- Public interest (serious misconduct)
- Legal claims (potential litigation)
- During retention period
Disclosurely Process:
-
Request Received
- Via email or in-app
- Identity verified
- Logged in system
-
Evaluation
- Legal team reviews
- Assess legal basis for processing
- Check exemptions
- Consider retention obligations
-
Decision
- Erase if required
- Explain if exemption applies
- Partial erasure if appropriate
- Document reasoning
-
Implementation
- Secure deletion if approved
- Anonymization alternative
- Update audit trail
- Notify data subject
Timeline: 1 month to respond
Right to Restriction of Processing (Article 18)
When Applicable:
- Accuracy disputed (restrict while verifying)
- Processing unlawful but subject prefers restriction to erasure
- No longer need data but subject needs it for legal claims
- Objection lodged (restrict while assessing)
Effect:
- Data stored but not processed
- Only with subject's consent or for legal claims
- Must inform before lifting restriction
In Disclosurely:
- There is no dedicated "restricted processing" flag. Record the restriction in your own procedures and the case messages, and avoid further processing of the case until it is lifted
Right to Data Portability (Article 20)
Scope:
- Data provided by subject
- Automated processing
- Based on consent or contract
- Technically feasible
In Disclosurely:
- Reporters cannot export data themselves; they have no account
- Your organisation prepares any export manually, for example from the case PDF export
- Provide the data the individual supplied (for example their report and messages), while protecting other people's information
Right to Object (Article 21)
Grounds for Objection:
- Processing based on legitimate interests
- Direct marketing (not applicable)
- Scientific/historical research
- Particular situation of data subject
Disclosurely Response:
-
Receive Objection
- Via email or in-app
- Document grounds
-
Assess
- Compelling legitimate grounds?
- Legal claims potential?
- Public interest?
- Overriding interests?
-
Decision
- Stop processing if no compelling grounds
- Continue if legal obligation or legitimate grounds
- Explain decision
- Inform of right to complain to supervisory authority
Rights Related to Automated Decision-Making (Article 22)
Disclosurely's Approach:
- No solely automated decisions
- AI assists but humans decide
- Meaningful human oversight
- Can request human review
- Can express point of view
- Can contest decision
AI Case Helper:
- Provides recommendations only
- Investigator makes final decision
- Can override AI suggestions
- Subject can challenge findings
- Human review always available
Data Processing Records
Article 30 Records
Required Documentation:
Controller Information:
- Organization name and contact
- Data Protection Officer contact
- Processing purposes
- Data subject categories
- Personal data categories
- Recipient categories
- International transfers
- Retention periods
- Security measures
Disclosurely does not generate Article 30 records for you. Keep your own record of processing activities; the DPA and security information, available on request, can help with the processor sections.
Data Protection Impact Assessment (DPIA)
When Required:
- High risk processing
- Systematic monitoring
- Large scale special category data
- New technologies
Disclosurely Use Cases Requiring DPIA:
- Implementing Disclosurely initially
- Processing sensitive allegations
- Using AI Case Helper
- Custom integrations
Disclosurely Provides:
- DPIA template
- Risk assessment guide
- Mitigation recommendations
- Regular review prompts
DPIA Process:
- Describe processing operations
- Assess necessity and proportionality
- Identify risks to data subjects
- Evaluate measures to address risks
- Document and review
Data Processing Agreements (DPAs)
Disclosurely as Processor:
- You (customer) are the controller
- Disclosurely is the processor
- DPA required by Article 28
DPA Includes:
- Subject matter and duration
- Nature and purpose of processing
- Type of personal data
- Categories of data subjects
- Controller and processor obligations
- Security measures
- Sub-processor arrangements
- Data subject rights assistance
- Audit rights
- Deletion obligations
Access DPA:
- Our DPA is available on request. Email security@disclosurely.com.
International Data Transfers
Data Location
Disclosurely Hosting:
- Core case data is stored in the single EU Supabase production project.
- Customers cannot select a hosting region; US hosting is not currently offered.
- Application delivery uses Vercel. Confirm authentication, email, logging, backup and other supporting-service processing locations during security review.
- Do not interpret the core database location as a guarantee that all service processing occurs in the EU.
Sub-Processors:
- Vetted and approved
- Data processing agreements
- Adequate safeguards
- Listed in documentation
Transfer Mechanisms
If Transfer Needed:
EU to Third Countries:
- Adequacy decision (UK, Switzerland)
- Standard Contractual Clauses (SCCs)
- Binding Corporate Rules
- Subject consent (rare)
UK Post-Brexit:
- UK considered adequate by EU
- EU considered adequate by UK
- Seamless transfers
Disclosurely Provides:
- SCCs if needed
- Transfer impact assessment
- Alternative safeguards
- Documentation
Data Breaches
Breach Notification Obligations
Timeline:
- Discover breach
- Assess severity
- Notify supervisory authority within 72 hours (if high risk)
- Notify data subjects without undue delay (if high risk to rights)
Disclosurely Process:
-
Detection
- Security and error monitoring
- User reports
- Regular audits
-
Containment
- Immediate action to stop breach
- Preserve evidence
- Prevent further damage
-
Assessment
- What data affected?
- How many data subjects?
- Risk to rights and freedoms?
- Notification required?
-
Notification
- Supervisory authority (if required)
- Affected data subjects (if high risk)
- Customer organizations
- Documentation
-
Remediation
- Fix vulnerability
- Implement additional controls
- Monitor for recurrence
- Document lessons learned
Customer Responsibilities:
- Assess impact on your processing
- Notify your supervisory authority if controller
- Notify affected data subjects if required
- Cooperate with Disclosurely on investigation
Breach Prevention
Disclosurely Security:
- Encryption at rest and in transit
- Access controls and account security controls
- Security monitoring
- Security review processes
- Vulnerability management
- Incident response plan
- Staff training
- security posture information available on request
GDPR Tools in Disclosurely
Retention and Deletion
These are separate things:
- Personal account deletion. A team member can delete their own account from Settings › Data. Their login, profile and personal information are removed and their name is removed from case records; reports, messages, attachments and case audit records stay with the organisation. It is not available while the organisation has an active subscription or trial. See Data Subject Requests.
- Organisation data retention. This is your organisation's responsibility. Org Admins can archive, unarchive and soft delete reports. Soft delete removes a report from the dashboard but marks the record as deleted rather than erasing it. Disclosurely does not enforce retention schedules or delete reports automatically. See Data Retention Policies.
- Organisation termination. What happens to your organisation's data when your account ends is governed by the Terms.
- Manual support processes. Requests to delete your organisation's data, or for a copy of a team member's personal data, are handled manually: contact support@disclosurely.com or privacy@disclosurely.com.
Access Records
The audit log records when a team member opens or exports a report (repeat views within a few minutes are recorded once), along with other key case actions. This helps you show who accessed a report when responding to a request or reviewing a data breach.
Data Subject Requests
Disclosurely does not currently include a data subject request portal. Handle requests through your own process. Your organisation remains responsible for verifying identity, assessing exemptions and responding within the legal timeframe. Team members can delete their own account from Settings › Data; self-service personal data export is unavailable, so copies of personal data are requested from privacy@disclosurely.com.
Privacy Notices
Your organisation should publish a privacy notice that covers whistleblowing reports. Disclosurely does not currently provide privacy notice templates or a privacy notice editor. A notice typically covers:
- Controller identity
- Processing purposes
- Legal basis
- Recipients
- Retention
- Data subject rights
- Right to complain
Consent
Whistleblowing processing usually relies on legal obligation or legitimate interests rather than consent. Disclosurely does not currently provide consent management tools. Take advice on the right legal basis for your organisation.
Best Practices
Designate a DPO
When Required:
- Public authority processing
- Large scale systematic monitoring
- Large scale special category data
DPO Responsibilities:
- Monitor GDPR compliance
- Advise on DPIAs
- Cooperate with supervisory authority
- Contact point for data subjects
In Disclosurely:
- Assign DPO role to user
- DPO dashboard access
- Compliance reports
- Alert notifications
Regular Compliance Reviews
Quarterly:
- Review data processing records
- Check retention and deletion
- Assess data subject requests
- Review privacy notices
- Staff training check
Annually:
- Update DPIAs
- Review DPAs
- Audit security measures
- Assess new processing activities
- Train staff on GDPR
Document Everything
Maintain Records:
- Legal basis for processing
- DPIA outcomes
- Data subject requests and responses
- Breach assessments
- Records of deletion decisions
- Staff training
- Policy updates
Demonstrates Accountability: Can show supervisory authority
Training
Who Needs Training:
- All Disclosurely users
- Investigators especially
- HR team
- Compliance team
- Senior management
Topics:
- GDPR principles
- Data subject rights
- Breach notification
- Secure handling of data
- Retention and deletion
- Using Disclosurely compliantly
Disclosurely Resources:
- Training videos
- Documentation
- Best practice guides
- Compliance checklists
Supervisory Authorities
UK Information Commissioner's Office (ICO)
Contact:
- Website: ico.org.uk
- Telephone: 0303 123 1113
- Report concerns online
Responsibilities:
- Enforce GDPR in UK
- Investigate complaints
- Issue guidance
- Impose fines
EU Data Protection Authorities
Each EU Country:
- National supervisory authority
- Lead authority for cross-border processing
- Cooperation mechanisms
Find Your Authority:
- European Data Protection Board website
- Lists all EU/EEA authorities
- Contact details
Filing a Complaint
Data Subjects Can:
- Complain to supervisory authority
- Disclosurely must cooperate
- May result in investigation
- Can appeal decisions
How to Avoid:
- Respond promptly to requests
- Respect data subject rights
- Be transparent
- Document compliance
- Seek legal advice when uncertain
Related:
