Your data
Privacy Policy
Last updated: 9 Nov 2026
1. Data controller
The controller for the processing described in this policy is the Service’s publisher, whose full identity appears in the Legal Notice. They can be reached at hello@hanori.app.
2. Data collected and purposes
2.1 Site: contact form
When you use the contact form, we collect your name, email address and the content of your message. This information is sent by email via our hosting provider Hostinger’s SMTP server, directly and without going through a third-party transactional email service; it is not stored in a database. Legal basis: responding to your request.
2.2 Site: browsing data (Google Analytics 4)
If you accept the “Analytics” category in the hanori.app site’s consent banner, the Service uses Google Analytics 4 (GA4) to measure its traffic: pages viewed, traffic source, device type, visit duration. Legal basis: your consent, collected as described in the Cookie Policy.
2.3 App: payment data (Premium subscription)
If you subscribe to the Premium plan, your payment data (name, email, card details) is processed directly by our payment provider, Stripe Payments Europe, Ltd., under its own privacy policy. We never have access to your full card number. Legal basis: performance of the subscription contract (see the Terms of Sale).
2.4 App: account, billing and security events
The Hanori app (app.hanori.app) records, regardless of your cookie choices, a limited set of events tied to your account: sign-up (with your chosen language and, where applicable, the referral source described in 2.8), log-in, log-out, checkout started, subscription activated and cancelled, payment failed, and reaching a free-plan limit (with the type of limit reached). Payment and subscription events include the plan and its billing interval and, where relevant, the cancellation reason or the number of payment attempts. These events are linked to your account’s technical identifier, never to your name or email address. Purposes: monitoring the paid plan and free-plan limits, and detecting log-in anomalies. Legal basis: our legitimate interest in running and securing the Service (Art. 6(1)(f) GDPR).
2.5 App: aggregated usage statistics
To measure how the Service is used across all accounts, a partial copy of our database is synced to our analytics tool. It only contains pseudonymised usage data: the account’s technical identifier, dates (creation, last activity, onboarding completed), Premium status, and for each project, yarn, needle or pattern, its creation and modification dates, its status where applicable and its links to your projects — never your name, email address or the content you enter (titles, notes, files). Subscription data from Stripe (plan, status, amounts, dates) is synced the same way, without customers’ contact details. This data is used as aggregated statistics (activation, retention, conversion rates). Legal basis: our legitimate interest in understanding how the Service is used in order to improve it (Art. 6(1)(f) GDPR).
2.6 App: detailed analytics and session replay
If you accept the “Analytics” category in the app’s consent banner, some of your actions in the interface (for example adding or editing items, searches, opening a pattern) are recorded to understand how the Service is used. If you also accept the “Session replay” category, your sessions may be replayed for support and interface improvements; input fields are masked and the log-in and sign-up forms are excluded. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time from the app’s settings (“Manage my preferences”).
2.7 App: error tracking
When a technical error occurs in the app, an error report is sent automatically, regardless of your cookie choices: the error’s message and stack trace, the page concerned, browser and operating-system type, and your account’s technical identifier if you are logged in. This tracking runs in a minimal mode: no session replay, no capture of your actions, no other event. Purpose: detecting and fixing malfunctions and keeping the Service secure. Legal basis: our legitimate interest in keeping the Service working properly (Art. 6(1)(f) GDPR).
2.8 App: sign-up referral source
When you reach the Service through a link carrying campaign parameters (“UTM” parameters: source, medium and campaign name, e.g. “instagram” / “social” / “launch”), these parameters are passed to the app when you sign up, stored on your account and added to the sign-up event described in 2.4. No cookie or other tracker is used for this: the parameters only travel in the links’ address. Purpose: knowing which channels people discover the Service through. Legal basis: our legitimate interest in measuring the effectiveness of our communication (Art. 6(1)(f) GDPR).
2.9 App: information emails (newsletter and getting started)
When you verify your email address, or as soon as your account is created if you sign up with Google or Apple, your email address is added to a short series of getting-started emails sent in the days after you sign up and, unless you declined it when signing up, to the newsletter, which presents what’s new in Hanori. The data passed to our email provider, Mailjet, is limited to your email address, your name, your account’s language and your Premium status (yes or no), which are used to write to you in your language and tailor emails to your plan. None of the content you enter in the app is shared.
These emails only concern the Service you signed up for. You are informed of them when you sign up, where a box, unticked by default, lets you decline the newsletter. Every email, newsletter and getting-started alike, also contains an unsubscribe link you can use at any time, free of charge. Legal basis: our legitimate interest in keeping you informed about the Service (Art. 6(1)(f) GDPR), under the exception in Article L34-5 of the French Postal and Electronic Communications Code for similar products or services provided by the same company.
3. Retention periods
| Data | Retention period |
|---|---|
| Contact-form emails | 3 years |
| Google Analytics 4 browsing data | 14 months |
| Billing data (Premium subscription) | 10 years (accounting obligations) |
| App events, analytics, error reports and synced data (PostHog) | 1 year |
| Session replays | 30 days |
| Sign-up referral source (UTM parameters) | Lifetime of the account |
| Mailing contact (newsletter, getting-started emails) | Until the account is deleted, at your request or for inactivity; the contact is then deleted from Mailjet |
4. Recipients and processors
| Processor | Role | Location |
|---|---|---|
| Google (Google Analytics 4) | Audience measurement | United States — transfer covered by the Data Privacy Framework |
| Hostinger International Ltd | Site hosting and sending contact-form emails | European Union (Cyprus) |
| Stripe Payments Europe, Ltd. | Processing Premium subscription payments | Ireland (European Union) |
| PostHog Inc. (PostHog Cloud EU) | App analytics and error tracking | European Union (Germany) — company established in the United States, any access covered by the European Commission’s standard contractual clauses |
| Mailjet SAS (Sinch group) | Sending the newsletter and getting-started emails | European Union (Germany and Belgium) |
No data is shared with any other recipient or sold to third parties.
5. Your rights
Under the General Data Protection Regulation, you have a right of access, rectification, erasure, objection and portability over your data. You can exercise these rights by writing to hello@hanori.app. In particular, you can object to processing based on our legitimate interest (sections 2.4, 2.5, 2.7, 2.8 and 2.9) and withdraw your consent to detailed analytics and session replay (section 2.6) at any time, without affecting processing already carried out. You can also unsubscribe from information emails (section 2.9) at any time using the link included in each of them. You also have the right to lodge a complaint with France’s supervisory authority, the Commission nationale de l’informatique et des libertés (cnil.fr), or with your own data protection authority if you live elsewhere in the European Union.
6. Security
The Service is only accessible over an encrypted connection (HTTPS/TLS). Access to administration and hosting tools is restricted, and the Service’s dependencies are kept up to date to limit known vulnerabilities.
7. Changes to this policy
This policy may be amended to reflect changes to the Service or to the law. The version in force is the one published on this page, as of the last-updated date shown at the top.