Privacy Policy for FormAnchor
Effective date: 3 August 2026
Release candidate: 0.3.1
Controller
Ruben Lazar Nickel, trading as PERENUS
Plieninger Straße 48, 70794 Filderstadt, Deutschland
Phone: +49 1523 3545120
Email: kontakt@perenus.com
FormAnchor can temporarily save text entered in web forms locally in the browser so users may deliberately restore it after a page error or accidental closure. It starts disabled. The user must first enable the extension through onboarding and then separately approve each exact host. Subdomains are not included automatically. Factory-blocked or user-blocked hosts cannot be approved.
The content script is technically embedded for supported URLs, but field content is not read or stored before approval of the exact host.
On an approved host, FormAnchor may locally store field content, a short field hint, origin and path, field key, timestamp, global activation status, host approvals, revocation timestamps and the blocklist. Depending on user input, this may include names, contact details, personal communications, employment data, health, financial or authentication information, confidential free text and website/path information.
FormAnchor filters typical password, one-time-code and credit-card fields and certain card or IBAN patterns. These filters reduce risk but cannot guarantee that sensitive free text is never stored. Data is stored unencrypted in chrome.storage.local; anyone using the same unlocked browser profile may be able to view it through the extension. Incognito use is disabled.
FormAnchor does not transmit form, website, usage or profile data to PERENUS or any server. It uses no telemetry, analytics, advertising, profiling, data trading, cloud storage or automatic synchronisation of form content.
Restoration is never automatic. It requires field selection, opening a dialog, reviewing a preview and explicitly clicking the entry. Users must confirm that entry, website, account and field belong together.
Form content is deleted no later than seven days after storage. Expiry is checked at startup, during scheduled cleanup, on access, when the dialog opens, immediately before restoration and when counts are displayed. Hard limits remove the oldest content when necessary. Revoking a host approval deletes associated form entries.
Host approval and revocation metadata does not contain form text and is not subject to the seven-day period. It may remain so revocations can reliably take precedence and is not removed by the “delete all form entries” function. Under Chrome's documented default behaviour, chrome.storage.local is cleared when the extension is removed.
To the extent the GDPR applies, local processing is necessary to provide the function deliberately enabled by the user under Article 6(1)(b) GDPR. Users are responsible for enabling FormAnchor only where local temporary storage is lawful and appropriate.
PERENUS and third parties do not receive stored content. PERENUS therefore cannot view, identify, remotely correct, export or delete it. Requests concerning information directly provided to PERENUS may be sent to kontakt@perenus.com.
Use of information received from Chrome APIs and website content complies with the Chrome Web Store User Data Policies, including Limited Use requirements. Information is used solely for the described core function and not for advertising, profiling or data trading.
Material changes will be disclosed before taking effect and, where required, will require a new deliberate activation. This policy concerns the extension. See the PERENUS Website Privacy Policy for Cloudflare hosting.