Privacy Policy · Divine

Divine (“we,” “us,” or “our”) operates the Divine mobile application (the “App”). This Privacy Policy describes what information we collect about you when you use Divine, how we use it, who we share it with, the rights you have over it, and how long we keep it. It applies to your use of the App, our website at divineapp.io, our customer support communications, and any other Divine service that links to this Policy (collectively, the “Service”).

Divine is intended solely for users who are 18 years of age or older. By creating an account or accessing Divine you represent that you are at least 18. If you do not agree with this Privacy Policy, or you are under 18, you must not use the App.

This Policy is written to comply with the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA), the EU General Data Protection Regulation (GDPR), the UK GDPR, the Swiss Federal Act on Data Protection (FADP), the California Online Privacy Protection Act (CalOPPA), the Virginia Consumer Data Protection Act (VCDPA), the Colorado Privacy Act (CPA), the Connecticut Data Privacy Act (CTDPA), the Utah Consumer Privacy Act (UCPA), the Texas Data Privacy and Security Act (TDPSA), the Oregon Consumer Privacy Act (OCPA), the Montana Consumer Data Privacy Act (MCDPA), the Iowa Consumer Data Protection Act, the Indiana Consumer Data Protection Act, the Tennessee Information Protection Act (TIPA), the Delaware Personal Data Privacy Act, the New Hampshire Privacy Act, the New Jersey Data Privacy Act, the Maryland Online Data Privacy Act (MODPA), the Rhode Island Data Transparency and Privacy Protection Act, the Minnesota Consumer Data Privacy Act, the Kentucky Consumer Data Protection Act, the Nebraska Data Privacy Act, the Washington My Health My Data Act (which is supplemented by our Consumer Health Data Privacy Policy), and applicable foreign equivalents.

Please also read our related notices — Cookie Policy, Child Safety policy, and Consumer Health Data Privacy Policy — which form part of our overall privacy framework.

Notice at Collection (CCPA)

California consumers: under Cal. Civ. Code § 1798.100(b), at or before the point of collection we are required to disclose the categories of personal information we collect and the purposes for which the categories will be used. Those categories and purposes are summarized in the table below and described in detail in the rest of this Policy. We do not sell your personal information for money. We do “share” some non-precise device identifiers for cross-context behavioral advertising as defined by the CPRA (when you have consented through the App Tracking Transparency prompt). You have the right to opt out of that sharing as described in Section 7.

Identifiers — account creation, authentication, fraud prevention, customer support.
Personal information categories listed in Cal. Civ. Code § 1798.80(e) — account profile, in-app billing records.
Characteristics of protected classifications (age, gender) — to confirm you are 18+ and to operate matching and discovery.
Commercial information — subscription and coin-pack transaction records.
Internet or other electronic network activity information — product usage, crash data, performance, advertising performance signals (when you have consented).
Geolocation data (approximate, with permission) — nearby-person discovery, distance, fraud prevention.
Audio/visual information — profile photos, voice messages, posts, Stories.
Inferences — inferences drawn from the above to operate matching, discovery, and content moderation.
Sensitive personal information as defined by the CPRA — account log-in credentials, contents of communications (because we host messages on your behalf), the facial geometry derived server-side from a verification selfie, and information about racial/ethnic origin, religious or philosophical beliefs, or sexual orientation that you choose to disclose. We use sensitive PI only for the purposes described in Section 2 and you have the right to limit its use under Section 7.

1. Information we collect

1.1 Information you provide directly

When you create an account and use the App, you give us:

