Privacy & Safety Center
Duruha is designed to be an intentional, reputation-aware community. Review our strict data safeguards, identity protections, and community guidelines below.
Verification IDs Deleted
Government IDs uploaded for persona verification are permanently deleted immediately after approval or rejection. We store no copies.
No Background Tracking
Location coordinates are captured once at onboarding to place you in the community hierarchy. No passive or background tracking.
No Advertising Profiles
We do not sell, rent, trade, or lease personal data. Duruha is completely free from third-party advertising trackers.
Privacy Policy
Effective Date: May 19, 2026 • Last Updated: July 3, 2026
This Privacy Policy explains what information Duruha collects from you when you use the Duruha mobile application ("App"), why we collect it, how we use and protect it, and what choices you have. By creating an account, you agree to the collection and use of information described here.
1. Introduction
Duruha ("we," "our," or "us") is a trust-first social platform that connects people through verified identities, geo-filtered communities, and credibility- based content. Our mission is to enable meaningful, accountable communication by ensuring that the people behind profiles are who they say they are. This Privacy Policy explains what information we collect from you when you use the Duruha mobile application ("App"), why we collect it, how we use and protect it, and what choices you have. By creating an account or using the App, you agree to the collection and use of information described in this policy.
2. Information We Collect
We collect information you provide directly and automatically:
2.1 Information You Provide Directly
When you create an account or use the App, we may collect: - Account information: Email address, password (stored as a hashed credential, never in plain text), and display name. - Profile information: Date of birth, persona labels, bio, and profile photo. - Location information: If you choose to provide it during onboarding, we collect your device's GPS coordinates to place you within our geographic community hierarchy. This is optional. See Section 5 for details. - User-generated content: Posts (text, images, video, audio), comments, reactions, votes, agenda items, and other content you create or share on the platform. - Feed preferences and muted topics: Your algorithm configuration choices, muted geographic areas, and muted communities.
2.2 Identity Verification Information (KYC)
If you apply for a Verified Persona badge, we collect, for internal identity review only: - Government ID images: A photo of the FRONT and the BACK of a valid government ID (passport, driver's license, or national ID). - A selfie: A photo of your face, used to confirm that the person submitting the ID is its holder. - Identity details: Your full legal name, date of birth, and place of birth, matched against the submitted ID. These images are uploaded to a PRIVATE storage location. They are never displayed on your public profile and are not shared with other users. They are accessible only to a small number of authorized Duruha compliance staff during the review window. Upon approval, the raw ID and selfie images are permanently deleted; we retain only a one-way SHA-256 "identity fingerprint" derived from the images, used solely to detect duplicate or fraudulent re-submissions. See Section 4. - Persona credentials and links: Professional registry links, portfolio URLs, credential references, or travel records submitted to support a persona claim. These may be visible to other community members. We do not grant verification based on self-attestation alone. All personas require objective, verifiable, matching proof.
2.3 Automatically Collected Information
The App does not integrate third-party analytics or crash reporting services. We do not collect advertising IDs and do not build advertising profiles. The only automatically collected information is: - App activity signals: Interactions such as votes, saves, shares, and views, used solely to calculate credibility and reputation signals within the platform. - Session authentication tokens: Managed by Supabase Auth, stored securely using Android Keystore-backed storage. - Push notification token: A device push token issued by Firebase Cloud Messaging (a Google service) and stored on our servers (associated with your active persona) so we can deliver notifications. The token identifies your app installation, not you personally, and is deactivated when you sign out or when the operating system refreshes it. See Section 7.
3. How We Use Your Information
We use the information we collect to: - Create and manage your account and verified persona - Authenticate your identity and secure your session - Populate and personalize your geographic and interest-based feeds - Display community and content relevant to your location or persona - Calculate and display credibility and reputation signals - Send you push notifications about activity relevant to you - Review and process verification applications - Enforce community safety, investigate reports, and take moderation action - Detect and prevent fraud, spam, impersonation, and misuse - Respond to support requests - Comply with applicable laws and legal obligations We do NOT use your information for targeted advertising. We do NOT use your information to build advertising profiles. We do NOT sell, rent, trade, lease, or license your personal data to any third party.
4. Identity Verification Documents (Private KYC Model)
Verification on Duruha is a private "know your customer" (KYC) review. There is NO publicly displayed copy of your ID. The images you submit are never shown to other users. What you submit: - A photo of the FRONT of your government ID. - A photo of the BACK of your government ID. - A SELFIE used to confirm you are the holder of the ID. - Your full legal name, date of birth, and place of birth. How it is handled: - All three images are uploaded to a private, access-controlled storage bucket (`profile-verification-documents`). They are encrypted at rest. - Access is restricted to a small number of authorized Duruha compliance staff under strict confidentiality obligations, only during the review window. - Before upload, the app computes a one-way SHA-256 "identity fingerprint" over the combined image bytes. This fingerprint is checked against existing records so that duplicate or recycled documents are flagged as a potential fraud signal. - Upon approval, the raw ID and selfie images are permanently and securely deleted from our systems. We retain only the non-reversible identity fingerprint hash and the verification outcome — never the images themselves. - If a verification request is rejected, you may resubmit; rejected images are likewise not retained beyond the review. Because the images are never made public, you do NOT need to redact them. Submit clear, unaltered images so review can succeed. Verification does not constitute endorsement. A verified badge means only that the submitted evidence was reviewed and matched the stated persona at the time of approval. It does not guarantee the accuracy of any future statements, advice, or opinions the user may post.
5. Location Data
What we collect: If you choose to provide location during onboarding, we collect your device's GPS coordinates (latitude and longitude) using Android's location services. Why: Location is used to place you within our geographic community hierarchy (barangay, city, province, region, country) and to show you geographically relevant content, communities, and posts. Background location: We do NOT request or use background location. Location is captured only during the one-time onboarding step, with your explicit permission. Public visibility: Your raw GPS coordinates are not displayed to other users. Community-level placement (e.g., city or barangay association) may be visible through your profile or content. Control: Location permission is optional at onboarding. You may deny location access and enter your location manually [NEEDS FOUNDER CONFIRMATION: confirm manual entry option exists]. You may update or remove your location in profile settings at any time. You can also revoke location permission at any time through your Android device settings.
6. User-Generated Content
Content you post on Duruha — including text posts, images, videos, audio recordings, comments, and linked credentials — may be visible to other users of the platform depending on the community context in which it is shared. You should not post sensitive personal information (government ID numbers, financial information, home addresses, phone numbers) in publicly visible posts or comments. If you believe content violates our Community Guidelines, you can report it through the in-app reporting tool. See Section 10 (User Rights) for your deletion rights.
7. Push Notifications
Duruha uses Firebase Cloud Messaging (FCM), a service provided by Google, to deliver push notifications about activity relevant to you (such as replies, mentions, and moderation updates). How it works: - When you enable notifications, your device is issued an FCM push token. We store this token in `profile_push_tokens`, associated with your active persona, so we can route notifications to your device. - The token identifies your app installation, not your real-world identity. - The token is deactivated when you sign out (`is_active = false`) and is refreshed periodically by the operating system. - To deliver a notification, the message payload is transmitted through Google's FCM infrastructure. We minimize the personal content included in notification payloads. - Notifications and push tokens are persona-scoped: tokens, preferences, and delivered notifications are all tied to the active persona. - You can disable notifications at any time in your device settings. NOTE: No private or encrypted messaging of any kind is available in the current launch build. The Signal Protocol end-to-end messaging feature was removed (June 9, 2026), and the agenda "private comments" encrypted-thread feature that briefly reused it was removed from the UI (June 14, 2026). All comments on the platform are non-private. If encrypted messaging is re-introduced in a future release, this policy will be updated to disclose the associated data handling.
8. Sharing of Information
We do not sell your personal data. We share information only in the following limited circumstances: - Service providers: We use Supabase as our backend infrastructure provider (database, authentication, and file storage). Supabase processes data on our behalf under contractual data processing terms. See supabase.com/privacy. - Push notifications: We use Firebase Cloud Messaging (Google) to deliver push notifications. Your device push token and notification payloads are processed through Google's infrastructure for this purpose. See Section 7 and Google's privacy policy at policies.google.com/privacy. - Font delivery: The App uses Google Fonts, which may result in font requests being sent to Google's CDN. No personal data is transmitted in these requests. - Community visibility: Certain profile information, persona credentials (Copy B), posts, and content you create are visible to other authenticated users of the platform. This is core platform functionality. - Legal obligations: We may disclose information if required by law, court order, or government authority, or to protect the rights, safety, or property of Duruha, our users, or the public. - Business transfers: [NEEDS FOUNDER CONFIRMATION — if Duruha is acquired or undergoes a corporate transaction, describe how user data would be handled] - Payments: Duruha does not process payments and does not collect any payment or financial data in the current launch build. No payment processor is integrated. If payment processing is added in the future, this section and the Data Safety form will be updated first. We do not share your personal data with advertisers, data brokers, or any third party for marketing purposes.
9. Data Retention
Data Category | Retention Period ----------------------------------|-------------------------------------------- Account data (email, profile) | Until account deletion Verification ID + selfie images | Deleted immediately upon approval (and not retained after rejection) Identity fingerprint (SHA-256) | Retained for duplicate-fraud detection; removed on account deletion User posts and media | Until deleted by user or account deletion Comments | Until deleted by user or account deletion Reputation and credibility data | Until account deletion Content reports | [NEEDS FOUNDER CONFIRMATION — recommended 2 years] Exchange / transaction records | [NEEDS FOUNDER CONFIRMATION — feature not live at launch] Authentication tokens | Session-scoped, managed by Supabase Auth Push notification token (FCM) | Until sign-out, token refresh, or account deletion
| Data Category | Retention Period |
|---|---|
| Account Data (email, profile) | Until account deletion |
| Verification ID + selfie images | Deleted immediately upon approval (and not retained after rejection) |
| Identity fingerprint (SHA-256) | Retained for duplicate-fraud detection; removed on account deletion |
| Posts, Comments & Media | Until deleted by user or account deletion |
| Reputation & Credibility Data | Until account deletion |
| Content Reports | [NEEDS FOUNDER CONFIRMATION — recommended 2 years] |
| Exchange / Transaction Records | [NEEDS FOUNDER CONFIRMATION — feature not live at launch] |
| Authentication Tokens | Session-scoped, managed by Supabase Auth |
| Push Notification Token (FCM) | Until sign-out, token refresh, or account deletion |
10. User Rights and Controls
You have the following rights regarding your data: - Access: View your profile, posts, and settings within the App. - Correction: Update your profile information at any time in settings. - Deletion: Delete your account through the in-app account deletion flow. This permanently deletes your profile, roles, posts, and all associated data via cascade deletion. - Post and comment deletion: You can delete your own posts and comments directly from the App, each behind a confirmation dialog. - Verification data deletion: Your raw ID and selfie images are deleted automatically once verification is approved. You may request removal of your verification record and the loss of your Verified Persona badge by contacting us. - Location control: Location permission can be denied at onboarding or revoked at any time through Android device settings. - Feed control: Mute geographic areas and communities through feed algorithm settings. - Block users: Block another user directly from their profile or from a post. You can block a single persona, or block all personas belonging to that account. Manage and remove your blocks from profile settings. - Withdraw consent: Where processing is based on consent, you may withdraw it at any time. To exercise any of these rights, use the in-app controls or contact us at: [NEEDS FOUNDER CONFIRMATION — privacy contact email]
11. Security
We implement the following safeguards to protect your data: - TLS/HTTPS encryption for all data in transit - AES-256 encryption for data at rest on Supabase backend servers - Android Keystore for local cryptographic key storage - Zero-trust access controls for unredacted verification documents - Automatic permanent deletion of unredacted identity documents after verification approval No system is completely secure. If you believe your data has been compromised, contact us immediately at: [NEEDS FOUNDER CONFIRMATION]
12. Children and Minors
Duruha is intended for people who are at least 13 years old. We do not knowingly collect personal information from children under 13. If we become aware that a user is below 13, we will suspend the account and delete associated data promptly. Users who are 13 to 17 are treated as minors for child safety enforcement, including our child sexual abuse and exploitation prevention, reporting, and escalation standards.
13. Philippines Context and International Users
Duruha is developed and operated by [NEEDS FOUNDER CONFIRMATION — legal entity name], based in the Philippines. By using the App, you understand that your data may be processed and stored on servers operated by Supabase, which may be located in the United States or the European Union. Filipino users have rights under the Data Privacy Act of 2012 (Republic Act No. 10173) and may contact the National Privacy Commission (privacy.gov.ph) for concerns not resolved by Duruha. [NEEDS FOUNDER CONFIRMATION: Confirm whether GDPR or other regional laws apply based on intended user base.]
RA 10173 - Data Privacy Act of 2012
Duruha fully supports your rights to access, object, delete, rectify, and file concerns with the National Privacy Commission (NPC) of the Philippines. Contact lmrtamayor@gmail.com for DPA inquiry handling.
14. Contact
If you have questions about this Privacy Policy, want to exercise your rights, or need to report a privacy concern: Trust and Safety: trust@duruha.social Privacy Contact: [NEEDS FOUNDER CONFIRMATION] Legal Entity: [NEEDS FOUNDER CONFIRMATION] Address: [NEEDS FOUNDER CONFIRMATION]