Keep the useful record.
Capture the purpose, source references, setup and checks. Review examples and company details before sharing. A saved record is not a code backup, and saving does not test or run the automation.
Sharing & privacy
Good work is shared
with care.
Share what a teammate needs to get started. Keep credentials and private conversations out of the workflow.
We’re developing the team-memory experience. The isolated pilot includes in-chat cards, record exports, following and reviewed workflow improvements. Here’s what those mean for sharing, alongside the current service information.
Sharing and source access are separate.
The test workspace supports private and team records. Sharing a record does not grant access to its repository, accounts or running app. Keep passwords, API keys and temporary access links out of saved content.
Plan for people and tools changing.
A team record helps the next person understand the automation. Keep source and service accounts under appropriate company ownership, and arrange access before a colleague leaves. AffinityAI does not retain someone’s credentials or keep their personal accounts running.
A copy you control.
Export the records you can access, with previous content versions and discussion separately opt-in. Other people’s private workflows are excluded. Review a downloaded copy before sharing it: AffinityAI’s access controls no longer govern the file. Source code and credentials are not included.
Evidence with its limits.
Sites observations are labelled as assistant reports, with the date, observed version and evidence. The GitHub pilot connection is designed for read-only source checks on selected repositories; activation is still pending. These checks do not edit or back up code, grant colleagues source access or verify a running automation.
You choose what to follow and change.
Saving or opening a workflow does not automatically follow it. Updates respect current workflow access. Adopting an improvement requires a preview and confirmation; it changes the saved record, not the running automation. AffinityAI does not observe unrelated AI conversations.
Your AI tool has its own terms.
Connecting a tool does not make all providers’ data policies the same. We’ll explain each supported connection and what it can access.
Clear answers, no big promises.
AffinityAI’s current security page describes the providers, access controls and limitations of the existing service. Read the current service details.
Requesting early access
We use the details you submit to respond about AffinityAI’s team-memory offer. It does not subscribe you to a paid plan or a marketing newsletter. You can ask us to remove your request at privacy@affinityai.app.
Read our Privacy Notice, Terms, DPA and provider list. These public preview pages do not set analytics cookies.