FlowGrid legal center
Clear rules.
Clear responsibilities.
Website visitors should know what is collected. Operators should know what they control. Guests should know where to exercise their rights. These documents keep those roles separate.
Public documents
Written for people,
not policy software.
Product contracts
A PMS or POS needs more than website terms.
A paid rollout must be governed by a signed contracting pack that matches the actual product architecture, payment flow, hosting locations, vendors, and support commitments.
Request contracting informationCustomer agreement
Purchased modules, fees, implementation, support, availability, renewal, suspension, termination, liability, and data export.
Data processing terms
Controller and processor duties, customer instructions, confidentiality, security incidents, subprocessors, audits, deletion, and international transfers.
Security schedule
Verified technical and organisational controls, access management, encryption, logging, backups, vulnerability management, and incident response.
Subprocessor register
Every production vendor that can process customer data, the service it provides, processing location, and change-notification process.
Payment terms
The licensed payment parties, PCI responsibilities, settlement, disputes, refunds, chargebacks, and the card information FlowGrid never stores.
Acceptable use
Prohibited activity, messaging rules, integrations, credential security, platform abuse, investigation, and enforcement.
Privacy requests