The English text is the legally binding version.
Last updated 2026-08-26. Issued by the 765T Flow publisher.
What this policy covers
This policy describes personal data processed by 765T Flow when you create an account, activate the product, use Community, or send feedback. It is issued by the 765T Flow publisher.
It does not govern Autodesk, Revit, or the AI client you connect to 765T Flow. Those parties have their own terms.
Three rules
Revit model files (RVT, RFA) do not leave the customer machine through 765T Flow.
Licensing traffic — who activated, which machine identifier, and when — is recorded when a machine is activated. Those records are required to issue or refresh an entitlement. Early Access does not charge a subscription fee.
Detailed product-usage telemetry is opt-in. No cloud telemetry is required for the local runtime.
What we collect
Account email (Google sign-in or magic link). Google subject identifier when you use Google. Google profile names are not published automatically; Community uses a random BIMer alias unless you explicitly choose a public display name. Optional installer-profile details you provide. Community posts, comments, tags, image attachments, reports, and moderation records when you use those features. A random machine identifier minted on first activation — not a hardware serial. Product version and Revit year reported by the add-in. Timestamps of entitlement issue, renew, session heartbeat, and takeover. Feedback text only when you press send. A session cookie on the website. Hashed device and magic-link tokens.
How much you used: a running count of billable calls, sent with the licensing heartbeat. Each entry is a limit name, the billing period it belongs to, and a number. Early Access sets no limits, so today there is nothing to count and nothing is sent. When a paid plan does set one, the count is what tells you and us how much of it is left.
What we never collect
Revit or family files, element unique ids, project paths or project names — unless you deliberately place that information in a Community post, comment, or image. Prompts, LLM provider keys, or AI-client conversation content. Windows user names, host names, MAC addresses, or hardware serials. Which tools you ran, in what order, on which model, or with what result — the billable-call count above is a total, and carries no tool name, so nothing in it can be read back as what you were working on.
Why and how long
Account, profile, and machine-binding data exist to issue a signed entitlement, limit active machines, and support you. Community content and its images remain available until you delete them, the publisher removes them, or you ask for account deletion; moderation and abuse-prevention records may be kept for up to two years. Unbound machine rows are kept ninety days. Entitlement, session, and conflict records are kept two years. Feedback is kept two years after you send it. Website session cookies last thirty days or until you sign out. Magic-link tokens last fifteen minutes or until used. Device access-token hashes last thirty days or until revoked.
Your choices
You can ask us to remove your Community contributions or report content that appears unsafe or inappropriate by emailing flow765t@gmail.com. Licensing and moderation records required to prove a past entitlement, protect users, or resolve a report may be retained for the periods above. You can refuse Community, feedback, and usage telemetry; the local product still runs.