Privacy: this website
This notice covers appro-app.com and the measurement preference it can share with appro-ai.com, both operated by Appro-app SRL. Audience measurement remains disabled on appro-ai.com. Each application has its own policy, reachable from its page.
Who is responsible
Appro-app SRL, Brussels, Belgium. For any question about this notice or about your data, write to hello@appro-app.com.
What this site collects
If you allow audience measurement, Appro loads Umami to count page visits and interactions such as section views, scrolling and clicks. For visitors arriving through the shared festival outreach link, email signature link or Facebook Waterloo link, the campaign may be counted without naming the recipient, festival or post. The measurement events we send use fixed page paths and declared event fields.
The measurement script is not loaded before your choice. Umami also receives technical information when your browser requests its script and sends a measurement event. We do not claim that this information is anonymous or that no personal data is processed.
Your measurement choice
Audience measurement is optional. You can allow or refuse it in the notice, then withdraw or review your choice using the measurement control in the footer. A new choice covers appro-app.com and appro-ai.com for the same Umami audience-measurement purpose. Previously saved version 3 choices remain limited to appro-app.com until you deliberately save a new choice. Withdrawing stops future measurement requests from this page; it cannot recall a request already sent.
A saved choice expires at most 180 days after its original date. Transferring it to appro-ai.com preserves that date and does not renew the period. An expired or invalid choice does not permit measurement. The transfer uses temporary URL fragments between the two sites; they are cleared before returning to content and are not part of hosting requests. We do not send the full page address, its query, fragment, title or referrer in our measurement events.
Limits of our measurement events
Appro's own measurement events omit email addresses, form content, free text, page-supplied identifiers and advertising identities. We do not combine these events with contact records or use them for advertising profiles. Umami may derive visitor and session metrics from technical request data; its exact processing terms remain under review.
When you send the contact form
Appro-app SRL receives the email address and message you submit, plus the page context chosen by the site. They are used only to answer and follow up your request. They are not added to a newsletter, marketing list or audience measurement.
For a project or service enquiry, this processing takes steps at your request before a possible contract. For a general question, it relies on Appro-app SRL’s legitimate interest in answering and documenting the exchange. A Firebase Function hosted by Google in Belgium validates the request, and Brevo transmits the message to Appro as transactional email.
An enquiry that does not become a service is deleted or anonymised no later than 24 months after the last useful exchange. Contractual, accounting or legal records may be retained longer where the law or the defence of a right requires it.
Who else is involved
Optional audience measurement uses Umami Cloud. The account displays the EU (Frankfurt) region; its contractual scope, support access and subprocessors remain under review. Contact requests use Google Firebase for validation and Brevo for transactional delivery. Brevo stores its main service databases in the European Union and may use contracted support and infrastructure subprocessors outside the European Economic Area under recognised GDPR transfer safeguards. No advertising company is involved.
Your choices
Refusing means the optional Umami script is not loaded. You can review your refusal or withdraw an earlier permission from the footer. After a preference has been transferred, Appro AI also offers a preference control to synchronize it or request withdrawal on both sites. Synchronization happens when arriving on Appro AI from Appro App or when you use that control. It does not instantly update an unrelated tab already open on the other site. If browser storage is unavailable or the source origin cannot be verified, the transfer is not accepted and does not authorize measurement. Appro AI measurement remains disabled.
Depending on where you live you may also have rights to access, correct, delete, restrict or object to processing, to portability, and to complain to a data protection authority. In Belgium that is the Autorité de protection des données. Write to hello@appro-app.com to exercise any of them.
Storage on your device
Appro App stores your choice in local browser storage under appro.consent.analytics. A new version 4 record contains its state (accepted, refused or custom), original date, version number, a true or false audience-measurement choice, the purpose audience-umami-v1 and the two sites www.appro-app.com and appro-ai.com. Appro AI stores a verified copy under appro.consent.shared. Older version 3 records remain App-only. To verify a transfer, Appro AI stores a temporary random challenge, its creation time and a return path in tab storage. The challenge is valid for at most two minutes and must be consumed before a transfer is accepted. The challenge and transferred record are cleared from the URL during a successful transfer. The measurement layer does not create a separate measurement identifier. Umami's own request processing and applicable terms are still under review.
How long the counts are kept
The Umami account currently displays six-month data retention. Actual deletion behavior and relevant contractual terms have not yet been independently verified. This provider retention is separate from your saved browser preference, which is valid for at most 180 days from its original date, including after transfer. An expired or invalid imported preference is rejected when checked and removed where browser storage permits.
While this site is being built
Nothing at all is recorded, and the measurement script is not even loaded, on a local copy or a preview address. Measurement begins only on the published site at its own domain.