Privacy notice
We collect less by design.
Your financial plan stays on your device during normal Personal use. This notice explains the separate information Styrvia handles for website and app delivery, Try measurement, optional analytics, email, product research, support, payments and records from previous Personal downloads.
Privacy Notice version 1.30 · 5 September 2026
Household model stays localEarlier licence records are separateAnalytics is optionalTry measurement is aggregate
At a glance
The important privacy boundary in four points.
1. Controller and contact
Styrvia · CVR 46690397 · Monica Zetterlundsvej 19, 4. tv., 2450 Copenhagen SV, Denmark is the controller for the website, optional analytics, records from previous Personal downloads, emails, support and payment records described here. Styrvia does not automatically collect the Personal household model. When the browser app is online, ordinary technical requests are made to deliver and protect the app; those requests do not need household plan values. Contact: [email protected].
2. What Styrvia processes and why
| Data | Purpose | Legal basis |
|---|---|---|
| Records from Personal copies previously issued through the website: email address, Terms version, Styrvia release version and acceptance time | Administer those issued copies, record which Terms were accepted and protect Styrvia against unauthorised redistribution or commercial use. | Performance of the licence agreement / steps requested by you to obtain the licensed copy (GDPR Art. 6(1)(b)); where necessary to establish, exercise or defend legal claims, Styrvia may also rely on legitimate interests (Art. 6(1)(f)) |
| Update checks from standalone Personal copies: app edition/version and, where enabled, a fixed aggregate activity event | Let standalone copies check for official release information and contribute to a minimal aggregate estimate of active copies. Manual Check now retrieves release information only and does not send the activity event. | Legitimate interests in maintaining and securing distributed Styrvia copies and in minimal aggregate product-usage statistics (GDPR Art. 6(1)(f)). Styrvia has documented a legitimate-interest assessment for the limited activity aggregate. |
| Technical website and app-delivery information processed by the hosting/security service, such as IP address and browser/network request information | Deliver and protect the website, forms and browser app; investigate abuse or security incidents; and count successful Personal downloads in aggregate where applicable. | Legitimate interests in operating and securing Styrvia (GDPR Art. 6(1)(f)) |
| Optional Google Analytics website-use data after you allow analytics, including page path, referrer, device/browser information and campaign parameters | Understand which pages and campaigns lead to meaningful website use and Personal access. Styrvia does not send financial-plan data, email addresses or form contents to Google Analytics. | Your consent (GDPR Art. 6(1)(a)). Google Analytics is not loaded before consent. |
| Plus interest feedback: selected feature categories; optional free-text “Other” comment if you choose to write one | Measure demand for possible Plus features. Categories are stored as aggregate counts. Optional “Other” comments are stored separately and are not linked by Styrvia to your email or selections. | Legitimate interests in product research and prioritisation (GDPR Art. 6(1)(f)). Cloudflare may separately process technical/security data needed to protect the form. |
| Email address and mailing-list subscription/consent information, only if you opt in | Send only the product-interest or project updates you explicitly opt into, including separate Plus or Professional notifications. | Your consent (GDPR Art. 6(1)(a)) |
| Professional interest/enquiry records: business contact details, role/organisation information and the intended Professional use or workflow information you choose to provide | Respond to enquiries and understand likely professional use. Registering interest does not create a licence or payment record. | Legitimate interests in responding to professional enquiries and measuring B2B product demand (GDPR Art. 6(1)(f)); any marketing email requires a separate opt-in where applicable |
| Voluntary contribution/payment information received from the payment provider you choose (for example Revolut or PayPal), such as payer name/contact identifier, transaction ID, amount, currency, date and payment reference | Receive and reconcile voluntary support, maintain accounting records, process an error/refund request, handle disputes and prevent fraud | Legitimate interests in administering voluntary support and protecting Styrvia (GDPR Art. 6(1)(f)); compliance with accounting, tax and other legal obligations where applicable (Art. 6(1)(c)) |
| Contact/support correspondence, business enquiries and the contact details you choose to provide | Respond to your question, troubleshoot a non-sensitive technical issue and protect Styrvia from abuse | Legitimate interests in responding to requests and operating/supporting Styrvia (GDPR Art. 6(1)(f)); where applicable, steps requested by you relating to use of Styrvia (Art. 6(1)(b)) |
| Support files deliberately shared by the user | Diagnose a specific problem when the first support details are not enough. Styrvia may ask you for a support snapshot only when necessary. Review it before sending; it may still contain financial and scenario information. Nothing is uploaded automatically. | Performance/administration of requested support (GDPR Art. 6(1)(b)) and, where appropriate, legitimate interests in diagnosing defects and improving reliability (Art. 6(1)(f)). |
| Aggregate Walkthrough usage counts: date, website version, step reached, approved source/campaign group and count. Styrvia does not store a visitor or session ID for these counts. | Measure whether the guided Walkthrough experience is understood and whether visitors move from viewing it to starting, seeing the result and opening Personal. These aggregate records do not contain email, IP address, user agent, household or plan values, financial inputs, raw referrer, arbitrary URL parameters or free-text feedback. | Legitimate interests in minimal aggregate product and acquisition measurement (GDPR Art. 6(1)(f)). This first-party aggregate measurement is separate from optional Google Analytics. |
| Personal Early Access requests app files, update information and reviewed reference data. Cloudflare may process standard technical request information. The household plan remains on the device during normal use. | Deliver and update Styrvia in the browser and make reviewed reference data available. Normal app and update requests do not need income, spending, asset, debt, pension, scenario or result values. | Performance/administration of the Personal service requested by the user (GDPR Art. 6(1)(b)) and legitimate interests in secure website/application delivery (Art. 6(1)(f)). |
Browser app and standalone update checks
Personal Early Access requests the app files and update information needed to load and run. These requests do not require your financial plan, balances, scenarios or results. Any standalone copy that uses the existing update-check option may check for release information at most about once every 15 days and, when enabled, contribute a separate aggregate activity count at most about once every 30 days. Manual Check now does not send that activity count.
Styrvia does not keep per-installation usage rows for this metric and does not retain raw IP addresses specifically for product-usage measurement. Cloudflare may separately process standard technical request information to deliver and secure the service under the production hosting configuration.
3. Financial information Styrvia does not collect during normal use
During normal use, Styrvia does not receive your household model, balances, salaries, assets, debts, pensions or scenario inputs. On a private device, local autosave/recovery stays in that browser profile when enabled; Shared device mode clears and prevents Styrvia plan autosave/recovery persistence. If the first support details are not enough, Styrvia may ask for a support snapshot. Review it before sending; it may contain personal and financial information.
In Personal Early Access, Styrvia serves the app while the financial model is calculated and stored on your device. Clearing browser/site data, resetting the browser profile or losing the device can remove the local working plan. Free Personal does not provide cloud plan recovery, so keep an encrypted .styrvia backup if the plan matters.
The guided Walkthrough requires no email or financial inputs. Encrypted .styrvia backups and result-sharing snapshots are created locally; Styrvia receives them only if you deliberately send them to Styrvia.
4. Processors and recipients
Cloudflare
Delivers and protects the website and browser app, provides bot protection on protected forms and supports aggregate Try counting. Cloudflare may process standard technical request information as part of delivering and securing the service.
Brevo
Handles optional double-opt-in email lists and sends website contact-form messages to Styrvia’s support mailbox. Mailing lists require a separate opt-in.
Payment providers
Revolut and PayPal process payments under their own terms and privacy notices. Styrvia receives the transaction information made available to the recipient.
The current Styrvia support mailbox is Gmail, so Google processes contact and support correspondence after Brevo delivers a website message and when Styrvia replies. Google Analytics processes website-use data only after you allow optional analytics.
Personal data may also be disclosed where required by law, or where reasonably necessary to establish, exercise or defend legal claims.
5. International transfers
Brevo states that its hosting databases are in the EU. Cloudflare, Google and payment providers may process data internationally using the transfer mechanisms described in their privacy documentation, including adequacy decisions, the EU–US Data Privacy Framework and/or Standard Contractual Clauses where applicable.
6. Retention
| Data | Retention approach |
|---|---|
| Records from previous Personal downloads | Normally 3 years after the latest registered download/Terms acceptance, unless longer retention is needed for a legal obligation or dispute. |
| Professional interest/enquiry records | Normally up to 3 years after the last relevant contact. |
| Plus product feedback | Aggregate category counts may be retained as research totals. Optional comments are deleted when no longer useful for product research. |
| Mailing-list data | Kept while subscribed. A minimal suppression record may be retained after unsubscribe to respect the opt-out. |
| Payment/accounting records | Transaction and supporting accounting records are retained for the period required by Danish bookkeeping/tax rules; accounting material is generally kept for 5 years from the end of the financial year it concerns. Records may be kept longer where necessary for an unresolved dispute or other legal requirement. |
| Contact/support/business correspondence | Normally deleted within 12 months after the matter is resolved, unless it is needed longer for a legal obligation or unresolved dispute. |
| Sensitive support files and attachments | Deleted as soon as they are no longer needed and in any event within 30 days after the support issue is resolved. |
| Website/security metadata | Styrvia does not maintain a separate visitor-log database. Cloudflare retains technical/security information under its service configuration. |
| Aggregate standalone update-check counts | Stored as monthly totals by app edition and version for release-maintenance and product-usage trend analysis. Styrvia does not store email, installation ID, plan data, IP address or user-level event rows for this metric. |
| Aggregate Personal download counts | Stored as daily totals by Personal release version, without email address, installation ID, IP address or user-level event rows. |
| Google Analytics data | Collected only after consent. User-level and event-level retention follows the configured Google Analytics property setting. You can withdraw analytics consent at any time using Analytics settings. |
| Google Analytics cookies (_ga and _ga_*) | Set only after consent and configured to expire after up to 12 months from when they are set. Withdrawing consent through Analytics settings removes Styrvia’s Google Analytics cookies from that browser. |
| Short-lived download access cookie used by previous Personal distribution | Previously used for about 15 minutes after licence registration so the browser could retrieve the protected download. |
| Browser-app access cookie used by previous Personal distribution | Previously issued access cookies could last up to 12 months. |
| Aggregate Try funnel counts | Stored only as aggregate totals by date, website version, approved event, source group and campaign. Duplicate suppression is memory-only during the current page load; Styrvia does not use browser storage or send a visitor/session identifier for this first-party aggregate funnel. |
7. Cookies and local browser storage
Personal Early Access uses local browser storage for the working plan and locally available app files for offline core use. These are functional product-storage features, not advertising identifiers. Clearing site data can remove the local working plan and locally stored app files.
Optional Google Analytics is off until you choose “Allow analytics”. If you decline, the Google tag is not loaded. Your choice is stored locally and can be changed in “Analytics settings”. Styrvia does not use advertising or cross-site profiling.
The Walkthrough suppresses duplicate measurement events only in memory during the current page load. It does not use browser storage or send a visitor/session identifier for this first-party aggregate funnel. Selecting Yes / Somewhat / No at the end of the Walkthrough sends only that fixed category.
If you have already chosen “Allow analytics”, the Try start, result, completion and Personal-click events are also mirrored to Google Analytics for campaign attribution. If analytics is declined or has not been allowed, Styrvia sends no Try event to Google and does not load the Google tag.
8. Mailing-list consent
Release/project emails and Plus notifications require separate optional opt-ins and Brevo double confirmation. You are not subscribed unless you confirm.
9. Voluntary payments
Payments are handled by the external provider or bank you choose. Styrvia may receive the payer information, amount, currency and transaction/reference details normally visible to the recipient. Do not put financial-model information in a payment reference.
10. Your rights
Subject to the conditions in the GDPR, you may have the right to access your personal data, correct inaccurate data, request deletion, restrict processing, object to processing based on legitimate interests, and receive certain data in a portable format. Where processing is based on consent, you may withdraw that consent at any time. To exercise a right, contact [email protected].
You may also complain to the Danish Data Protection Authority, Datatilsynet. Datatilsynet →
11. Automated decisions
Styrvia does not use website, email or support data to make decisions about you based solely on automated processing. App calculations are user-directed model outputs.
12. Security and data minimisation
In Personal Early Access, financial modelling and household plan data stay on your device during normal use. When the browser app is online, ordinary app and update requests do not need financial-plan values. Standalone copies may use the limited update checks described above. Encrypted .styrvia files add passphrase protection and portability; keep the passphrase separate from the file. Styrvia does not receive or recover it. Support files are shared only if you choose to send them.
13. Changes to this notice
Material changes to Styrvia’s data-processing arrangements will be reflected by updating the version and date on this page.