Identifiers — display name, email address, phone number when you choose phone sign-in, and, if you sign in with a third party, the identifier returned by Apple Sign In or Google Sign In.
Profile information — date of birth (used to compute age and gate access), gender, photos, bio, languages, interests, what you’re looking for, and any text you place on your profile.
Approximate location — captured when you grant permission so we can show you nearby people and the distance to your matches. We request reduced (approximate) accuracy only and never collect precise GPS coordinates. You can revoke location access at any time in your device settings.
Voice and audio content — voice messages you record in chat and voice messages you send in a Clan. Real-time audio in one-on-one voice/video calls and in live Spaces is routed between participants but is not recorded by us.
Photo and video content — profile photos, additional photos, post images, Story images, chat images, and Clan images.
Face verification (optional) — when you complete face verification, we send a selfie and a profile photo to our verification partner (Amazon Web Services Rekognition), which analyzes them server-side and returns a match score. We do not build or store a facial-recognition template or other biometric template on your device, and our verification partner does not retain the facial geometry it derives. We keep only the verification decision and timestamp, and the underlying selfie is deleted from active systems within thirty (30) days.
Communications — the contents of messages and posts you create, including reactions, comments, and replies. We retain message metadata such as timestamps, sender, recipient, and call duration even if the underlying message is deleted, for the operational and safety reasons set out in Section 2.
Payment and transaction data — when you purchase a subscription, a coin pack, or other in-app item, the App Store or Google Play handles payment. We receive a receipt confirming the purchase and the entitlement that should be granted — we do not see your credit card or bank details.
Reports and support correspondence — when you report another user, submit a support request, or contact us directly, we retain that correspondence to investigate the report and to comply with our legal obligations.
Survey and research responses — if you participate in a user-research interview, focus group, or beta-test program, we retain the responses you provide, anonymized where possible.

1.2 Information collected automatically

When you use Divine, certain information is collected automatically:

Usage data — which features you use, how often, screens visited, taps and other interactions, crash reports, and performance traces. We use Sentry to capture crashes and stack traces; we use PostHog for product analytics.
Device information — device type, operating system version, locale, time zone, screen resolution, generic device identifiers, IP address, and (when granted) the Apple Identifier for Advertisers (IDFA) used by AdMob.
Network information — IP address and approximate location derived from IP, used for fraud prevention and to comply with regional content rules.
Cookies and SDK identifiers — see our Cookie Policy for the full inventory. The App itself does not use browser cookies; the SDKs we integrate (AdMob, RevenueCat, Sentry, PostHog) maintain their own identifiers on-device.
App Tracking Transparency status (iOS) — whether you have granted, denied, or not yet been asked for ATT permission.
Push-notification delivery status — whether a notification was delivered, opened, or dismissed, for product-analytics purposes.
Server-side logs — standard request logs (timestamp, route, response code, latency) retained for operational, security, and audit purposes.

1.3 Information from third parties

Sign-in providers — if you sign in with Apple or Google, the provider sends us a stable identifier, your email (if you authorize sharing), and, in some cases, your name.
WhatsApp authentication delivery — when you request phone sign-in, Meta/WhatsApp processes the phone number and authentication message solely to deliver the requested one-time code.
Payment platforms — Apple and Google share entitlement and renewal status with us via RevenueCat so we know whether your subscription is active.
Verification partner — Amazon Web Services Rekognition processes verification selfies and returns a match score. We do not retain biometric templates produced by Rekognition.
Advertising partners — when you grant App Tracking Transparency permission, AdMob may share aggregated audience signals to help measure ad performance.
Account-takeover signals — Apple DeviceCheck and equivalent Android signals let us detect that the same device is being used to spawn many abusive accounts, without revealing private device information to us.

2. How we use your information

We use the information we collect to:

Create and maintain your account, authenticate you on each app launch, deliver requested phone-authentication codes through WhatsApp, and keep your session secure.
Match you with other users — find compatible profiles, route voice calls, surface relevant Spaces and Clans, and rank your feed.
Operate voice calls, messages, gifts, Stories, posts, and Spaces — including routing audio through our voice-infrastructure partner so two devices can talk in real time.
Verify that users are real humans and at least 18 years old, and detect attempts at impersonation, fraud, and account takeover.
Moderate content — scan uploaded images for harmful content before they reach other users, review reports, and enforce our Community Guidelines.
Process payments, restore purchases, manage subscriptions, and grant access to paid features.
Send transactional notifications (incoming calls, new messages, follower events, ticket grants) via Apple Push Notification service and Google Firebase Cloud Messaging.
Send service updates, security alerts, and (with your consent) promotional messages.
Improve the App — diagnose crashes via Sentry, analyze product flows via PostHog, A/B test changes, and respond to support requests.
Show in-app advertising — when you have not subscribed to an ad-free tier, we may show banner or interstitial ads through Google AdMob. With your ATT permission, those ads may be personalized.
Investigate violations of our Terms of Service and Community Guidelines, including by reviewing reports filed against you.
Establish, exercise, or defend legal claims.
Comply with applicable law and respond to lawful legal process. See our Law Enforcement Guide.

