FlowTun

FlowTun

Privacy Policy

1. Information processed

  • Account details such as name, email, phone number, address, password hash, account status, account tier, payment status, parent account, and accepted policy timestamp.
  • Workspace and project membership, roles, permissions, invitations, and user administration activity.
  • Issue data including tasks, bugs, subtasks, descriptions, due dates, priorities, statuses, sprints, links, comments, replies, attachments, and change history.
  • Payment-related records needed for account upgrades, such as requested tier, current tier, transfer note, transaction status, review status, reviewer, review time, and failure reason if any.
  • Operational data required for authentication, password reset links, invitation links, image uploads, localization, payment confirmation, and security checks.

2. How information is used

Information is used to authenticate users, enforce permissions, route users to the right workspace/project, display dashboards and reports, track changes, send invitations and password reset emails, manage account status, verify upgrade requests, review payment confirmation, and keep the platform usable and secure.

3. Payment and banking information

The platform shows bank transfer information configured by the platform owner and stores upgrade confirmation records so the platform team can verify whether a requested tier should be activated. The platform does not need users to enter card numbers, online banking passwords, OTP codes, or payment account credentials.

Banks, payment intermediaries, telecommunication providers, internet providers, and government authorities may process their own records under their own rules. Their charges, taxes, fees, deductions, and processing are outside the platform's control except where the platform has a direct legal obligation.

4. Images, files, and rich text

Images inserted into descriptions or comments are processed to optimize storage and display. Pending images are kept only when the related description or comment is saved, reducing unused files on the server.

5. Access and visibility

Users only see accounts, workspaces, projects, tickets, transactions, and settings allowed by their permissions. Higher-ranked accounts are hidden from lower-ranked accounts unless permission explicitly allows visibility. Platform content management is restricted to the platform owner account and authorized platform support.

6. Retention and deletion

Project data, comments, files, payment confirmation records, and history may remain while a workspace, project, account, or transaction review record exists. Authorized users may delete workspaces or projects where permitted, and destructive actions require confirmation to reduce accidental deletion.

7. Contact

For privacy, account, payment, or access questions, contact [email protected].

Back to login
Submitting Please wait while we process your request.
Protected view Developer tools and source viewing are disabled for this workspace.