1. Who is responsible?
FORMA is developed and operated by Moritz Lauper, Switzerland. For privacy questions and requests, contact moritz.lauper@hispeed.ch. This policy covers the extension, the optional local FORMA companion introduced in 2.1.0, and this privacy page. Shops, Chrome, GitHub and any AI provider you choose have their own privacy policies.
FORMA stores your fit information locally. When you enable an AI assessment, relevant product and fit information is sent directly to your chosen provider. FORMA has no developer-operated server that receives those assessments, and the extension includes no advertising or analytics service.
2. Information FORMA handles
- Fit profile: your profile label, height, weight, usual clothing and shoe sizes, body shape, preferred fit, style, optional chest, waist, hip, arm, inseam and foot measurements, and free-text notes. Body-related information may be sensitive. Only enter information you want used for fit assessment.
- Clothes and feedback: saved product names and URLs, sizes, measurements, product-image URLs, fit feedback, notes and relevant timestamps. Product measurements may also be saved automatically as a local comparison library.
- Product-page information: the current page URL, site, title, brand, categories, attributes, available sizes, description, measurement and model details, size charts and up to four product-image URLs. FORMA reads authorised pages to recognise clothing products. It does not read Chrome's stored history database; assessed and saved product URLs nevertheless constitute browsing-related data.
- Settings and credentials: your selected assessment mode and model, request counter and limit, on/off preference, cached assessments and, if supplied, your Anthropic API key. Temporary tab state connects each assessment to its page.
FORMA does not request your address, payment details, contacts, emails, precise location or a FORMA account. It does not log your keystrokes or clicks for analytics. Information you put in free-text notes or that appears in extracted product content may still be included in an assessment.
3. When information leaves your device
Anthropic API
When you select Anthropic, provide your own API key and grant connection access, FORMA sends an HTTPS request directly to api.anthropic.com. It includes the current product URL and extracted product information, up to three product-image URLs, your fit profile without its name/label, your notes, and relevant saved clothing references and feedback. URLs of saved clothing references are omitted. Names or other personal information written inside notes are not automatically removed. Your API key authenticates the request. Anthropic also receives normal connection information, such as your IP address.
Anthropic can retrieve the supplied product images from their hosts. Its processing, international transfers, retention and any training use are governed by your API account's terms and settings. These may involve processing outside Switzerland or the EEA, including in the United States. See Anthropic's privacy policy and API data retention information. FORMA cannot erase copies held by your provider; use its privacy controls or contact it directly. API charges are handled by your provider.
Ollama on your computer
If you choose Ollama and grant the connection, FORMA sends the same text-based assessment input to http://localhost:11434. Product photos are not sent in this mode. FORMA does not send these requests to Anthropic. Storage or onward processing by the Ollama installation or model you configure is controlled by that setup.
Codex or Claude Code through the local companion (2.1.0)
If you select Codex or Claude Code and allow the local connection, Chrome starts the installed FORMA companion using native messaging. The companion passes text-based product information, your profile without its label, notes and relevant clothing references to the official command-line application signed in on your computer. Codex processes this through OpenAI; Claude Code through Anthropic. This is cloud AI accessed through a local application, not offline AI. Product photos are not sent by this integration. FORMA does not copy CLI login credentials into the extension or extract them from the provider application.
Your provider receives assessment content and normal connection data. Its account terms, plan limits, retention, data controls and any training settings apply; these may differ from API-account terms. Processing outside Switzerland or the EEA, including in the United States, may occur. See OpenAI's privacy policy and Anthropic's privacy policy. FORMA requests non-persistent CLI sessions and deletes its temporary request/output files after each run; provider-side records and CLI operational logs are governed by the provider and your local setup.
Optional profile connection for assistant-led shopping (2.1.0)
Connect my fit profile creates and updates a local copy in ~/.forma/context.json: your fit profile without its label, notes, saved clothes, feedback and comparison library, including product URLs and timestamps. API keys are excluded. Other programs running as your operating-system user, including an assistant you ask to use FORMA, can read this file. When an assistant reads it into its conversation, its provider can receive that information, including reference URLs. The assistant's own browsing, conversations and retention are separate from FORMA's automated CLI calls.
Choose Disconnect and delete local copy in FORMA Settings to stop updates and delete this copy. You can also run forma forget to remove the current file; disconnect sync in Chrome as well to prevent a future copy. The file otherwise remains until you remove it. Uninstalling the Chrome extension does not remove companion files, exported files, assistant conversations or provider-held data. These must be deleted separately. The companion uses owner-only file permissions, no additional encryption, and no listening network server.
No AI
No AI mode compares published and seller-provided measurements locally; the extension sends no assessment request to an AI provider. The separate assistant profile connection can still be enabled; an assistant you ask to read that copy may send it to its own provider. Shop pages and displayed remote product images still load from their respective hosts in the normal course of browsing.
4. Purpose and limits
Information is used to provide clothing-fit assessments, compare sizes, remember your preferences and feedback, cache results and control request usage. Processing is initiated through your use of these features and your choice of provider and website permissions. Where applicable data protection law requires consent for optional AI processing or sensitive information, that processing is based on your consent; you can stop future processing using the controls below. Necessary service operation and responding to support requests may also rely on providing the service you request or our legitimate interest in operating and supporting it.
FORMA's use and transfer of information adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. We do not sell user data, use it for advertising, transfer it for purposes unrelated to the extension's single purpose, or use it to determine creditworthiness or for lending. Transfers to your chosen AI service are solely to deliver the requested fit assessment. The developer has no routine access to your locally stored profile or direct provider requests. If you contact support, we use the information you voluntarily send to answer your request; do not send API keys or unnecessary body information.
5. Storage, retention and security
The extension uses Chrome's local and session extension storage, not Chrome Sync. Persistent profiles, notes, references, feedback, settings and the API key remain until you change or remove them, clear the extension's data, or uninstall it. Cached AI readings are limited to the latest 40 entries; the clothing comparison library is bounded separately. Temporary page state is removed when a tab closes or the browser session ends. Profile exports are files you control and do not contain the API key; deleting the extension does not delete exported files, backups or provider-held data.
Chrome restricts extension storage access, and FORMA restricts storage access to its trusted extension contexts. It does not add application-level encryption: browser storage is not an encrypted password vault. Anthropic requests use HTTPS; the Ollama connection uses HTTP on your computer's loopback interface. Protect your device and keep your API key private.
6. Your controls and rights
- Edit your profile and notes, remove individual saved garments or feedback, and export your profile through the side panel.
- Use Forget API key in Settings to remove the stored key. Revoke a compromised key with Anthropic as well.
- Choose No AI, turn FORMA off to stop reading and cancel running requests, or revoke website access in Chrome. Requests already received by a provider cannot be recalled.
- Uninstall FORMA to remove its local extension data. Delete any exported profile files separately.
Depending on applicable law, you may have rights to access, correct, delete, restrict or object to processing, receive a portable copy, withdraw consent and complain to a competent data protection authority. Contact the address above for requests concerning data the developer holds. Most fit data is held only on your device or by your selected provider; we cannot retrieve or delete it remotely. Withdrawal does not affect processing that occurred before withdrawal.
7. This website and policy updates
This privacy page is hosted on Vercel. Delivering it involves normal technical request data such as IP address, requested URL, time and browser information; the host may process operational and security logs under its own retention practices. The page itself sets no cookies and loads no analytics scripts, external fonts or third-party images. See Vercel's privacy policy. Other pages on angebunden.ch may have different features and data handling.
We update this policy when FORMA's data handling changes and show the effective date above. Material changes requiring new permission or consent must be presented before that new processing starts.