PRIVATE PREVIEW

Product capabilities, integrations, availability, and proposed pricing remain subject to change.

Request access →

Effective 11 September 2026

Acceptable Use Policy

This policy applies to this website now and states the boundaries expected for any future FlowPoint testing pilot.

Authorization is mandatory

You may test only systems, applications, accounts, devices, APIs, and environments that you own or are explicitly authorized to test. A visitor cannot authorize testing of another party’s system. Scope must be documented before execution.

Prohibited activity

Do not use FlowPoint or this site for unauthorized access, credential attacks, malware, denial of service, evasion, surveillance, deceptive activity, scraping that violates rights or access controls, exploitation beyond an approved proof, or activity that harms people, systems, or data.

Credentials and test data

Future pilots must use dedicated, least-privilege test credentials where possible. Do not submit secrets through this marketing site. Test data must be lawfully sourced, minimized, and appropriate for the approved environment; avoid live sensitive data when representative data is sufficient.

Execution safeguards

A pilot scope should name target hosts or app identifiers, environments, allowed actions, rate limits, maintenance windows, contacts, and stop conditions. Human approval should remain in place for destructive, financial, externally communicative, or production-impacting actions.

Mobile applications

You must have the right to provide any APK, IPA, build URL, signing material, or connected account used in a future pilot, and permission to test the people, content, and systems represented by that build.

Enforcement

We may reject an early-access request or suspend a future pilot when activity appears unauthorized, unsafe, deceptive, or outside the agreed scope. Serious concerns may be preserved and handled as required by an applicable agreement or law.

Implementation and policy consistency review
These materials were reviewed against the implemented forms, storage, cookies, routes, and product claims. That review is not a lawyer’s approval and does not guarantee compliance in every jurisdiction.