Privacy Policy

Operator: HiiiPower (“we”, “us”, “our”)
Contact / privacy requests: support@hiiipower.app
Public URL: https://hiiipower.app/privacy
Related: Terms of Service

This Privacy Policy explains what personal data we collect when you use the HiiiPower mobile app and related services (the “Service”), why we use it, how long we keep it, and the choices you have.

1. Who we are

HiiiPower operates a social application with optional privacy-preserving (encrypted) posts and identity checks intended to reduce fake accounts. For privacy questions or data requests, email support@hiiipower.app.

2. Data we collect

2.1 Account and profile

• Email address (via Privy authentication)
• Username, display name, bio, and other profile fields you provide
• Profile photos / banners you upload
• Account status (active, deactivated, pending deletion) and related timestamps

2.2 Authentication and wallet identifiers

• Privy user identifiers and linked email account metadata
• Embedded wallet address(es) created for your account (and, if applicable, smart-wallet addresses used for sponsored transactions)
• Authentication tokens / session credentials needed to keep you signed in

Sign-in is through Privy email one-time-passcode (OTP) only. We do not offer password-based login.

2.3 Face data (TrueDepth camera / ARKit liveness check)

This section describes all face data HiiiPower collects, how it is used, shared, stored, retained, and deleted.

2.3.1 What we collect. During registration, on iPhones with a TrueDepth (Face ID) camera, HiiiPower runs a one-time face liveness and uniqueness check using Apple's TrueDepth camera and ARKit face tracking.

• Processed on your device only, never transmitted or stored: camera frames, face position and orientation, and facial expression values (such as eye blink, smile, and head turn) that ARKit provides through the TrueDepth camera. The app uses these only to confirm that a single, live person is present and completing a randomized on-screen challenge. They are discarded as soon as the check ends. We never upload or store photos, video, depth maps, or face-mesh geometry.
• Sent to our servers: a numeric face template (also called an embedding) that an on-device model computes from the captured frames. The template is encrypted on your device before it is sent. With it we receive the liveness score, a session identifier, and a one-way hash of your device identifier.
• Created on our servers: the check outcome (accept, review, or reject), a similarity score, a reference to the most similar existing account (if any), a one-way hash of the template, and the time of the check.

A face template is a string of numbers, not an image, and cannot be viewed as a photo.

2.3.2 How we use face data. We use face data only to:

1. confirm that a real, live person is creating the account; and
2. prevent duplicate and fraudulent accounts by comparing your template against the templates of existing HiiiPower accounts, so that each person can hold only one account.

We do not use face data for advertising, marketing, profiling, analytics, use-based data mining, or training machine-learning models. We do not use it to identify you to other users, and we do not use it to unlock the app or sign you in. We never sell face data.

2.3.3 Sharing. We do not share, sell, rent, or disclose face data to any third party. Face data is not sent to Privy, advertising networks, analytics providers, or any other third-party service. It is handled only by HiiiPower's own systems, which run on the infrastructure providers listed in §2.3.4. Those providers host our systems on our behalf and may not use the data for their own purposes. Within HiiiPower, access is limited to authorized personnel who review flagged checks, and they see outcomes and scores only (no images exist). We will disclose face data only if the law requires it.

2.3.4 Where face data is stored.

• Database: HiiiPower's own database on MongoDB Atlas, hosted on Amazon Web Services in the Mumbai, India region (ap-south-1). The template is stored only in encrypted form.
• Application servers: our API servers on Render, hosted in the United States (Oregon). They decrypt the template in memory only to run the uniqueness comparison, and do not write it to disk or to logs.
• Operational logs: our server logs record the outcome and similarity score of each check, never the template. These logs roll off automatically within 30 days.

2.3.5 Security. Templates are protected in transit by TLS and by encryption on your device (RSA-OAEP with AES-256-GCM). At rest they are encrypted with AES-256-GCM using keys held on our application servers, separately from the database. The database provider also encrypts storage at rest.

2.3.6 Retention. We keep your face template and related liveness records only while your account exists, because they are needed to keep preventing duplicate accounts. If a check is rejected as a duplicate, your template is not stored. We keep only the attempt record (outcome, score, and the matched-account reference), and it is deleted along with your account. Temporary check sessions expire automatically within minutes. We do not currently keep separate database backups that contain face data. If we add backups, encrypted backup copies will be overwritten within 30 days of deletion.

2.3.7 Deletion. When you delete your account (Settings → Deactivate / Delete Account), your face template, template hash, liveness scores, and all liveness session and attempt records are permanently erased when the 30-day deletion grace period ends. Any reference to your account in other users' liveness records is also removed. You can ask us to delete your face data at any time by emailing support@hiiipower.app. Deleting your face data this way also removes your verified status, and you may need to verify again to keep using features that require it.

2.3.8 Consent. The face check runs only after you choose to start it and grant camera permission. You can revoke camera permission at any time in iOS Settings.

2.4 User-generated content

• Posts, captions, comments, likes, and direct messages (plaintext and/or encrypted, depending on feature; comments are currently plaintext)
• Media you upload (stored on our servers and/or decentralized storage such as IPFS)
• Location labels you attach to posts (for example city / place), when you choose to share them

2.5 Location

If you grant permission, we may access approximate or precise location to help you select a city/country or discover nearby content. You can deny or revoke location permission in system settings.

2.6 Device, push, and diagnostics