We do not use any “solely automated decision-making” that produces legal effects on you or similarly significantly affects you within the meaning of GDPR Article 22 or comparable U.S. state laws. Automated systems narrow the field for human reviewers in moderation and verification; the final decisions in significant cases (account terminations for severe abuse, child-safety reports) are made by humans.

3. Sensitive personal information

Under the CPRA and similar state laws, “sensitive personal information” (“SPI”) is a defined sub-category that gets additional protection. The SPI we may collect from you is:

Account log-in credentials (when you sign in).
The contents of your communications (text messages and voice messages) — because we host those communications on your behalf.
The facial geometry derived server-side from a verification selfie, processed once to confirm your identity (see Section 3A).
Racial or ethnic origin, religious or philosophical beliefs, or information about your sexual orientation or sex life, but only to the extent you choose to disclose them on your profile or in your User Content.

We use SPI strictly for the purposes for which you provided it (authenticating you, finding matches, operating messaging, verifying your identity, moderating content). We do not use SPI to infer characteristics about you for advertising. California residents have the right to limit our use of SPI to what is necessary to perform the services you have requested (see Section 7).

3A. Face-verification notice

This notice is provided to comply with the Illinois Biometric Information Privacy Act (740 ILCS 14, “BIPA”), the Texas Capture or Use of Biometric Identifier statute (Tex. Bus. & Com. Code § 503.001, “CUBI”), and the Washington biometric privacy statute (RCW 19.375), and applies to all users of the App without regard to residency.

What happens. During face verification you submit a selfie, which we transmit to our verification partner (Amazon Web Services Rekognition). Rekognition analyzes the facial geometry server-side and returns a match score comparing the selfie to your profile photo. We do not capture, generate, or store any biometric template, faceprint, or voiceprint on your device, and we do not operate any voice-based biometric or “voiceprint” identification.
Informed written consent. Before you submit a verification selfie we obtain your informed written consent through the in-app verification consent screen, which describes the purpose, what is sent, and how long the selfie is kept.
Specific purpose. Face verification is used solely to confirm that the account belongs to a real human and that the selfie matches the profile photo and, where applicable, that the user reasonably appears to be 18 or older.
No sale. Divine does not sell, lease, trade, or otherwise profit from verification selfies or any facial geometry derived from them.
No retained template. Our verification partner does not retain the facial geometry it derives, and we never receive a biometric template — only the match decision and a confidence score. The underlying selfie is deleted from active systems within thirty (30) days of the verification decision; we keep only the decision and timestamp after that.
Standard of care. Verification selfies are transmitted and protected from disclosure using a reasonable standard of care that is the same as or more protective than the manner in which we store, transmit, and protect other confidential and sensitive information.

4. How we share information

We do not sell your personal information in the ordinary sense of the word. We share information in the limited circumstances below.

4.1 With other users

Profile content (display name, photos, bio, posts, Stories) is visible to other users in the surfaces where you place it — the active feed, voice match, posts, Stories, Spaces, Clans, and direct chats. Precise coordinates are never shared with other users; only computed distance and, with your opt-in, city-level location. Reports you file about another user are confidential; the reported user is not told who reported them.

4.2 Service providers (sub-processors)

We rely on a small set of trusted providers, each bound by contract to use your data only to perform the service we engage them for. Our current sub-processor list:

Cloudflare, Inc. (United States) — image hosting and resizing (Cloudflare Images), audio hosting (Cloudflare R2), and content-delivery network.
Fly.io, Inc. (United States) — application hosting and edge compute.
Stream.io, Inc. (United States) — real-time audio routing for voice match and Spaces.
Amazon Web Services, Inc. (United States) — Amazon Rekognition for face verification; Amazon S3 for limited storage related to moderation queues.
RevenueCat, Inc. (United States) — server-side validation of App Store and Play Store receipts.
Functional Software, Inc. (Sentry) (United States) — crash reporting and error monitoring.
PostHog, Inc. (United States) — product analytics.
Apple Inc. (United States) — APNs push delivery, Sign in with Apple, App Store payments, DeviceCheck.
Google LLC / Alphabet Inc. (United States) — Firebase Cloud Messaging, Sign in with Google, Google Play payments, Google AdMob, Google User Messaging Platform, Google Fonts (marketing site).
Meta Platforms, Inc. / WhatsApp LLC (United States) — delivery of one-time authentication codes for optional phone sign-in.

