1. Controller
The controller responsible for this website is:
Jonas SaloTegnérvägen 20E
682 60 Lesjöfors
Sweden
Email: salomannen1234@gmail.com
You can browse public builds and documentation without creating an account. Maintainer accounts are available by invitation.
2. Website delivery, security and statistics
When you access the website, catalogs or downloads, the server processes your IP address, request date and time, requested URL, HTTP status, transferred volume, and any referrer or browser/user-agent information supplied by your client. This allows us to deliver content, diagnose faults and prevent abuse. Security records may also document suspicious requests and access restrictions.
Public statistics contain anonymous aggregate counts, such as completed downloads by device and channel. They do not contain IP addresses or user-agent strings, create visitor profiles or count unique people. Temporary technical identifiers are used internally to recognise completed transfers and avoid duplicate counting.
The legal basis is our legitimate interest in reliable delivery, useful project statistics and secure operation under Article 6(1)(f) GDPR.
3. Maintainer accounts and account email
An invitation uses the email address provided by a project administrator, together with the assigned role and device permissions. When you accept it, you choose your username, display name and password. We process these details, email-verification status, account settings, permissions and relevant account activity to provide and protect publishing access.
Passwords are stored as hashes. If you enable two-factor authentication, the service stores an encrypted authenticator secret and protected recovery codes. Login sessions may record an IP address, browser information and recent activity so that you can review and revoke them. Invitations, verification, email changes and password resets use limited-validity links or tokens.
We send operational account messages, including invitations, verification and password-reset email. These are not marketing messages. Providing an email address and the required account details is necessary to use an account; without them we cannot provide access or password recovery.
Administrators can manage accounts, permissions, profiles, builds and release notes. An activity log and content revisions document relevant changes. The legal basis is our legitimate interest in providing requested maintainer access, maintaining the project and preventing unauthorised changes under Article 6(1)(f) GDPR.
4. Public profiles, builds and release notes
A visible maintainer profile can display your chosen name, username, biography, avatar, project or social links, donation link and published releases. Biography, avatar and links are optional. You can edit these details and your profile visibility in the portal. Your account email, password and two-factor authentication data are not shown on your public profile.
Publishing a release makes its build information, device tree link, release notes and maintainer credit public. This information can also appear in public catalogs, project announcements, search results or copies made by other people. Hiding a profile does not remove the maintainer credit from published releases.
Builds and release notes form a project archive. Older ZIP files may expire while their release notes remain available. An administrator can deliberately remove archive entries. Removing an account disables access and clears its profile and authentication details; published history and a minimal internal account reference remain. A display name may be retained as release credit when that option is selected. Relevant historical activity records may also remain.
The legal basis is our legitimate interest in publishing requested contributions, identifying their maintainers and preserving understandable release history under Article 6(1)(f) GDPR. Please include only information that you intend to publish.
5. Contact email and attachments
If you email the project, we process your sender name and email address, subject, message text, dates, message/thread identifiers and any attachments you send, together with our replies. Mail addressed to support@aera-recovery.com is handled through our email provider and a protected project inbox accessible to authorised project administrators. Ordinary maintainer accounts cannot access this correspondence.
We use this information to answer questions, handle feedback or reports, and retain the context of a conversation. Please send only the information needed for your request. Remove passwords, authentication tokens and unrelated personal information from logs, screenshots and attachments before sending them.
The legal basis is our legitimate interest in responding to correspondence and maintaining the project under Article 6(1)(f) GDPR.
6. Cookies and browser storage
We do not use advertising cookies, third-party analytics or tracking pixels. The application uses necessary session and request-protection cookies for functions such as sign-in, form security and account navigation. These can also be set when opening a public page. If you choose Remember me, an additional sign-in cookie can persist beyond the current session. Blocking necessary cookies can prevent account features from working.
Your optional interface accent is stored locally under aera-accent. It is not transmitted to the AERA server. Clear the site's browser data to remove it.
The device directory remembers your search, manufacturer filter and page in this browser tab under aera-directory-v1, so returning from a device page restores your selection. These filters are also sent to the server when requesting matching devices.
The interactive recovery demo stores chosen appearance settings and an optional locally resized wallpaper under aera-interactive-demo-theme-v1. Image processing happens in your browser; the wallpaper is not uploaded. Use Reset demo or clear site data to remove these preferences. Simulated files, connections and other demo actions remain in browser memory and reset on reload; the demo does not access a phone or execute real maintenance commands.
7. Services, recipients and external links
The hosting provider and authorised technical administrators process data as necessary to operate the site. OVHcloud provides email delivery and mailbox access. Recovery backups are encrypted before being stored in Microsoft OneDrive; account, profile and correspondence data can be included in those encrypted backups.
The public plugin list loads directly from raw.githubusercontent.com, so GitHub receives connection data such as your IP address, user agent and requested resource. This serves our legitimate interest in displaying current project information under Article 6(1)(f) GDPR. Following GitHub, Telegram, maintainer or donation links opens the respective external service. Telegram is not embedded and receives no request merely from displaying one of our Telegram links.
External providers may process data outside the EU or EEA. Their privacy notices explain their processing locations and applicable transfer arrangements. We do not sell personal data. You can read the providers' notices here:
8. Retention and recovery backups
Web access and error logs are rotated daily, with 14 rotated log files normally retained. Records relevant to a security incident or legal obligation may need to be kept longer. This log rotation does not set the retention period for account records, correspondence or release history.
Account data is retained while needed to provide access and administer contributions. Correspondence and attachments are kept for handling the matter and retaining necessary project context; the inbox currently has no automatic age-based deletion. Public release notes are retained as an ongoing archive unless deliberately removed. Activity records and revisions can remain where needed to explain changes, resolve disputes or investigate abuse.
We review requests to erase data against these purposes and applicable legal requirements. Recovery backups follow a rolling retention policy. Deleting information from the live service does not immediately remove it from existing encrypted backup snapshots; those copies expire through backup rotation and are retained for recovery rather than ordinary use.
9. Your data protection rights
Subject to the conditions of the GDPR, you may request access, correction, erasure, restriction of processing and data portability where applicable. You may object to processing based on legitimate interests, in particular on grounds relating to your situation. Contact salomannen1234@gmail.com to exercise these rights.
You may also complain to a supervisory authority, including the Swedish Authority for Privacy Protection, Integritetsskyddsmyndigheten (IMY).
Changes to this policy
We update this notice when the service or its data processing changes. This page contains the current version.
