Causling

Privacy Policy

Effective date: August 13, 2026 · Version 1.0.0

This Privacy Policy explains how Causling collects, uses, shares, and protects personal information when you use the Causling app and related services.

1. Scope

This policy applies to our mobile app, account systems, APIs, moderation services, and support operations.

2. Eligibility and child safety

Causling is for adults (18+). The service is not directed to children, and we do not knowingly collect personal information from children.

3. Account and profile data

We collect account identifiers such as email, auth identifiers, handle, and profile details you choose to provide.

4. Content and activity data

We collect content and metadata when you create or interact with causes, comments, votes, and other community activity.

5. Device, network, security logs, and crash reporting

We collect technical data such as app/device version, IP-derived security context, request timestamps, and operational diagnostics.

We retain crash reporting and diagnostics (including Firebase Crashlytics) so we can keep the app reliable. Crashlytics setUserID associates crash and diagnostic reports with an account identifier. That is linked diagnostics, not product analytics.

6. Product analytics (disabled at launch)

Product analytics are disabled at launch. We do not collect product-usage analytics in this version, and there is no in-app analytics toggle. If we enable product analytics later, we will update this policy before any collection begins.

7. Purchase and entitlement data

For Monthly Vote Access, stores process payment while we receive transaction/entitlement metadata needed to verify access and support account state. Vote Access is a one-time purchase for the current UTC calendar month only (not an auto-renewing subscription); unused access does not carry over to a later month. If you agree as described in How Vote Access works, we may share limited purchase-status information with Apple when Apple requests it for that purchase.

8. Media and moderation data

Uploaded images and moderation outputs (for example reason codes and correlation identifiers) are processed for safety enforcement and abuse prevention.

9. How we use data

We use information to run the service, authenticate users, enforce policies, support voting and access rules, maintain reliability, and comply with law.

10. How we share data

We do not sell personal information for money. We share data with service providers (such as AWS, app stores, auth providers, and moderation vendors) only as needed to operate the service.

11. Legal, fraud, and safety disclosures

We may disclose information to comply with legal obligations, investigate abuse/fraud, and protect users, Causling, and the public.

12. Retention

We retain data only as long as needed for service operations, legal compliance, dispute handling, fraud prevention, and audit integrity.

When you delete your account, we remove associated personal data and user-authored content as described in the app and these policies, including causes and topics you created, subject to limited legal/safety retention where required.

If a cause is removed (for example because the creator deleted their account, or for legal or operational reasons), affected voters who had used their monthly vote on that cause may have monthly vote access restored for the current UTC period so they can vote on another cause. That restores the in-app ability to cast again; it is not an App Store purchase refund or a return of money.

13. Rights and choices

Depending on jurisdiction, you may request access, correction, deletion, portability, or other privacy rights by contacting Contact@Causling.com.

14. Security

We use technical and administrative safeguards including access controls, encryption in transit where appropriate, and operational monitoring. No system is perfectly secure.

15. International processing

Data may be processed in the United States and other jurisdictions where our providers operate, subject to applicable legal safeguards.

United States CloudFront geographic restriction blocks API requests from locations outside the United States. That is request blocking, not a data-residency guarantee. Content moderation (OpenAI) and sign-in or related services (Google) may still process data outside the United States.

16. Policy updates and contact

We may update this policy and will update the effective date/version when we do.