This notice describes the intended privacy practices for 414Unlock. Before collecting real identity documents, device identifiers or payment references from the public, the operator must finish and publish the controller, processor, retention, deletion and contact details required in relevant jurisdictions.
Information we may process
Information may include your name and email, authentication and verification records, identity or professional documents you choose to submit, device model and serial/IMEI details required for a requested service, issue notes, wallet transactions, top-up request and provider references, order status and administrator review notes.
Why information is used
We use this information to manage accounts, review account and device authorization, prevent duplicate payment claims, confirm top-ups, charge wallet credit for requested services, handle service requests, provide status updates, prevent abuse, and meet legal obligations. We should collect only information required for these purposes.
Access controls and sensitive data
Wallet balances and transactions are associated with the signed-in account. Full device identifiers are not displayed in the customer dashboard. The intended Worker implementation encrypts submitted device identifiers before storage and reveals them only to an authenticated administrator for the requested service. This protection depends on correct deployment and secret configuration; do not enable public service intake until the backend and encryption key have been configured and tested. A private admin URL alone is not an access control.
Verification documents should be stored in private object storage, not in the public website repository or public URLs, and should be available only to authorized reviewers. Uploaded documents should be deleted when no longer required, subject to a documented retention policy.
Payments and third parties
SquashberryPay payment references are used to investigate and confirm a top-up. The website should never treat a user-entered code, transaction ID, or screenshot as proof of payment without an authorized review or a confirmed server-to-server provider integration. Third-party providers may process information under their own policies.
Browser and sign-in security
Each account creation and sign-in uses a fresh, short-lived browser challenge. The server checks the one-time challenge, its proof, and whether the same network and browser session completed it without replay or unexpected changes. To monitor suspicious activity and repeated failed sign-ins, 414Unlock stores one-way keyed fingerprints derived from the connecting IP address, browser user-agent and account email, together with the edge country code, network ASN, event type and timestamp. Raw IP addresses, raw browser user-agent strings, passwords and browser challenge nonces are not stored in the security-event log. Challenge records expire shortly after use; security events are automatically pruned after 90 days when new challenges are issued. The browser check is an abuse-prevention signal, not proof of a person's identity.
Public repository and security
The website source repository must never contain identity documents, raw device data, passwords, session tokens, API keys, or private verification records. Credentials and encryption keys belong in server-side secrets. Production deployment includes origin checks, request throttling, browser challenge replay protection, security-event monitoring, backups and session revocation. Contact 414unlock@gmail.com for privacy questions or account-related requests.
Your choices and contact
Before public launch, the operator must publish a working contact method and a clear process for access, correction and deletion requests, complaints, retention periods and account closure. Avoid submitting unnecessary personal information or documents belonging to another person without appropriate permission.