Privacy & trust
Private by construction.
Synapse measures how work is organized, never the person. These aren’t settings someone can switch off. They’re how the product is built, and every page states who can see it.
1Aggregate onlyTeam figures need enough contributors to clear the privacy floor: 10 by default, never fewer than 4. Smaller groups are withheld, never estimated.
2Consent is yoursHuman state reaches Synapse only after you connect Life by Synheart yourself, and stops the moment you disconnect.
3Raw sensor data stays on deviceLife works out your state on your device and sends Synapse the resulting scores, never raw sensor readings.
4No one is rankedThere is no per-person metric view, ranking or drill-down. Admins see who has connected, never their numbers.
The privacy floor
Four people, or nothing at all.
- Every team figure is an aggregate of at least 10 contributing people by default. Admins can set the floor anywhere from 4 to 50, and lowering it asks them to acknowledge the trade-off first.
- A department below the floor shows its parent’s numbers, with a banner saying so.
- Below the floor, Synapse never says how many people contributed, because a count would expose who chose not to.
- A smaller team can see its own view only while every current member has opted in. If anyone opts out or someone new joins, it’s withheld again immediately.
k=10DEFAULT FLOOR · NEVER BELOW 4
Company
EngineeringShown with the company’s numbers
SalesShown with the company’s numbers
No count is shown for groups below the floor. Not even “9 of 10”.
Where your numbers can go
Three scopes, each with its own rule.
ALWAYS PRIVATEJust youMy Effectiveness and your agent decision records show your own detail. No one else, including admins, can open them.
ABOVE THE FLOORYour teamYour work and AI activity count toward your department’s totals. Your human state joins once enough people share it to clear the floor.
AGGREGATE ONLYYour companyLeads and admins see company aggregates. Your consented human state is one of many contributions, never shown alone.
What Synapse receives
The list is short on purpose.
What we receiveHuman-state scores such as focus, load and fatigue, with consentHow complete and reliable each reading isCalendar event times, status and type, never their contentCommit, pull request and review activity and timingIssue titles and state changes, AI seat and usage countsDocuments and channels you choose as knowledge sources
What we never receiveRaw sensor readings from your devicesPrompts, completions or AI suggestionsStored copies of your code: code search reads it live and keeps nothingIssue descriptions or commentsMessages outside channels you choose as memoryPages outside what you chose to share
Security
Agents get memory, not master keys.
The same rules apply to every person and every agent acting for them, and every governance event leaves a trail.
OAuth 2.1 with PKCEMCP clients sign in through a consent screen that shows who is asking and for what. Nothing is granted without an explicit click.
Encrypted credentialsTokens for your connected tools are encrypted with keys held in AWS KMS, and the database only accepts encrypted connections.
Source permissions respectedGoogle Drive, OneDrive and Notion documents reach an agent only if its person can open them at the source, checked on every call.
Content-free decision recordsWhen an agent is stopped or told to check in, Synapse records that it happened. No prompts or excerpts are stored.
Separate consentsMicrosoft 365 is connected with your tenant administrator’s consent, separately from any member’s Life connection.
Audit log and safe exportsGovernance events are recorded in an audit log. Exports carry team-level series, never per-person rows.