Journoist Account and Data Deletion Policy
Draft for review — not legally approved. Confirm this document matches actual product behavior and obtain qualified legal review before publication.
This draft describes the intended deletion request route. The actual implementation must be verified across Firebase, the Journoist API/database, backups and service providers before publication.
1. How to request deletion
Provide an in-app account deletion flow and/or a clearly accessible web request page. The final page must state the exact steps and the monitored contact route. Current contact draft: contact@journoist.com.
2. Identity and security
Journoist may take proportionate steps to verify a request belongs to the account holder. Do not ask users to send passwords or authentication codes by email.
3. Systems to cover
Deletion should address Firebase Authentication identity, profile records, role selections, user-generated content, campaign ownership, petition/signature records, uploaded evidence and related metadata where legally and technically appropriate. Build and test an explicit dependency map; deleting only the login account may leave personal data behind.
4. Exceptions and retention
Some records may need to be retained for legal compliance, security, fraud prevention, dispute resolution or integrity of public records where permitted by law. Explain categories, legal reasons and retention periods specifically; do not use a blanket exception.
5. Backups and logs
Document how deleted data ages out of backups and operational logs. If immediate erasure is not technically possible, state the real timeframe and restrict further use where appropriate.
6. Public content and petitions
Explain whether public Drops or campaigns are deleted, anonymised, retained as public-interest records, or transferred to another owner. Explain how petition integrity and signer privacy are balanced. Do not silently retain identifiable content after promising full deletion.
7. Confirmation and timing
Confirm receipt and completion through a secure channel and provide the actual expected timeframe required by applicable law and platform rules. Do not publish a specific number of days until engineering and legal teams verify it.
8. Google Play compliance
Ensure the in-app flow and any required web deletion resource match current Google Play requirements and the Data safety disclosures. Test the full deletion lifecycle before production.
Contact
For questions, contact contact@journoist.com. Confirm this contact channel is active and monitored before publication.