Privacy Policy

Effective Date: August 1, 2026 | Application: Happy Harmony

Privacy Policy

Effective Date: 2026-06-27
Last Updated: 2026-11-11

1. Overview

This Privacy Policy describes how Sunset Architecture Collective ("we", "us"), the developer and operator of Happy Harmony ("Platform"), collects, use, share, and protect information when you use our services, including payments, subscriptions, payouts, and fraud prevention.

2. Information We Collect

Account data: name, email, phone, user ID, role (buyer/seller/contractor)

Billing data: subscription tier, purchase history, add-on selections (full card numbers are not stored by us)

Payout data: Stripe Connect account ID, onboarding status, bank verification status (held by Stripe)

Transaction data: order amounts, fee breakdowns, escrow status, payout logs

Fraud/risk data: transaction velocity, dispute counts, device fingerprint hooks, IP address, app instance identifiers

Usage data: analytics, crash logs, feature usage (Firebase)

3. Stripe Data Sharing

We share necessary data with Stripe, Inc. to:

Process payments and destination charges

Onboard sellers via Stripe Connect Express

Verify identity (KYC) and bank accounts

Route seller payouts and platform fees

Handle disputes and chargebacks

Stripe's privacy policy: https://stripe.com/privacy

We do not store full payment card numbers. Stripe tokenizes payment methods.

4. How We Use Information

Operate checkout, subscriptions, escrow, and payouts

Calculate and disclose fees (platform, processing, reserve)

Enforce rolling payout delays and payout freezes

Detect fraud, volume spikes, and suspicious activity

Unlock subscription entitlements and add-on features

Comply with law and respond to disputes

We do not sell personal information.

5. Device Fingerprinting and Fraud Detection

We may collect device and session signals (device model, OS version, app version, anonymized device fingerprint hooks) to:

Prevent account takeover and payment fraud

Detect volume spikes and suspicious seller activity

Support seller freeze and payout hold decisions

You may limit some signals through device settings; certain features may not function without them.

6. Data Retention

We retain data as long as needed for transactions, tax/legal compliance, dispute resolution, and fraud prevention. Payout and chargeback logs may be retained for seven (7) years or as required by law.

7. Security

We use HTTPS for app API traffic, access controls and Stripe payment processing. Real-time media transport depends on the configured provider and is not represented here as universally TLS-only. No method is 100% secure.

8. Your Rights

Depending on jurisdiction you may request access, correction, deletion, portability, or restriction. Contact support@deletedatainhouse.com. California (CCPA/CPRA) and EU (GDPR) rights apply where relevant.

9. International Transfers

Data may be processed in the United States where our servers and Stripe operate.

10. Children

The Platform is not intended for users under 18.

11. Changes

We will update this Policy when practices change. Review periodically.

12. Contact

support@deletedatainhouse.com

Payments and Payouts Reference

Happy Harmony operates under the following payments and payout terms:

15% platform service fee on qualifying marketplace transactions

Stripe Connect Express onboarding, KYC, bank verification, and destination charges

7–14 day rolling payout delay for new sellers (no instant payouts until eligibility)

chargeback reserve (1%) and seller-primary liability routing

Developer, contact and deletion requests

Happy Harmony is the app name. Its developer, operator and the organization responsible for this service is Sunset Architecture Collective. Android package: com.happyharmony.

Contact us at support@deletedatainhouse.com. To request account deletion, email us from the address linked to your account with subject "Happy Harmony Account Deletion Request". For data-only deletion, specify the data you want removed. We verify ownership before acting.

We complete verified account and data deletion requests within 30 days by deleting or de-identifying active app account data we control and submitting applicable provider deletion requests. Records required for tax, accounting, fraud prevention, disputes or other legal obligations may be retained for those limited purposes. Retained records are limited to those purposes and are not used to market to a deleted account.

Service providers can retain restricted backup or security records under their own retention policies after an active account is deleted. For example, Firebase documents that Authentication and Cloud Messaging deletion can take up to 180 days across live and backup systems, and Crashlytics keeps crash records and associated identifiers for 90 days before starting removal. The 30-day request-completion commitment does not promise physical erasure of every provider backup within 30 days. See Firebase privacy and retention information.

App data, SDKs and service providers

Depending on the features you choose, data sent off your device can include account and contact information; user identifiers; addresses; tax identifiers and payout records for recipients of payouts; order and purchase history; messages; uploaded photos, videos and documents; live camera, microphone and screen-share content; searches and saved searches; profiles, listings, reports and other user content; activity/audit records; crash logs, diagnostics and device identifiers.

Location: Location-aware features can transmit precise GPS latitude/longitude and approximate location when the relevant permission is granted. You can deny location permission in Android settings. These releases do not declare background location permission. Firebase Analytics can also derive approximate location from network information.

Google Firebase: Authentication for sign-in, Cloud Firestore for database/content records, Cloud Messaging for push notifications and installation tokens, Analytics for usage measurement and approximate location, and Crashlytics for crashes and diagnostics. Firebase Cloud Storage is not asserted merely because Firestore stores content.

Stripe: payments, connected-account onboarding/verification and payouts where applicable. Observed checkout flows open Stripe-hosted checkout. A local masked-card label is not proof that the app stores a full card number. Stripe processes payment details entered into its payment form. Order/payment identifiers, transaction amounts and payout or tax totals can be held in our service records.

Google Play: in-app billing and subscription purchase/verification where offered. Google handles payment information entered in Google Play's payment interface.

LiveKit-compatible media infrastructure: when in-app rooms or calls are enabled, the configured real-time media service carries the camera, microphone or screen-share tracks you choose to publish. A server-issued room URL selects the media endpoint. Users start sharing through the app and Android's consent prompt, and can stop sharing or leave the room.

Google/YouTube: Google sign-in and, when you choose to connect your own channel, YouTube Live broadcasts and video playback. RootEncoder is an encoder library used by the app for live publishing, not a separate claimed data-storage processor. Google Meet may be opened as an external meeting fallback.

Map services: OpenStreetMap-compatible map/tile services receive requests when relevant map features are used; requests can reveal IP address and the map area requested.

Hosting: Render hosts the app API endpoints identified in the code. Netlify hosts this legal website. These services can process connection and request information needed to provide the service.

Advertising ID: the audited vc100 releases include Google Analytics for Firebase with Advertising ID collection enabled by default when the identifier is available. It is used for analytics. Android advertising settings may limit availability. This statement does not claim that the app displays third-party ads.

Security: the app's configured API URLs use HTTPS. Firebase and Stripe document TLS protection for their SDK/API traffic. The release app network-security policy disallows cleartext HTTP. Real-time media transport is selected by the configured provider; we do not claim every media path is TLS-only until those paths are verified. No transmission or storage method is completely secure.

We do not treat on-device image effects or local preference storage alone as proof that your photos or other data are uploaded. The app does not read your email inbox, SMS inbox or device contacts merely because you provide an email address or phone number.