GSA Flow operator
- GSA Flow operator
- Grupo Santa Ana
- Privacy and support contact
- contact@gsaflow.com
1. Information we use
We process registration and authentication data, records you enter and technical information needed to run the service: name, email, account identifier, session, IP address, security events and usage.
Depending on enabled features, you may record amounts, accounts, cards, categories, family members, pets, vehicles and suppliers, and submit photos, invoices, contracts, PDFs, messages and audio. Do not provide bank passwords, authentication codes or card security codes. Avoid unnecessary health or other sensitive information.
2. Sign in with Google
If you choose Google sign-in, we request the openid, email and profile scopes. We use your Google account identifier, email and verification status to authenticate and link your Flow account. Google may return basic profile information; we do not request your Google password or access to Gmail, Drive, contacts or calendar.
The identity link is stored with your Flow account for access and security, not advertising. Google sign-in does not send your Flow documents or financial records to Google. You can revoke access in your Google account settings; this does not automatically delete your Flow account or existing records.
3. Purposes and legal grounds
We use information to provide the requested service, authenticate, organise records, generate reports and manage permissions. The legal ground is performance of the contract or steps you request before entering into it. Legal obligations may require retention of tax documents when purchases become available.
Fraud, abuse and incident prevention rely on our legitimate interest in protecting the service and its users, taking your rights into account. Optional sharing of reports and messages with support depends on specific, revocable choices. Processing sensitive information requires its own applicable legal ground; uploading a file alone does not establish one.
4. AI and conversations
AI is optional and must be enabled for your account. When you request an analysis, the files, messages, audio and context needed for the task may be sent to the OpenAI API. AI may produce a transcript or proposed record; review information that affects your finances.
Conversation history supports continuing tasks and investigating errors. Rating a task does not automatically allow support to read the conversation: sharing a report and sharing messages are separate choices. Feedback records support system fixes and do not automatically train a model.
OpenAI states that API data is not used to train models by default unless explicitly opted in. This does not mean zero retention: periods depend on the service and provider settings. This policy does not automatically authorise submitting conversations for training.
5. Storage and access
Records are held in the service database; files are held in private storage configured for the environment, on the server or in an object service such as Amazon S3. Access to data and documents requires authorisation. People you authorise in a workspace can view information according to their permissions.
An image used only to extract information may be retained temporarily. An original you choose to keep follows the archived-file lifecycle. Deleting an original does not itself delete amounts or information already confirmed in a financial record.
6. Providers and transfers
We use infrastructure and email providers and, when enabled, AWS for hosting/storage, Cloudflare for protection, Google for sign-in and OpenAI for AI. They receive the information needed for their functions. A payment integration will have its own disclosures before becoming available; a roadmap entry does not mean it is active.
A provider's processing may involve countries outside your place of residence. International transfers subject to the GDPR or LGPD must use appropriate legal mechanisms, including contractual clauses or an adequacy decision where applicable. The inventory of providers, regions and safeguards must reflect integrations actually enabled.
7. Retention and deletion
We retain information while it is needed for your account and the features you use. Deletion requests take legal duties, security and legal claims into account. Environment-specific criteria and periods must separately address accounts, financial records, files, conversations, logs and backups.
Temporary files, trash, versions and messages have their own retention cycles. Removing a file from view may precede physical disposal; backups follow their rotation cycle. An AI rating does not extend the conversation's retention. Operational periods and the deletion procedure must be confirmed before public registration opens.
9. Your rights and contact
Under applicable law, you may request access, correction, deletion, restriction, portability, objection and withdrawal of consent. Use the contact shown on this page. We will verify your identity only as needed to protect information and respond within legal deadlines.
You may complain to the competent authority, including CNPD in Portugal or ANPD in Brazil. Accounts are intended for a responsible adult; information about dependants should be entered only by someone entitled to do so, respecting those people's rights.
10. Changes to this policy
The version and date appear on this page. Relevant changes to purposes, sharing or rights must be communicated before they apply where required. An update does not replace specific consent that a new use of information may require.
You can print this page or save it as a PDF using your browser menu.