• Device identifiers used for push notifications (e.g. Expo push tokens) and platform (iOS/Android)
• App version / basic device information needed for compatibility
• IP address and request metadata processed by our servers (security, rate limiting, abuse prevention)
• If we later enable a crash-reporting service, limited crash and diagnostic logs may be collected to improve reliability; we will update this Policy if that becomes material

2.7 Social graph and safety

• Outer Circle and Inner Circle relationships and access requests
• Blocks and reports you submit or that involve you (reason codes and optional details)
• Notifications related to social activity

2.8 Progression / referrals

• XP, levels, quests, streaks, medals / rewards metadata, and referral codes or slots tied to your account

2.9 Optional platform connections

If you connect third-party platforms for data-portability features (separate from sign-in), we may store connection status and data assets you choose to archive. Depending on the provider and how the connection works:

• OAuth-based connections (for example Spotify or Google today) — encrypted access / refresh tokens, scopes, and derived or synced assets
• Archive / guided export connections (for example Meta family platforms today) — uploaded archive files or summaries you provide, plus connection status (not OAuth tokens)
• Additional providers we may add later — using similar OAuth and/or archive patterns, which we will describe in this Policy when material

3. How we use data

We use personal data to:

• Create and secure your account and sessions
• Provide core social features (profiles, posts, comments, messaging, notifications)
• Operate encrypted / access-controlled posts (including key wrapping and access checks)
• Run the face liveness / uniqueness check to prevent fraud and duplicate accounts (face data is used only as described in §2.3)
• Enforce safety (reports, blocks, bans) and respond to abuse
• Send transactional email (for example account lifecycle notices when an email is on file)
• Improve reliability, debug issues, and prevent spam / attacks
• Comply with law and App Store / platform requirements

We do not sell your personal data. We do not use your content for third-party advertising profiles.

4. Legal bases (where applicable)

Depending on your jurisdiction, we process data based on: contract (to provide the Service), consent (e.g. camera / location / the face liveness check), legitimate interests (security, abuse prevention, product improvement), and legal obligation.

5. Sharing and processors

Face data is never shared with third parties. See §2.3.3.

We share other data with service providers who process it on our instructions, which may include:

• Privy: email OTP authentication and embedded wallets (receives no face data)
• Cloud hosting / database (Render for application servers; MongoDB Atlas on AWS for the database): API, realtime, and data storage
• Object storage (Cloudflare R2): uploaded media such as profile photos and post images (receives no face data)
• Email delivery: transactional messages
• Maps / geocoding providers (Apple Maps via the device, LocationIQ): location features
• IPFS pinning / gateways (e.g. Infura, Pinata, or another provider we configure): media and metadata storage for posts
• Push infrastructure (e.g. Expo / APNs): notifications

Encrypted / access-controlled posts use server-side key wrapping and access checks operated by us (not a separate third-party key network).

We may disclose information if required by law, to protect rights and safety, or in connection with a merger / acquisition (with notice where required).

Public or decentralized publications (IPFS CIDs, on-chain commitments) may be visible to anyone with the relevant identifier and are outside ordinary “private database” controls.

6. International transfers

Our database is hosted in India (AWS Mumbai region) and our application servers in the United States, so your data, including encrypted face templates, may be processed in countries other than your own. Where required, we use appropriate safeguards for cross-border transfers.

7. Retention

• Active accounts: data retained while your account is open and as needed to operate the Service
• Deactivation: profile and posts may be hidden while account data is retained
• Deletion request: after you request deletion in-app, we schedule permanent erasure (currently a 30-day grace period during which you may cancel by signing back in). After purge we delete account records, social graph rows, messages involving you, safety rows involving you, face templates and all liveness session/attempt records, local profile media files we host, and related progression data, as described in our account lifecycle process
• Face data: retained and deleted as described in §2.3.6 and §2.3.7. Deactivation or the deletion grace period hides your account but keeps your template until the purge completes. The template is then permanently erased
• Backups: may persist for a limited period (no more than 30 days) before rolling off
• Legal holds / abuse records: may be retained longer when necessary (this never includes face templates beyond the periods in §2.3)
• IPFS / blockchain: we may be unable to erase copies that already exist on public networks (face data is never published to IPFS or a blockchain)

8. Your choices and rights

Depending on your location, you may have rights to access, correct, delete, export, or restrict processing of your personal data, and to withdraw consent where processing is consent-based.

In-app controls:

• Settings → Deactivate / Delete Account: start deletion (including face data)
• Settings → Blocked users: manage blocks
• Report controls on posts, profiles, comments, and chats
• System settings: revoke camera, photos, location, and notification permissions

You can also email support@hiiipower.app, including to request deletion of your face data only. We aim to respond within a reasonable period (and within 2–3 business days for safety reports where feasible).

9. Children

The Service is not directed to children under 13 (or higher age required locally). We do not knowingly collect personal data from children under that age. If you believe a child has registered, contact us and we will take appropriate steps.

10. Security

We use industry-standard measures including transport encryption (HTTPS/TLS), access-controlled APIs, and encryption for certain post content and for face templates (see §2.3.5). No method of transmission or storage is 100% secure.

11. App Store privacy labels

We disclose data collection categories in Apple App Store Connect (and equivalent store listings) consistent with this Policy, including identifiers, contact info, user content, location (if enabled), diagnostics, and sensitive info related to the face liveness check.

12. Changes

We may update this Policy from time to time. We will update the effective date and, for material changes, provide additional notice where appropriate.

13. Contact

support@hiiipower.app
Website: https://hiiipower.app