We update this list as our vendor relationships change. The canonical version of this list is always on this page.

4.3 Advertising partners

For users who do not have an ad-free entitlement, we may show in-app advertising through Google AdMob. With your App Tracking Transparency permission, AdMob may serve personalized ads using the Apple Identifier for Advertisers (IDFA) on iOS or the Android Advertising ID. Without that permission, AdMob serves non-personalized ads using a randomly generated, non-resettable, on-device identifier limited to ad serving. We use Google’s User Messaging Platform to capture and record your personalized-advertising consent for GDPR compliance.

4.4 Legal disclosures

We will share information when required by law, valid legal process, or government request, or when we believe in good faith that disclosure is necessary to protect Divine’s rights, users’ safety, or the public. We may also share information to investigate fraud, abuse, or violations of these terms. Our procedures for handling subpoenas, court orders, and emergency disclosure requests are described in our Law Enforcement Guide.

4.5 Business transfers

If Divine is acquired, merges, or sells its assets, your information may be part of that transfer. We will notify you and any successor will be bound to honor commitments we made to you in this Policy.

4.6 With your consent

Beyond the categories above, we share your personal information only with your direct consent (e.g., if you choose to publish a post to a public surface).

5. Data retention

We retain personal information only as long as we need it to provide the Service, fulfil a legal obligation, resolve a dispute, or enforce our agreements. Specific retention periods by category:

Account profile — kept while your account exists; deleted within 30 days of account deletion (with backups overwritten on their normal rotation, typically within 90 days).
Messages and posts — kept while your account exists; deleted with the account, except for messages preserved in connection with a specific user report (see below).
Stories — leave public view 24 hours after posting; the expired Story and its view records are removed on the next housekeeping pass, but the photo remains in your private Story Archive (Settings → Preferences → Social → Story Archive) until you delete it from the Archive or delete your account. Deleting a Story from public view before it expires does not remove it from your Archive.
Voice match audio — not recorded by default. Audio is processed in real time and is not persisted to our servers.
Spaces audio — not recorded by Divine.
Voice messages (chat and Clan audio) — kept while the message exists in the conversation thread; deleted with the account.
Call metadata — participants, timestamps, and duration retained for up to 24 months for safety, fraud, and operational purposes, then anonymized.
Moderation copies — content flagged by moderation may be retained for up to 12 months in a separate, restricted-access store for review and law-enforcement purposes.
Verification selfies — deleted from active systems within 30 days of completion of the verification; we retain only the verification decision and timestamp.
Reports filed by you or about you — retained for up to 24 months from filing to support pattern review; CSAM-related reports preserved as required by 18 U.S.C. § 2258A.
Server logs & security telemetry — retained for up to 90 days, then aggregated.
Transaction records — retained for the period required by accounting and tax laws (generally 7 years).
Communications with our support team — retained for up to 36 months from the last response.
Marketing-list email addresses — retained until you unsubscribe.

6. Security

Commercially reasonable administrative, technical, and physical security measures protecting your information include:

TLS 1.2+ for all traffic between your device and our servers.
Encryption at rest for sensitive fields and uploaded media.
Role-based access control limiting employee access on a need-to-know basis.
Audit logging of administrative access.
Regular security reviews and third-party penetration testing.
A bug-bounty program for responsible disclosure of vulnerabilities.
Operational separation between production systems and analytics environments.

No method of transmission over the Internet is perfectly secure, so we cannot guarantee absolute security. We will notify affected users of any data breach in accordance with applicable law.

7. Your rights — California (CCPA / CPRA)

If you are a California resident, you have the right to:

Know what categories of personal information we have collected, the sources, the business purpose, and the categories of third parties with whom we share it.
Receive a copy of the specific pieces of personal information we have collected about you in a portable, machine-readable format.
Delete personal information we’ve collected, subject to legal exceptions.
Correct inaccurate information we hold about you.
Opt out of sale or sharing of personal information for cross-context behavioral advertising.
Limit use of sensitive personal information to purposes necessary to provide the Service.
Be free from retaliation for exercising any of these rights.

To exercise these rights, email us at support@divineapp.io with the subject line “CCPA Request.” We will verify your identity before processing. You may use an authorized agent. We will respond within the timeframes set by the CCPA (typically 45 days, extendable once for an additional 45 days on notice). If we deny your request you may appeal by replying to our response.

