Your data,
clearly explained.

1. Who is responsible for your data?

ALOPRO LLC, 30 N Gould St, Ste R, Sheridan, Wyoming 82801, United States, is responsible for processing performed to provide and administer HyperControl. For data questions or requests: hello@alopro.net.

This policy covers the app, its API and hypercontrol.app. Controlled apps, message recipients and payment providers may process data for their own purposes under their own privacy information.

2. Why do we process this information?

Where the GDPR applies, the following legal bases correspond to the service's purposes. An Android permission is a technical access control; it is not, by itself, the legal basis for every subsequent processing operation.

• Providing the requested service: creating your account, authenticating logins, interpreting instructions, performing tasks and managing credits. This processing is necessary to perform the contract.
• Optional features: enabling push notifications, wake-word detection and personal voice creation is your choice. You can disable these features and withdraw consent for processing that depends on it.
• Securing and operating the service: preventing fraud, limiting abuse of free credits, diagnosing incidents and protecting access. We pursue these legitimate interests with technical data limited to those needs.
• Managing obligations and claims: keeping records needed for payment tracking and legal requests under applicable obligations; retaining information relevant to a dispute to defend the rights concerned.
• Responding to support requests: using contact details and information you provide to handle your request, according to whether it concerns service performance, your rights or a legitimate support interest.

Information required to open an account or process a request cannot be omitted without preventing the relevant function. You choose whether to add documents, photos, resources and preferences. Do not send sensitive data unnecessarily.

3. Account, login and security

The server stores your email address, a secure password hash if you use password login, sessions, necessary account settings and usage records. Passwords are not stored in plain text.

If you choose Google, Firebase Authentication verifies login. HyperControl receives the verified email, a technical identifier and, where available, a profile-photo URL. This does not grant access to Gmail, Google Drive or contacts, or disclose your Google password to HyperControl. The photo may be cached on the phone.

Hosting logs may contain the IP address, date, requested path, status and diagnostic information. They are not intended to record passwords, request bodies or conversation contents. Administrative access is restricted to authorised support, security and service-management personnel.

4. Instructions and screen contents

To maintain task continuity, available conversation history, instructions, tool calls, results and useful observations may pass through the HyperControl server to DeepSeek. The server does not act as an archive of conversations or screen text.

The accessibility service can read interfaces and perform gestures during tasks. Fields marked as passwords by Android are masked, but other visible personal data may be included in transmitted context. An app that fails to identify sensitive fields correctly may limit filtering. You can exclude apps, stop tasks and disable accessibility in Android.

When HyperControl is the default assistant, its panel may receive context shared by the visible app: text, links or structured data. You can disable this input or deselect it before sending. Selecting a default assistant does not, by itself, enable continuous listening.

5. Resources, files and personal memory

Resources, working files, routines, conversations and detailed logs are encrypted locally and separated by account. The server does not store your library. Imported files are processed on the phone; originals are not automatically uploaded. During tasks, relevant titles, types, excerpts and active instructions may be sent to AI. A photo needed for analysis may also be transmitted.

The catalogue can link a resource to its original file. Files in that space remain until deleted. Explicit export to Downloads/HyperControl creates an independent public copy: deleting the resource in the app does not automatically delete that copy. Sharing grants the receiving app access to the selected file.

Personal memory keeps useful preferences, facts and relationships between conversations. Active memories may accompany AI requests. You can view, correct or delete memories, or disable the feature. Deleting a conversation does not automatically delete memories saved separately. Do not ask the assistant to remember passwords or secret codes.

Home suggestions use available apps, habits and local context. Limited AI generation may supplement them using a small context excerpt. Suggestions are cached and do not trigger actions on their own. Learned navigation procedures keep technical navigation references locally, without entered values; you can disable their use and delete the data.

6. Images and audio files

Depending on the task, the assistant may analyse a screenshot of an accessible window, a shared image or a resource photo. Useful images are resized before transmission through HyperControl to DeepSeek. Windows that prohibit screenshots remain protected.

An audio file shared to the workspace may be sent to Fish Audio for transcription. Format conversion may be needed. Compressed audio requiring server-side decoding is processed in a private temporary space deleted afterwards. A transcript from a file is not automatically treated as a spoken instruction from you.

When a file cannot be shared, the assistant may propose capturing the app's audio. Android requests permission for every new capture. Some sources refuse capture. The voice-session microphone is paused during this operation to avoid confusing captured audio with your instructions.

Temporary analysis and sharing copies are encrypted on the phone. Useful analyses or transcripts may remain in text history. Deleting a local copy does not remove a file already received by another app or person.

7. Voice conversations and personal voice

An active voice session uses the microphone to capture your phrases. Audio segments pass through HyperControl to Fish Audio for transcription, then the text goes to the agent. Replies to be read aloud are sent to Fish Audio for synthesis. You can mute the microphone or end the session.

Voice-conversation segments are processed in memory. A short local cache avoids generating the same spoken reply repeatedly; it is separated by session and disappears when the process stops, among other cleanup events. Transcripts may enter text history. Imported files or files prepared for sending follow working-file and temporary-media rules.

Wake-word activation with “HyperControl” is optional and disabled by default. When enabled, detection runs locally with a notification that lets you stop it. Standby audio is neither saved nor sent to online services. Once a session starts, transcription and synthesis follow the process described above.

Creating a personal voice requires confirmation and a sample of your own voice. Fish Audio receives the sample to create a private model used by your account. HyperControl's server does not retain the original file; Fish Audio retains references needed for the model. Deletion in settings sends a model-removal request to the provider. Account deletion also includes that request. Creation pricing and speech usage are shown in the app.

