Skip to main content

Protocolos de Seguridad

WAKEBEAR APP™ — SECURITY AND DATA DELETION (v1.0)

Last updated: July 07, 2026. Effective from: July 07, 2026. Controller: Luis Angel CG (Iniciativa Peruana) Contact: support@wakebear.app

1. Our Commitment to Your Privacy

At WakeBear we do not sell or commercialize your personal data or your geolocation routes. Your GPS location is processed locally on your device's hardware to trigger the alarm. We do not build behavioral profiles, do not store travel or route history on external servers, and do not share your email or direct account with third parties. Independently, we use advertising services strictly as a separate monetization mechanism or for unlocking usage limits, sharing only the technical information or identifiers necessary for this purpose, in accordance with the Privacy Policy.

2. Data Governance and Storage

A. Cloud Servers (Firebase Firestore — Google Cloud us-central1)

We store solely and exclusively the technical data necessary to validate the integrity of your account and protect the business model:

  • Your unique user identifier (anonymous UID generated by Firebase Authentication).
  • Registration email obtained via Google Sign-In.
  • Active subscription plan (GUEST Trial, PREMIUM or PRO PLUS).
  • Atomic counter of available trips (free_trips_remaining and total_trips_used).
  • The encrypted hardware hash in the trials_used collection to mitigate fraud and abuse of the trial period.

B. Local Device Memory (SharedPreferences)

Interface personalization data and usage persistence live only in your phone's physical storage:

  • The history of Recent Trips and Favorite Geofences (processed locally for your convenience).
  • Cache of current plan, preferred alarm mode (AlarmMode) and search session token.
  • The cryptographic coordinates of the trip origin point, protected by AES-256 algorithms and anchored to the device's hardware (Android KeyStore / iOS Secure Enclave) to prevent spoofing in automatic PNR refund requests. Note: All these data are automatically and permanently deleted upon uninstalling the application from the phone.

C. Volatile Memory (Device RAM)

Telemetry data and mathematical estimation from the Inertial Tunnel Engine (v3.6) — such as entry speed above ground and calculated seconds underground — are processed exclusively in the phone's volatile RAM memory. They are not persisted on the phone's disk nor transmitted to any database. Upon canceling the journey or turning off the alarm, this information is instantly destroyed.

  • Google Maps Shared Links: Shortened URLs received from Android's native tray are resolved externally because it is necessary to provide the link decompression service. This resolution occurs temporarily in the phone's RAM. The app does not consume local disk storage nor does it generate read or write operations in the cloud Firestore database, ensuring highly efficient network data consumption and minimizing data retention outside the device.

D. Pre-launch Database (Waitlist)

Waitlist data or web pre-launch phase data, particularly email addresses voluntarily provided through the WakeBear web form, are securely stored in the Firebase infrastructure used by the initiative, under strictly restricted access controls and reasonable technical and organizational security measures. Such data are not commercialized, rented, assigned, or shared with data brokers or third parties foreign to WakeBear's logistical operation, and may only be consulted by authorized personnel exclusively for pre-launch management purposes, according to the applicable Privacy Policy.

3. Technical Security Architecture

To protect system integrity, WakeBear implements the following software engineering safeguards:

  • Encryption in Transit: All communication between the mobile application and Google Firebase servers uses standard cryptographic protocols (HTTPS/TLS).
  • Perimeter Isolation: Firestore security rules are designed to ensure that each user (authenticated UID) can only access and modify their own records.
  • Transaction Protection: Validation of credits and subscriptions is performed server-side, preventing local manipulation of balances.
  • Mandatory Network Validation: The system requires active connectivity at launch to synchronize account state, which prevents starting journeys if the device is disconnected (e.g., in Airplane Mode).
  • Cryptographic Integrity Verification: The application incorporates mechanisms to validate its official signature (SHA-256). If an unauthorized modified or altered version is detected, the system may halt execution to protect user data.

4. Official Data Deletion Mechanisms

In strict compliance with Google Play Store policies and Law N° 29733 of the Republic of Peru, you may revoke your consents and request the total destruction of your records through two official channels:

Option A: From the Application (Recommended — Instantaneous)

Go to the Profile → Danger Zone → Delete Account tab. The software will execute an atomic deletion command in Firebase Auth and Firestore. The deletion of your credentials and the purging of data on Google Cloud servers is carried out immediately, irreversibly, and automatically.

Option B: From the Web (Email Request)

You may send an email from the address associated with your account to support@wakebear.app with the mandatory subject "ACCOUNT DELETION".

  • Pursuant to Article 18 of Law N° 29733, our support team will process the deregistration, identity validation, and physical deletion from servers within a maximum period of fifteen (15) business days.

What data is permanently destroyed when deleting the account?

  • Your complete user profile (name, email, and Google photo).
  • Your immutable UID and your transactional history of trip quotas in Firestore.
  • Your access tokens in Firebase Authentication are revoked, preventing any future login with that account. Important note: The cancellation of recurring monthly subscriptions associated with the PREMIUM or PRO PLUS plans must be managed directly by the user within the Google Play Store dashboard (Subscriptions Section) to prevent Google from making automatic charges to your bank cards in subsequent billing cycles.