♥ TrueLove TrueLove
Current release

Australian free release · Email and password sign-in. Paid subscriptions, VIP, group winks and social sign-in are not available in the free edition. Future-feature policies apply only when those features are introduced.

Document revision 2.0.2 · Effective date 2026-10-14

Third-Party Services and International Transfers Notice

1. Confirmed core provider

Supabase: the TrueLove project uses the Sydney, Australia (ap-southeast-2) region for its core PostgreSQL database and associated Auth and private Storage services. Avatar objects are protected by access policies. This region selection is not a guarantee that all service logs, support access, CDN traffic or third-party processing remains in Australia.

2. Identity providers — conditional on use

The free first release uses email and password. Apple, Google and Facebook sign-in are deferred. If introduced and actively chosen later, a provider may process an account identifier and the profile fields you authorise, and may set cookies in its own sign-in flow. Apple may supply a Hide My Email relay address and does not supply a profile photograph through Sign in with Apple. We will explain available fields and request the permissions needed for the selected feature.

3. Website and contact email

Cloudflare Workers Assets hosts the public legal website at https://shantechsolutions.com/truelove/legal/ and processes technical request information for delivery, security and aggregate traffic statistics. Contact for support, privacy, deletion and safety requests: support@shantechsolutions.com; include the relevant topic in the subject. Email routing and the receiving mailbox handle the sender address, subject and content needed to answer a request; do not send passwords, one-time codes or full payment-card details.

4. Transactional email, notifications and device services

Resend is the selected transactional email provider for account verification, password resets and necessary service messages, through Supabase Auth’s configured SMTP delivery for verification and recovery. Delivery involves the recipient email, message content such as a verification code, and delivery/security logs.

Expo Push, together with the device’s Apple Push Notification service or Google Firebase Cloud Messaging, delivers notifications on supported devices when enabled. It handles push tokens, a generic new-message notice, badge/delivery data and the conversation and recipient identifiers needed to open the right chat. The push payload does not include the private message text or sender name. Notification permission can be withdrawn in device settings.

Device location and geocoding services process the permitted foreground coordinates to return place details. Device face/fingerprint authentication is local: TrueLove receives an authentication outcome, not a biometric template. A separate analytics or crash-reporting provider is not implied solely by listing device technical information.

5. Payments and memberships — deferred

Apple In-App Purchase, Google Play Billing and RevenueCat are selected for a later paid release. New purchases and VIP entry points are disabled for the free first release. RevenueCat may still process existing subscription or test identifiers, entitlement reconciliation and deletion requests where such records already exist; this does not enable real charging or turn a sandbox test into a production entitlement. Future purchases will involve the provider shown at checkout and the necessary product, transaction, subscription-status and account-linkage information. TrueLove does not collect complete payment-card numbers in the free release.

6. Overseas processing and safeguards

Supplier infrastructure, support, security logs, content-delivery networks, email and device notification systems can process data outside Australia, including in the United States and other countries used by those providers. The Supabase Sydney database region does not limit every supplier’s processing location. We limit disclosures to their stated purposes and assess relevant contractual and technical safeguards and APP 8 requirements where applicable. You can contact support@shantechsolutions.com for information about applicable recipients and transfers.

7. Changes and contact

This notice distinguishes current core services, services used only with a relevant feature or device permission, and deferred services. We will update the dated notice when a material supplier or processing purpose changes. Privacy and access requests: support@shantechsolutions.com. Safety reports: support@shantechsolutions.com.