8. Automations and notifications

After Android permission is granted, enabled rules may process notifications from selected apps. Useful content, instructions and relevant resources pass to AI to prepare a reply or summary. Events and results are recorded in the local log. Other people concerned may include message authors, contacts or people mentioned in files you provide.

If you enable push notifications, Firebase Cloud Messaging sends technical signals about top-ups, security and updates. The server associates an installation identifier, routing identifier, language, version and preferences with your session. Signals contain no conversations, screenshots, passwords or payment amounts. The app then retrieves necessary information from the server.

Disable categories in Profile → Notifications. Signing out removes the session association. Information remains available in the app without enabling push notifications.

9. Credits, payments and abuse prevention

The credit ledger stores balances, reservations, usage, applied rates, top-up references and adjustments. Usage metrics include text volumes, audio durations, models, processing times and task states. They do not include conversation text or analysed media.

The payments.alopro.net service forwards requests to the provider available for the chosen country and method. Card data is entered with that provider, not in HyperControl's credit ledger. A phone number may be sent for compatible mobile payments. HyperControl retains references, amounts and statuses needed for tracking and complaints.

When device-based protection of the free allocation is enabled, the app uses a fingerprint of ANDROID_ID, accessible without an additional permission. The server stores a protected fingerprint, grants and the associated latest account; it does not receive the raw identifier. This prevents multiple free allocations for one device and is not used for advertising tracking. The identifier depends on factors including the Android profile and app signature; a reset can change it.

Changing accounts does not reset the allocation. Transferring remaining free credits requires confirmation. Control data may remain after account deletion to prevent another grant in the same month and investigate abuse. Ask support for details or review of a restriction; you do not need to create another account to obtain a review.

10. Providers and international transfers

Only information needed for each feature is sent to the relevant providers:

• Hostinger: hosting the HyperControl website and server.
• DeepSeek: instructions, conversation context, tool results and images needed by the AI. See its privacy policy.
• Fish Audio: audio to transcribe, text to read aloud and a voice sample if you enable a personal voice. See its privacy policy.
• Google Firebase: Google authentication and push notifications if you use those features. See the Firebase privacy information.
• Payment service and relevant providers: information needed for the chosen transaction, confirmation and refunds. The provider and its information are presented during payment.

The publisher is established in the United States. These providers may process data in other countries, including China for DeepSeek. Processing locations, retention and reuse conditions may differ from local storage. We do not describe processing as exclusively European or guarantee that every provider universally excludes training use.

To learn about countries, contractual conditions and safeguards applicable to your data, or obtain corresponding documents where access rights apply, contact hello@alopro.net. Links to provider policies do not replace ALOPRO LLC's obligations regarding these transfers.

11. How long is data kept?

• Local history and logs: adjustable retention of 7, 30 or 90 days, which can be disabled or cleared in the app.
• Memories, routines and resources: until deleted, or until the account's local data is deleted. Memories are managed separately from history.
• Learned navigation procedures: up to 30 days, with deletion available in Profile.
• Temporary media: available for 24 hours; expired items are cleaned up on the next access or launch. Files deliberately kept in the workspace follow that space's rules.
• Session voice cache: up to five minutes for reusable replies, cleared when the process closes or the relevant cleanup runs.
• Login sessions: expire after 30 days and may be revoked earlier.
• Detailed usage metrics: up to 90 days. Financial ledger entries are separate.
• Push-notification log: seven days; inactive routing associations are cleaned up separately.
• Account data: while the account exists, followed by deletion or limited retention of information needed for an obligation, payment or dispute.
• Financial and support records: for as long as needed to settle transactions, meet applicable obligations and observe relevant dispute or limitation periods. They are not an archive of conversations.
• Technical logs and anti-abuse checks: for the period needed for diagnosis, security or incident investigation; an incident may justify retaining only the relevant information.

Routine server backups use a seven-day rotation. Maintenance or incident copies may be retained separately for necessary verification and restoration. They are not used as an active personalisation database. Android backups of the app's private data are disabled. Provider retention also follows their terms and applicable service commitments.

12. Deleting data or your account

You can delete conversations, manage memory, remove resources, suspend routines, revoke sessions and withdraw Android permissions. Account deletion is available in Profile → Manage my account; if inaccessible, contact support from the associated email address.

A pending payment, purchased balance or unsettled amount may require support to arrange financial tracking and closure. Retaining necessary records does not mean all other account data must be retained.

Deletion removes the account, its sessions and relevant local data on the phone making the request. Copies may remain on other devices: remove them through the app or Android settings. Public exports and already shared copies remain independent.

The Google link is removed from HyperControl's server. A technical authentication account may remain in Firebase; contact us to request its deletion. This does not delete your Google account.

13. Exercising your rights

Depending on applicable law, you may request access, rectification, erasure, restriction or portability, or object to certain processing. You can withdraw consent without affecting processing performed before withdrawal. Dependent features may then stop working.

Write to hello@alopro.net and specify your account email and request. Proportionate verification may be required; do not send your password. We will reply within applicable legal deadlines and explain permitted restrictions or extensions.

You may contact the competent data-protection authority, including the CNIL in France. Its information on personal-data rights describes available procedures. Exercising your rights does not require deleting your account first.

14. Website and policy changes

Public pages have no account login, advertising or audience-measurement tools. Fonts and illustrations are hosted with the site. They use no tracking cookies. Visits and downloads may produce technical hosting logs.

Provider pages opened during login or payment have their own processing and privacy information. The date at the top identifies this policy's version. Significant changes to data processed or purposes will be communicated appropriately through the service.