Redhatch: Privacy Policy & Terms of Data

Last Updated: February 9, 2026

1. Introduction

redhatch ("the App," "we," "us") is a geo-spatial augmented reality interface designed to overlay a persistent game world and social utility network over the real world. We take your privacy seriously. Because our application bridges digital data with physical reality, we strictly adhere to a "Data Minimization" and "User Sovereignty" philosophy.

By using redhatch, you agree to the collection and use of information in accordance with this policy.

2. The AccessibilityService API Disclosure (Critical)

redhatch uses the Android AccessibilityService API for a single, specific safety feature: The Hardware Emergency Trigger.

• Why we use it: To allow users to broadcast an Emergency SOS ("Mayday") by holding the physical Volume Up/Down buttons for 3 seconds. This feature must work even when the app is in the background or the screen is locked to ensure safety during distress.
• What we access: We monitor KEY_EVENT streams solely to detect the specific pattern of volume button presses.
• What we DO NOT access: We do not read screen content, view notifications, intercept text inputs, or access any other accessibility capabilities. We do not change user settings.
• User Consent: You must explicitly enable this service in Android Settings. You can disable it at any time.

3. Data We Collect & How We Use It

A. Location Data (Foreground & Background)

• Data: Precise GPS (Fine Location) and Coarse Location.
• Purpose:
  - Gameplay: To render your avatar, local quests, and infrastructure on the 3D map.
  - Infrastructure Verification: To verify you are physically present at a location (e.g., verifying a Quest or Shop).
  - Safety Net (Background): If you enable "Emergency Protocols," we monitor your location in the background relative to your designated "Super Spawn" (Safe Zone). This allows the SOS feature to attach accurate coordinates to your distress signal.
• Storage: Real-time location is ephemeral. We only persist location data when you actively create a marker (Post, Quest, or Structure) or trigger an emergency.

B. Camera Data

• Data: Image data stream.
• Purpose:
  - Identity Verification: To capture a "Live Selfie" for P2P (Peer-to-Peer) verification.
  - QR Scanning: To read merchant codes and verify identity proofs.
  - Content Creation: To take photos for News, Posts, or Profile pictures.
• Storage: Images used for P2P verification are encrypted locally on your device and are not uploaded to our servers in plaintext. Public profile/post images are hosted on secure cloud storage (Cloudinary).

C. Audio & Microphone

• Data: Audio input.
• Purpose: Used solely for the "Audio Verification" feature during high-stakes Quests to prove human presence.
• Storage: Audio is processed in real-time and is not permanently recorded or stored on our servers.

D. User Content & Messages

• Data: Chat messages, comments, and posts.
• Privacy: Direct Messages (1-on-1) are end-to-end encrypted using the Signal Protocol. We (the developers) cannot read your private chats.
• Public Data: Content posted to the "Global Feed," "City Board," or "News" is public and visible to other users in your vicinity.

E. Device Information & Identifiers

• Data: Device ID, Firebase Cloud Messaging (FCM) Token.
• Purpose: To deliver push notifications for chats, zone alerts, and emergency warnings. To prevent bot farms and fraud via device integrity checks.

4. Third-Party Services

We use the following trusted third-party services:

• Google Maps Platform / Mapbox: For rendering map tiles and navigation routing.
• Supabase: For secure database hosting, authentication, and backend logic.
• Cloudinary: For hosting public user-generated images (optimized media).
• Firebase (Google): For Push Notifications (FCM) and verifying Google Play billing receipts.
• Google Play Billing: To process in-app purchases for Gems, Verification Badges, and Fees. We do not store your credit card information.

5. Peer-to-Peer (P2P) Data Handling

redhatch includes a "Dead Drop" Identity Protocol. When you verify your identity with another user:

• Your proofs (ID/Selfie) are encrypted on your device.
• The decryption key is transferred visually via QR code to the verifier.
• Our servers act only as a relay for the encrypted blob. We cannot decrypt or view your identity documents.

6. Account Deletion

You have the right to delete your account at any time.

• In-App: Go to Settings > Account > Delete Account.
• Effect: This triggers a cascading wipe. Your profile, authentication credentials, and Signal encryption keys are permanently removed. Public contributions (e.g., Quest completions) may be anonymized to preserve the game state for other players.

7. Children's Privacy

redhatch is not intended for children under the age of 13. We do not knowingly collect personal identification information from children. If we discover a user is under 13, we will immediately delete the account.

8. Contact Us

If you have questions about this privacy policy or our data practices, please contact us at:
Email: redhatch.org@gmail.com