JOEBook demo

Privacy Policy

This page explains how Joe handles the information used to provide accounts, connected applications, task execution, and support.

Account data
Connected app data
Support and security
Privacy and policy visual.
LEGAL

Information used to operate Joe

The policy should make it clear what is collected, why it is collected, and how users can control their data.

What the policy should cover

A useful policy should explain the practical data flows without burying the user in vague legal language.

Accounts

Information needed to create and manage Joe accounts.

Connected apps

Data used to let Joe work inside other applications.

Security

How Joe protects the systems and information it touches.

Your choices

The ways users can ask questions or manage their data.

EXAMPLE

Policy that is easy to read

A useful policy should explain the practical data flows without burying the user in vague legal language.

1What is collected

A useful policy should explain the practical data flows without burying the user in vague legal language.

2Why it is needed

A useful policy should explain the practical data flows without burying the user in vague legal language.

3How it is protected

A useful policy should explain the practical data flows without burying the user in vague legal language.

4How long it is kept

A useful policy should explain the practical data flows without burying the user in vague legal language.

5How to ask questions

A useful policy should explain the practical data flows without burying the user in vague legal language.

Use the policy to set expectations clearly.

If you need help understanding how Joe handles data in your deployment, book a demo and we will review it directly.