Fruitask Security

How Fruitask protects your account and data — sign-on options, two-factor authentication, session control, API keys, audit logging, permissions, and data protection.

Overview

Security in Fruitask spans how you sign in, how sessions and access are controlled, and how your data is protected and governed. It’s designed so individuals and teams can keep accounts safe and meet organizational and compliance needs.

Account sign-in

  • Email + password with email verification.
  • Single sign-on options: Google and GitHub.
  • Enterprise SSO support for organizations that centralize identity.
  • Password reset via secure, time-limited links.

Two-factor authentication (2FA)

  • Add two-factor authentication for an extra layer at sign-in.
  • Backup codes are provided for recovery if you lose your second factor.
  • Sensitive security values (2FA secrets, backup codes) are never exposed back to the client.

Sessions & devices

  • Active sign-ins are tracked as device sessions, including device type (desktop/mobile/tablet) and the IP address used.
  • Sessions expire automatically and can be reviewed; signing out ends a session.

API keys (for developers)

  • Generate API keys to access Fruitask programmatically.
  • Each key has scoped permissions (read, write, delete, admin) and an optional expiry.
  • Keys track last used so you can spot stale or unused keys and revoke them.

Permissions & access control

  • Workspace access is role-based: Viewer, Editor, or a Custom set of granular permissions.
  • Permissions cover data (rows/columns), members, comments, chat, automations, plugins, launching public pages, and AI actions — and can be scoped per table.
  • The most restrictive rule wins when workspace and table permissions overlap, preventing accidental over-exposure.

Auditing & monitoring

  • An audit log records key actions with the user, action, IP address, device/user agent, and whether it succeeded or failed — useful for investigating account activity.

Data protection

  • Sensitive credentials you store (such as your AI API keys and external storage provider secrets) are encrypted and never returned to the browser.
  • Public vs. private files: private files are access-controlled with temporary, expiring links.
  • Bring your own storage lets organizations keep files in infrastructure they control (e.g., for data-residency needs).

Privacy & compliance

Fruitask provides standard legal and compliance resources, including Privacy Policy, Terms of Service, Cookie Policy, GDPR information, a Data Processing Agreement, a subprocessor list, and data deletion/export options.

Where to find it

  • 2FA, sessions, sign-in methods, password: Account → Security.
  • API keys: developer/API settings.
  • Permissions & roles: workspace member/collaborator settings.
  • Legal/compliance: the policy pages in the footer (Privacy, Terms, GDPR, DPA, etc.).

Requirements & access

Some controls (enterprise SSO, audit visibility, advanced data governance) are aimed at higher plans and organization admins. API access requires generating a key with the appropriate scope.

Limits & notes

  • Revoking an API key or ending a session takes effect immediately for new requests.
  • Turning on 2FA strongly improves account security — store your backup codes somewhere safe.

Tips

  • Enable 2FA on every admin/owner account.
  • Give integrations scoped, expiring API keys rather than broad, permanent ones.
  • Use Custom roles and per-table permissions to follow least-privilege access.