Privacy Policy — JWith

Last updated: 2026-07-17

Effective from: 2026-05-28

About this document

This Privacy Policy explains what personal data JWith collects from you, how we use it, who we share it with, how long we keep it, and what your rights are. It is written to be readable and to reflect what actually happens in our infrastructure — without unnecessary legalese.

It applies to your use of the JWith mobile app (iOS and Android), the website jwith.app, and all related services, regardless of where you are located.

1. Who is responsible for your data

• Controller: Ox Digital LLC
• Address: 1209 Mountain Road Pl NE, Ste N, Albuquerque, NM 87110, USA
• Phone: +1 505-451-2303
• Privacy / Data Protection Officer email: privacy@jwith.app

2. What personal data we collect

2.1 Account creation

• Email address
• Password (stored as a cryptographic hash — we never see the plaintext password)
• A unique device identifier (generated locally on first use and tied to your account for single-device session control)
• Phone number — collected when you verify your phone (a prerequisite for the "verified" badge, and an anti-fraud measure). We store the number and the country it belongs to; the one-time SMS code is sent and checked through Twilio (see section 4.2)
• Device-integrity attestation results — timestamps recording when your device last passed Google Play Integrity (Android) / Apple App Attest (iOS) checks, used to block automated abuse and scraping (see section 4.2). No device fingerprint is stored — only the attestation outcome, tied to your account

2.2 Public profile

Voluntarily provided by you during onboarding or profile editing:

• Nickname (you pick from auto-generated options or submit your own — subject to moderation)
• Gender identity ("man"/"woman") and preference ("interested in women"/"interested in men")
• Age range (derived from your exact age — only the range, never your exact age, is shown publicly)
• Marital status ("single", "divorced", "widowed")
• Children: whether you have any, whether you want any
• Approximate location (derived from your city — only "City, Region, Country" is publicly exposed)
• Description / bio (subject to a length limit shown in the app and to automated moderation)
• Verification status ("verified" badge if you complete the process described in section 2.5)
• Languages spoken
• Interests
• Optional details you choose to display: height, body type, drinking frequency, education, occupation

2.3 Private profile (sensitive and detailed data)

Visible only to people you explicitly authorized via the "private profile share" flow:

• Exact age
• Location at neighborhood granularity — the place you selected (city, locality, or neighborhood) and its marker on the map. Derived from your manual selection, never from GPS or device positioning
• Height, body type, drinks, education, occupation (even if you didn't make them public)
• Religious data (treated as sensitive personal data under most data-protection laws): if you choose to reveal, your pioneer status (auxiliary or regular) and congregational role (ministerial servant, elder). These fields are opt-in — only processed after your explicit consent during onboarding, removable at any time.

2.4 Photos

• Private photo: your real photo, uploaded during onboarding. Used as the reference for generating your public photo and as proof of existence (automated validation described in section 9). Stored in a private bucket, encrypted at rest, accessible only via short-lived signed URLs.

• Public photo (AI): an image automatically generated from your private photo by an image diffusion model (Flux), with features altered to preserve your privacy. This is the image other users see in the feed. You control the level of modification in the photo editor.

• Shared private photo: if you accept a private-photo-share request from another user, that user can see your original (unmodified) photo during the chat. Blocking the user suspends that access for as long as the block lasts (unblocking restores it); deleting your account removes it permanently.

2.5 Identity verification (biometric)

To earn the "verified" badge, you record a short video (15–30 seconds) answering a randomly generated question shown on screen. The video:

• Is uploaded to a private bucket (accessible only via service-role)
• Is reviewed manually by our team to confirm correspondence with your private photo
• Is automatically deleted as soon as the review finishes — approved or rejected — by an automated database trigger (no human action required)
• The review result (approved/rejected + standardized reason) is retained for audit and anti-fraud purposes, but the video itself does not persist

This is the only biometric data collected by JWith. Verification is optional — you can use the app without the badge.

Face data

What we collect. Your private photo (section 2.4) and your verification video (above) contain your face as ordinary images — that is the only face data JWith collects. We do not perform facial recognition, and we do not extract, generate, or store face geometry, facial landmarks, faceprints, or any other biometric template — from the photo, the video, or anything else.

How we use it and who receives it. Face data is used only to operate the features you invoke, never for advertising, profiling, or training our own models:

• Public photo generation: your private photo is sent to fal.ai (United States), which runs the image diffusion model that produces your privacy-preserving public photo.
• Photo validation: your private photo is sent to Sightengine (France, EU), whose automated checks confirm it shows one real adult and is not AI-generated.
• Identity verification: your verification video is reviewed manually by our own team to confirm it matches your private photo; it is not sent to any third party.
• Private photo sharing: your original photo is shown to another user only if you accept that user's share request (section 2.4).

fal.ai and Sightengine process the image transiently, on our instruction, under Data Processing Agreements, and may not use it for any other purpose. Any third party that receives face data is contractually bound to provide the same or equal protection of that data as described in this policy.

How long we keep it. The verification video is deleted automatically as soon as its review finishes (approved or rejected). The private photo is kept for as long as your account exists, stored in a private bucket, encrypted at rest, accessible only via short-lived signed URLs (section 2.4). No other face data exists to retain (no templates — see above). Full retention table: section 6.

How to delete it and revoke consent. You can replace your private photo at any time in the app (the previous one is deleted). Verification is optional — you can simply not record a video, and an unreviewed attempt can be cancelled in the app. Because the private photo is required to operate a profile, fully revoking consent to face-data processing means deleting your account: Settings → Delete account removes your photo, any pending verification video, and every derived record (permanent erasure within 30 days — section 6). You can also write to privacy@jwith.app (section 8).

2.6 Communications

• Invitations (you send or receive a chat request — we record sender, recipient, date, status)
• Chat messages (text — visible only to you and the person on the other side of the thread)
• Private profile / private photo shares (the request + status)
• Reports you file against another user, or reports received about your profile (reporter, target, reason, details)

2.7 Usage data

• Profile view history in the feed (used to order who you haven't seen yet on your next session)
• Last activity (timestamp of last login)
• Quotas: how many times you've recently used AI photo generation / sent invitations, to enforce the daily limits
• Credits earned via rewarded ads (AdMob — we store the Google-issued transaction ID to prevent replay fraud). To serve these ads, Google's Mobile Ads SDK transmits a device advertising identifier to Google for ad delivery and ad-fraud prevention. Ads are non-personalized — the identifier is not used for cross-context behavioral advertising (see section 8)

2.8 Technical diagnostics (Sentry)

When the app encounters an unexpected error, we send a technical report to an observability service (Sentry):

• Error message + stack trace
• App version, device model, operating system
• "Breadcrumbs" — a sequence of your last actions in the app (e.g. "opened Meet", "tapped Verify"). We do not include message content, descriptions, photos, or other data you entered
• An internal identifier for your account (UUID — not your email or nickname)

IP addresses are not sent.

2.9 Push notifications

To notify you of important events (new invitation, photo verified, etc.), we store your device's push token (provided by Apple Push Notification Service or Google Firebase Cloud Messaging, via Expo Push Service).

3. Why we collect each piece of data (legal bases)

The table below maps each data category to its purpose and the legal basis under which we process it. The terms used map to the equivalent bases under GDPR, LGPD, CCPA, and other data-protection laws.

You can withdraw any consent at any time without affecting the lawfulness of processing based on consent before its withdrawal. Where we rely on legitimate interest, you can object — see section 8.

4. Who we share your data with

4.1 Other JWith users

As described in section 2, certain data is visible to other app users:

• Visible to any authenticated user (once your profile enters the feed): your public profile + your public AI photo
• Visible only after your explicit authorization: your private profile + your original private photo
• Messages: visible only to you and the person on the other side of the thread

4.2 Sub-processors (operators)

We engage the following companies to process data on our behalf. Each has access to only what is needed to perform its function:

We maintain Data Processing Agreements with each sub-processor, binding them to standards equivalent to or stricter than GDPR/LGPD.

4.3 Authorities

We may share data when legally required by a court order or valid request from a public authority. Whenever possible, we will notify you in advance — except when prohibited by law.

4.4 Business succession

If JWith is sold, merged, or has assets transferred, your data may be transferred to the successor entity. You would be notified in advance to exercise your rights (including deleting your account before the transfer).

5. International transfers

Several sub-processors store data outside your country of residence. We rely on the following safeguards for cross-border transfers:

• For transfers from the EU/EEA/UK: Standard Contractual Clauses (SCCs) approved by the European Commission, plus supplementary measures (encryption at rest, short-lived signed URLs).
• For transfers from Brazil: standard processing clauses aligned with LGPD requirements, and ANPD adequacy determinations where applicable.
• For transfers from other jurisdictions: equivalent contractual safeguards in our Data Processing Agreements.

The current list of safeguards per sub-processor is available upon request at privacy@jwith.app.

6. How long we keep your data (retention)

7. How we protect your data (security)

• All connections use HTTPS encryption
• Data at rest is encrypted (database, photo storage)
• Passwords are stored as cryptographic hashes — never plaintext
• Photo access requires short-lived signed URLs
• User-scoped database access — each user can read only their own data, with controlled exceptions for public profiles and shared chat threads
• Automated content moderation rejects inappropriate photos and descriptions before they become visible
• Block and report tools are available to any user at any time

Despite all protections, no system is 100% secure. If you suspect your account has been compromised, change your password immediately and notify us at privacy@jwith.app.

8. Your rights

You have the following rights regardless of where you are located. The specific legal basis differs by jurisdiction (GDPR Art. 15–22, LGPD Art. 18, CCPA/CPRA, and equivalents elsewhere), but the substance is equivalent.

• Confirm and access the data we hold about you, and receive a copy
• Correct inaccurate or incomplete data
• Delete / erase your data
• Restrict how we use your data (in limited circumstances)
• Port your data to another service in a structured, machine-readable format
• Object to processing based on legitimate interest
• Withdraw consent for any data processed on the basis of consent
• Be informed about who we share your data with
• Opt out of any sale or sharing of personal information for cross-context behavioral advertising — we do neither
• Limit the use of sensitive personal information
• Not be discriminated against for exercising any of these rights
• Lodge a complaint with your local data-protection authority — see section 13

How to exercise

• Access and correction: directly in the app (Profile tab)
• Export: Settings → Export my data (provided within the period required by applicable law)
• Delete account: Settings → Delete account (immediate soft-delete, permanent erasure within 30 days)
• Withdraw consent: edit or remove the relevant data in the app, or write to privacy@jwith.app
• Other requests: privacy@jwith.app — we respond within the timeframe required by applicable law (e.g. one month under GDPR, 15 days under LGPD)

9. Automated decisions and AI

JWith uses AI to automate certain decisions:

• Description moderation: Anthropic's AI (Claude Haiku) reads your bio and decides whether it contains external contacts, ads, or inappropriate content. If rejected, we show the standardized reason.
• Nickname moderation: a custom nickname you type is screened the same way (profanity, reserved words, impersonation). Auto-generated nicknames come from a pre-approved pool.
• Private photo validation: Sightengine's AI evaluates whether your photo contains a real adult person, a single subject, and is not AI-generated. If rejected, we show the standardized reason.
• Public photo generation: the Flux model generates your public photo from the private one — you control the modification level.
• Feed ordering: an algorithm determines the order in which you see other profiles, based on geographic proximity, recent activity, and how many times you've already seen each profile. There is no "quality ranking" — only contextual relevance.

You have the right to request human review of any automated decision. To do so, email privacy@jwith.app with a description of the decision and your reasoning. We respond within the timeframe required by applicable law.

10. Minimum age (children and adolescents)

JWith's baseline minimum age is 18 years. Where the age of legal majority or the legal age to use online dating services in your jurisdiction is higher, that higher age applies. We do not allow use by anyone below the applicable legal age.

The complete description of how we prevent minors from accessing the service, how we detect suspected child-safety issues, and how to report concerns is in our Child Safety Standards.

If you are under 18 and created a JWith account, ask a parent or legal guardian to email privacy@jwith.app so the account can be deleted immediately.

11. Cookies and mobile identifiers

The mobile app does not use cookies. We use:

• Local secure storage for your session and device ID
• Local image cache for performance — clearable from your device settings
• Push tokens (provided by the OS) for notifications

The website jwith.app sets no cookies. When you pick a language or a light/dark theme, the choice is stored in your browser's localStorage — user-requested preferences, never used for tracking. We do not use third-party tracking cookies.

12. How we will notify you of changes

This policy may be updated. When there is a material change — a new sub-processor, a new category of data collected, a change of legal basis — we will notify you via in-app notification and via email (if you provided one), in advance before the change takes effect.

The current version is always available at jwith.app/legal/privacy and in Settings → Privacy Policy in the app.

13. Contact

For any question, request, or concern about your personal data — including the rights described in section 8 — write to privacy@jwith.app. This is the primary channel for all data-protection matters, regardless of where you are located.

• Privacy / Data Protection Officer: privacy@jwith.app
• General support: support@jwith.app
• Postal address: Ox Digital LLC — 1209 Mountain Road Pl NE, Ste N, Albuquerque, NM 87110, USA
• Website: jwith.app

We respond within the timeframe required by applicable law.

If you believe your rights have been violated, you may file a complaint with your local data-protection authority — your national DPA in the EU/EEA, the ICO (UK), the ANPD (Brazil), the California Attorney General, or the equivalent agency in your jurisdiction.