Opt-out of sale/sharing. To opt out of cross-context behavioral advertising, decline the App Tracking Transparency prompt on iOS, decline personalized advertising in the Google User Messaging Platform prompt where applicable, and reset or delete your Apple Identifier for Advertisers / Android Advertising ID. You can also email us with the subject line “Do Not Sell or Share.”

We have not sold or shared the personal information of consumers we actually knew were under 16 years of age in the preceding 12 months.

7A. Categories of personal information sold, shared, or disclosed in the preceding 12 months

In the preceding 12 months, Divine has not sold the personal information of any consumer for monetary consideration.
In the preceding 12 months, Divine has shared the following limited categories of personal information for cross-context behavioral advertising through Google AdMob, in each case only where users have granted App Tracking Transparency consent on iOS or have not opted out of personalized advertising on Android: identifiers (the Apple Identifier for Advertisers or Android Advertising ID), commercial information (in-app purchase signals where used for ad measurement), and inferences (audience interest signals).
In the preceding 12 months, Divine has not sold or shared the personal information of any consumer Divine actually knew to be under 16 years of age, consistent with Cal. Civ. Code § 1798.120(c).

7B. California Shine the Light disclosure (Cal. Civ. Code § 1798.83)

California residents may request, once per calendar year, information about Divine’s disclosure of personal information to third parties for those third parties’ own direct-marketing purposes during the immediately preceding calendar year. Divine does not share personal information with third parties for those third parties’ own direct-marketing purposes. To make a Shine the Light request anyway, email support@divineapp.io with the subject line “Shine the Light Request.”

8. Your rights — other U.S. states

Residents of Virginia (VCDPA), Colorado (CPA), Connecticut (CTDPA), Utah (UCPA), Texas (TDPSA), Oregon (OCPA), Montana (MCDPA), Iowa, Indiana, Tennessee (TIPA), Delaware, New Hampshire, New Jersey, Maryland (MODPA), Rhode Island, Minnesota, Kentucky, and Nebraska have privacy rights substantially similar to California’s, with some variation by state. In general you have the rights to:

Access the personal data we hold about you.
Correct inaccurate personal data.
Delete personal data we collected from you or that we received from a third party.
Obtain a portable copy of your personal data.
Opt out of targeted advertising, sale, and certain profiling.
Appeal a refusal of any of these rights.

Some states require additional disclosures. For Colorado and Connecticut residents, we honor the Global Privacy Control (GPC) signal as a valid opt-out of targeted advertising and the sale of personal data on the marketing site. For Texas residents, we are not a “small business” under TDPSA and the full-controller obligations apply. For Maryland residents, we confirm we do not sell sensitive personal data.

To exercise rights under any of these state laws, email support@divineapp.io with the subject line corresponding to your state (e.g., “Virginia Privacy Request,” “Texas Privacy Request,” etc.). If you are not sure which state law applies, use “State Privacy Request” and we will identify the right one.

9. Your rights — Washington (My Health My Data Act)

Washington residents have additional rights with respect to “consumer health data,” defined broadly under the MHMDA. See our Consumer Health Data Privacy Policy for the specific categories, your rights, and how to exercise them. Nevada and Connecticut residents have substantially similar rights with respect to consumer-health-data categories.

10. Your rights — Europe, the UK, and Switzerland (GDPR / UK GDPR / FADP)

If you are in the EEA, the UK, or Switzerland, you have the right to:

Access the personal data we hold about you.
Request correction of inaccurate or incomplete data.
Request erasure (“right to be forgotten”).
Restrict our processing of your data.
Receive your data in a portable, machine-readable format.
Object to processing based on our legitimate interests or for direct marketing.
Withdraw any consent you previously gave (without affecting processing already carried out).
Lodge a complaint with your local supervisory authority.

Our legal bases for processing are:

Contract — operating the App for you, processing payments, providing customer support.
Consent — location, camera, microphone, push notifications, App Tracking Transparency, certain marketing communications.
Legitimate interests — product safety and fraud prevention, security incident response, analytics, abuse detection, internal research, network and information security.
Legal obligation — responding to lawful requests, mandatory reporting (e.g., CSAM under 18 U.S.C. § 2258A), tax and accounting record-keeping.
Vital interests — in rare cases, sharing data to protect the life or physical safety of a person.

