FLOW ACADEMY LTD

Privacy

Effective date: October 2026

Contents
  1. Overview
  2. Singular (attribution)
  3. OneSignal (push)
  4. In-app AI assistant
  5. No data exchange between users
  6. No personal profile
  7. Unique id
  8. Emails to the developer
  9. Changes
  10. Contact

Overview

This privacy note describes how apps associated with FLOW ACADEMY LTD handle information. It is written for people who use those apps and for anyone who emails the studio. The practice is narrow on purpose: the products are built so they do not assemble a personal profile, and so people do not send personal data to each other through the apps.

When we say “unique id,” we mean an identifier used for attribution and for push delivery — not a name, not an email, not a phone number. Attribution uses Singular. Push notifications use OneSignal. The in-app AI assistant can reply to what someone types; it is not a human and not professional advice; those messages are used only to answer and are not passed to other users.

Singular (attribution)

Singular is used for attribution. That means install and campaign measurement so the studio can understand which channels bring people to the apps. Singular works with a unique id tied to the app install context. It is not a license to invent a social graph or a marketing biography of the person.

We do not treat Singular as a place to store your name, email address, phone number, address book, or precise location. If you want detail on Singular’s own processing, review Singular’s documentation and policies. In our product design, Singular sits on the attribution path from the device — not between users.

OneSignal (push)

OneSignal is used for push notifications. Delivery depends on a unique id associated with the installation so a notification can reach the right device. Push content is meant to inform about the product — updates, reminders the person opted into, or operational notes — not to open a chat between users.

We do not use OneSignal as a personal inbox for private data exchange between people. As with Singular, the identifying item on our side of this path is the unique id, not a profile assembled from contacts or precise location.

In-app AI assistant

Some screens include an AI assistant that can talk with the person using the app. The assistant is software. It is not a human. It does not provide professional advice — legal, medical, financial, or otherwise. Treat its replies as product help text generated for that moment, not as counsel.

What someone writes to the assistant is used only to form a reply. Those messages are not passed to other users. The assistant is not a channel for user-to-user messaging and must not be read as one.

No data exchange between users

Users do not send personal data to each other through these apps. There is no social graph product here, no inbox between accounts for personal dossiers, and no feature that forwards what you typed to another person as a message network.

If a screen shows shared or public content curated by the product, that is not the same as piping your private inputs to another user. The design goal is separation: your assistant prompts stay on the reply path; attribution and push stay on Singular and OneSignal with a unique id.

No personal profile

The apps build no personal profile of the kind that stitches together name, email, phone, contacts, or precise location into an identity record for the studio’s convenience. We do not ask the product to become an address book clone or a location memoir.

Operationally, that means product analytics and messaging lean on the unique id and on event signals required to run the app — not on harvesting contact lists or continuous precise location for profiling.

Unique id

The only identifying item called out for attribution and push in this note is a unique id. It exists so Singular can attribute and OneSignal can deliver. It is not a substitute nameplate for a private citizen profile, and it is not shared with other users as a handle for personal messaging.

Emails to the developer

If you email FLOW ACADEMY LTD at [email protected], you choose what to write. Those messages arrive as ordinary email so the studio can respond. Email content is not fed into a user-to-user app channel. Keep passwords and unnecessary sensitive data out of email when you can.

Changes

We may update this privacy note. The effective date at the top will change when we do. Continued use of the apps after an update means the revised note applies. Material changes are reflected in this document rather than buried in marketing copy.

Effective date for this version: October 2026.

Contact

Questions about privacy go to FLOW ACADEMY LTD by email at [email protected]. You may also use the Contacts page on this site.