Journoist Privacy Policy
Draft for review — not legally approved. Confirm this document matches actual product behavior and obtain qualified legal review before publication.
This draft explains potential processing by Journoist. Publish only after verifying the live app, API, Firebase project, database, logging, analytics and hosting configuration.
1. Who operates the Service
The current project brief identifies Journoist and Anzer Ayoob. Confirm the legal operator, contact address and any grievance officer before launch.
2. Information collected
Depending on enabled features, Journoist may process account identifiers such as Firebase UID, Google-provided name, email address and profile image; profile and role selections; Drops, comments, campaign content and petition signatures; moderation reports; and technical logs needed for security and reliability. Remove any category that is not actually collected and add omitted categories.
3. Purposes
Information may be used to authenticate accounts, display profiles and user content, administer campaigns and signatures, enforce community rules, respond to reports, prevent abuse, maintain security, support users and meet legal obligations.
4. Legal basis and choices
The lawful basis or consent mechanism depends on jurisdiction and feature. Explain consent withdrawal, permissions, optional fields and consequences of refusing required information. Do not claim consent where another legal basis applies.
5. Firebase and service providers
The app may use Firebase Authentication for sign-in and a Journoist API/database for app records. Confirm the actual Firebase project, Google services, hosting provider, logging and any analytics/crash-reporting SDKs. Link to applicable provider privacy documentation and disclose transfers where required.
6. Visibility and sharing
Public Drops, comments and campaigns may be visible to other users and may be shared by URL. Petition signatures may be visible depending on the feature design. Clearly state what is public, what is private, and whether search engines can index it.
7. Retention
Retain data only as long as needed for stated purposes, legal obligations, dispute handling and security. Define actual retention periods for account records, content, moderation logs, backups and server logs; do not publish invented timelines.
8. Security
Use reasonable administrative, technical and organisational safeguards. No online system can guarantee absolute security. Document incident response and access controls internally.
9. Rights and complaints
Depending on applicable law, users may have rights to access, correct, erase, object, restrict or port certain data, or withdraw consent. Provide a monitored contact route and explain how complaints are handled.
10. Children and international users
State age eligibility only after legal review. Apply additional safeguards where required. International availability does not mean every feature is lawful in every jurisdiction.
11. Changes and contact
Update this notice when data practices materially change and preserve version/effective-date history. Contact: contact@journoist.com. Verify this address and complaint workflow before publishing.
Contact
For questions, contact contact@journoist.com. Confirm this contact channel is active and monitored before publication.