Dockit is built around intentional knowledge capture and transparent data handling.

• Dockit helps you save notes, links, files, messages, and imported knowledge from connected tools.
• Your saved content can be organized, searched, and used in AI-powered answers.
• This policy explains what is stored, how it is used, and where you stay in control.

Dockit stores the content you choose to save or import, along with the metadata needed to organize and retrieve it later.

• Notes, links, files, and images you save directly
• Imported content from connected integrations
• Profile and account details needed to run your account

Dockit collects data through the actions you take in the app and the integrations you choose to connect.

• Direct capture inside the app
• Forwarding content to Dockit
• Importing content from authorized integrations

Note: Dockit is centered on intentional capture. It is not designed to pull in everything from every source automatically.

WhatsApp works through forwarding.

• Dockit only receives the messages or media you send to the Dockit number.
• Dockit does not read your full chat history.
• There is no background chat syncing.

Slack access is based on the connection and permissions you approve.

• Dockit can sync messages and files from the Slack content you authorize.
• Slack data can then become searchable and available to Ask AI.

Note: Dockit only accesses channels you authorize.

Confluence content is imported through the spaces or pages you choose.

• You choose what Dockit should import.
• Imported docs can be searched and used in AI responses.
• You can re-sync later using the saved selection.

AI is used to help organize and answer questions over the knowledge you save.

• AI can help summarize and connect saved content.
• Ask AI uses the relevant context from your knowledge when answering.
• AI responses are best treated as helpful guidance, not a substitute for checking the source.
• Dockit does not claim ownership of the content you save or import.
• Your content is processed only to provide retrieval, organization, and AI-powered features.

Note: Where possible, use the source context in Dockit to verify an answer.

Your data is used to provide the Dockit experience you ask for.

• To store and organize saved knowledge
• To power search and retrieval
• To support AI features over your saved content
• To support connected integrations you enable

Dockit is designed to protect account access and saved content with practical safeguards.

• Authenticated APIs require your account session.
• Integrations use explicit connection flows.
• Disconnecting an integration prevents future syncs from that connection.
• Secure storage, access controls, and encryption in transit and at rest are used where appropriate.

Retention is based on what Dockit needs to provide your account experience.

• Saved content and connection state are kept until they are changed or removed through product controls.
• You can delete saved content, disconnect integrations, and request account removal as those controls become available.

Note: Retention behavior may evolve as product controls become more granular.

You stay in control of what Dockit can access.

• Choose what to save
• Choose which integrations to connect
• Choose what to import from supported sources
• Disconnect integrations when you no longer want them active
• Update account details and review connected content through available product controls

Use Dockit for content you have the right to save, search, and work with.

• Only connect sources you are allowed to access
• Only import content you are permitted to use
• Review AI outputs before treating them as final

You are responsible for securing your account and reviewing connected content.

• Use secure login methods
• Verify your account details when asked
• Log out on shared devices when needed

Questions about privacy or usage can be directed to Dockit support.

• Use the help or support channels available in the product.

This policy may change as Dockit evolves.

• Updated versions can be delivered remotely as the product and controls mature.

Note: Future versions can be delivered remotely and versioned without changing the screen architecture.