This page explains how Cardsflow approaches account protection, operational safeguards, and the handling of user information.
What this page covers
This page provides a general overview of:
- account access protection
- operational controls
- user-submitted information
- support-related information handling
- practical user responsibilities
Our general approach
We aim to reduce risk by combining clear product boundaries, limited workflow scope, controlled support processes, responsible access practices, and internal review for trust-sensitive content and policies.
Security is not just a technical issue. It also depends on how clearly a product is scoped, how support is handled, and whether users follow good account practices.
Information users may share with us
Depending on the workflow, users may provide information such as:
- account contact details
- support requests
- billing or workflow questions
- product feedback
- limited operational information needed to resolve issues
How we handle operational and support information
We aim to handle account and support-related information in a way that is:
- limited to the purpose of the request
- reviewed only by appropriate personnel
- retained according to internal policy or legal requirements
- not used beyond the legitimate operation of the service
Account protection: what users should do
Users should take reasonable steps to protect their own accounts and workflows, including:
- using strong, unique passwords
- limiting who has access to operational tools
- reviewing payment workflows regularly
- avoiding shared credentials
- contacting support promptly when suspicious activity appears
Important limitation
No online system can promise zero risk.
We aim to reduce risk through product design, operational controls, and support processes, but users should still evaluate whether the service is appropriate for their specific workflow and risk tolerance.
If you need help with a security or account concern
If you believe there is an account issue, security concern, or operational problem that requires attention, please contact support as soon as possible.