Privacy

FluxDesk Privacy Policy

This policy explains what information FluxDesk processes, how collaboration content is used, how AI requests work, and what device information is not collected when you accept the terms.

Current version: 2026-06-20

1. Information we process

  • Account information: name, email, avatar, language preference, role, project membership, and sign-in state.
  • Collaboration content: projects, requirements, tasks, comments, quick chats, documents, meeting notes, attachments, feedback, decisions, and risk information.
  • Operational records: event logs, timestamps, versions, and system state needed for security, audit, synchronization, notifications, and troubleshooting.
  • Integration information: third-party integrations configured by you or administrators, token status, delivery records, and necessary connection metadata.
  • Legal acceptance records: current terms version, privacy policy version, and acceptance time.

2. What terms acceptance does not collect

  • When you click accept in the terms and privacy banner, FluxDesk stores only the version numbers and acceptance time.
  • That acceptance action does not save IP address, device identifier, browser fingerprint, or extra fields used to identify a device.
  • FluxDesk does not use acceptance records for employee performance scoring, personal ranking, or productivity monitoring.

3. How we use information

  • To provide, maintain, and improve FluxDesk's project collaboration, work items, communication, documents, meetings, notifications, and search.
  • To enforce access control, project isolation, role permissions, audit, incident troubleshooting, and security protections.
  • To send notifications, generate drafts, synchronize integration events, or show collaboration context based on actions that users explicitly trigger.
  • To understand product reliability and experience issues using aggregated or de-identified information, not oppressive personal monitoring.

4. AI and third-party processing

  • When you use AI drafting, summarization, breakdown, or follow-up features, relevant context may be sent to configured AI service providers to complete that request.
  • AI responses are drafts or suggestions by default. Creation, assignment, confirmation, and changes still require explicit human action.
  • Third-party integrations receive only the information needed for that integration, such as notification delivery, code signals, external messages, or authentication callbacks.

5. Who can see content

  • Project content is visible by default only to authorized project members, owners, administrators, or explicitly involved participants.
  • Data from different projects, tenants, or organizations is not automatically mixed together in search, AI, or summary views.
  • Limited information may be processed by necessary personnel or vendors for security, legal, compliance, service maintenance, or actions you explicitly authorize.

6. Retention, deletion, and export

FluxDesk keeps information for as long as needed to provide the service, satisfy security audit needs, resolve disputes, and comply with law. Administrators may manage member access, deactivate accounts, clean project content, or request exports according to organizational processes. Some audit records may remain for a necessary period after an account is deactivated.

7. Security

We protect information with sign-in authentication, project permissions, audit records, secret management, least-necessary access, and infrastructure security controls. No online service can be absolutely secure; if you find a suspected security or privacy issue, please contact us promptly.

8. Contact

To access, correct, delete, or export your information, or to ask privacy questions, contact the FluxDesk team: [email protected].