10A. EU and UK Representatives (GDPR Article 27 / UK GDPR)

Divine does not currently target Divine at users in the European Economic Area, the United Kingdom, or Switzerland, and is not therefore established as a controller of personal data subject to the appointment obligation under Article 27 of Regulation (EU) 2016/679 (the GDPR) or the equivalent provision of the UK GDPR. If we begin offering the App to users in those regions we will appoint and publish an Article 27 Representative on this page prior to that launch. In the meantime, EEA, UK, and Swiss users may contact us directly at support@divineapp.io with the subject line “GDPR Request,” “UK GDPR Request,” or “FADP Request.”

10B. Data Protection Officer

Divine has not designated a Data Protection Officer because our core activities do not consist of processing operations which, by virtue of their nature, scope, or purposes, require regular and systematic monitoring of data subjects on a large scale or large-scale processing of special categories of data within the meaning of GDPR Article 37(1). Data-protection inquiries should be directed to the contact in Section 18.

11. Brazil (LGPD), Quebec (Law 25), and other jurisdictions

If you are in Brazil, Quebec, South Korea, Japan, Australia, or another jurisdiction with a comprehensive privacy law, you have rights substantially similar to GDPR rights. Email us with the subject line of the applicable law and we will respond within the timeframes that law requires.

12. International data transfers

We are based in the United States. By using Divine, you understand that your information may be transferred to, stored, and processed in the United States and other countries that may have different data-protection rules than your own. Where we transfer personal data out of the EEA, the UK, or Switzerland, we rely on the Standard Contractual Clauses approved by the European Commission, the UK Addendum issued by the ICO, the Swiss-U.S. Data Privacy Framework where applicable, and equivalent safeguards. A copy of the SCCs or the Addendum is available on request.

13. Children

Divine is strictly limited to users 18 and older. We do not knowingly collect information from anyone under 18. If you believe an underage person is using the App or that we have inadvertently collected information from a minor, please contact us at support@divineapp.io with the subject line “Underage User Report.” We will suspend the account, delete the data within 30 days, and report as required by law. Full details are in our Child Safety policy.

13A. Known-minor protections for state-law purposes

Although Divine is adults-only and we do not knowingly collect data from anyone under 18, certain state privacy laws — including the New Jersey Data Privacy Act, the Oregon Consumer Privacy Act, the Delaware Personal Data Privacy Act, the Maryland Online Data Privacy Act, and the Florida Digital Bill of Rights — require additional protections for consumers between the ages of 13 and 17. Divine will not sell or share the personal information of a consumer Divine actually knows to be between 13 and 17 years of age, and will not process such data for targeted advertising or for profiling in furtherance of decisions that produce legal or similarly significant effects, in each case absent the affirmative consent required by the applicable statute.

14. Do Not Track and Global Privacy Control

Our marketing site honors Do Not Track signals where supported. For Colorado, Connecticut, and other states whose laws require it, we treat a Global Privacy Control (GPC) signal received from your browser as a valid opt-out of sale and targeted advertising on divineapp.io. The App itself does not present a browser-style DNT control; instead, you can control tracking through your device’s App Tracking Transparency prompt and the ad-personalization settings of your operating system.

15. Account deletion

You can delete your account at any time from within the App (Settings → Account → Delete Account) or by emailing support@divineapp.io from the email address associated with the account. Account deletion removes your profile, photos, voice content, posts, Stories, and messages within thirty (30) days, except for the limited retention categories described in Section 5.

16. Marketing communications

With your consent, we may send promotional emails about Divine (new features, tips, surveys). You can unsubscribe at any time by clicking the unsubscribe link in any marketing email or by emailing us. Transactional messages (incoming-call notifications, security alerts, billing receipts) are not promotional and cannot be unsubscribed from without account deletion.

17. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will update the “Effective date” at the top, and for material changes we will notify you within the App or by email and obtain fresh consent where required by law. Continuing to use Divine after a change takes effect means you accept the updated Policy.

18. Contact

Divine
Email: support@divineapp.io
Website: divineapp.io

Use the subject lines suggested throughout this Policy to route your request quickly: “CCPA Request,” “GDPR Request,” “UK GDPR Request,” “Health Data Request,” “State Privacy Request,” “Do Not Sell or Share,” “Underage User Report.”