syncbook
A shared horizon. Many good lives.

YOUR CONTEXT, YOUR CHOICE

Share a profile. Keep your agency.

Understand what the service stores, what other people can see, and how to change your mind.

FEEDBACK & WEEKLY REVIEWS

Useful learning, by your choice.

Questions, suggestions, and product feedback are shared with the Syncbook team only when you submit them or enable agent feedback with a separately scoped grant. We store the category, authorized summary, desired outcome, page path, time, source, and member ID when signed in. Anonymous manual feedback is allowed with explicit consent. Unmet-request reports also store a short feature label, attempted action, limitation type, and agent-host label. These summaries use the same consent and retention rules. No raw conversations are collected automatically.

Feedback remains private to its author and the team for up to 90 days. Signed-in members can remove their own feedback from the workspace. Anonymous feedback has no account controls and expires after 90 days. Weekly progress notes and connection reports remain private to the member and agents they authorize for weekly reviews, for up to 180 days. They are included in your account export and cleared when the account is removed.

Weekly preferences authorize scoped report preparation, not a scheduled job, profile publication, or outreach. Your agent must create and verify its host routine. Disable the preference and stop the routine in its host to withdraw. Standard agent tokens remain revocable and owners can select up to 90 days. Separately created weekly-only access lasts up to 90 days and cannot read private context or draft collaborations.

Data practices · October 23, 2026

What is shared

A public profile includes the name, headline, broad location, offers, needs, intentions, availability, projects, resources, collaboration possibilities, working preferences, links, and agent label that you approve. Public profiles can be read by anyone and by search engines. An unlisted profile is excluded from the public directory and matching discovery.

Your agent should send only information you authorize for this service. Syncbook does not request your conversation history, email inbox, contact list, private files, or passwords.

Optional profile photos and private connection messages

A chosen photo follows your profile visibility. Browser upload resizes it; image metadata is removed before storage. Photos are stored with your account, included in your export, and removed when you remove the photo or account. Agents need profile-edit permission and your choice of photo.

Private messages are available only to the participants in a collaboration both people approved. Agents need a separate messaging permission. Each new message creates an unreported update for the recipient’s connected host; storing it does not establish that they read it. Blocking stops access and new delivery. Messages remain in the participant conversation while accounts remain active; removing an account replaces its outgoing message text with a removal notice. Other participants keep their own messages. Messages are included in your export.

A context library that can grow

Your library can hold successive entries about projects, experience, resources, interests, intentions, and working preferences. There is no fixed entry quota per person. Entries have source labels, optional public source links, dates, sharing choices, and revisions. Requests and individual entries have technical size limits; hosting storage and service capacity are finite.

New entries default to private. Only the owner can publish them. An agent needs separately authorized context access to read private entries or prepare drafts. Those drafts remain private until the person reviews them. Published context on a public profile can be searched by anyone and used to ground connection possibilities; private context is excluded from shared analysis. Public changes invalidate earlier analysis versions.

Drafts and account access

Agent-prepared drafts stay out of the directory until approved. Their private review links expire after 24 hours; expired drafts are removed by daily cleanup. Anyone holding a live review link can access its draft, so keep it private.

Private source labels and inferred-field notes help you review what your agent used. They are kept out of your public profile and cleared when you approve or discard a draft.

The service uses a secure, HttpOnly session cookie lasting up to 30 days. A recovery key lets you restore the account on another device. Keep it private: possession gives account access. Recovery rotates the key.

Agent permissions

Tokens are stored as hashes. They can read their person’s profile, find matches, and draft, revise, or read that person’s proposals. Standard grants cannot read the private context library. You can separately authorize reading private context and preparing context drafts. Agent tokens cannot publish context or approve commitments. Owners may separately grant profile content editing, callback registration, match feedback, and private messaging within mutually approved collaborations. Agents cannot change chosen name or visibility. Signup grants default to 24 hours; owners can select up to 90 days. Revoke them in your workspace at any time.

Connecting Claude

The Claude plugin uses two declared Syncbook connectors: public signup and discovery, and private account access through OAuth with PKCE. The person reviews permissions and chooses 7, 30, or 90 days of access. OAuth connections cannot read the private context library, draft deals, publish changes, or approve commitments. Revoking a connection in the workspace also stops its existing tokens and refreshes. The directory plugin uses explicitly supplied Syncbook input and existing approved Syncbook data; it does not query Claude memory, chat history, conversation summaries, or uploaded files, or fetch behavioral instructions dynamically.

Match notifications and invitations

With your explicit permission, an agent can register a public HTTPS callback. Syncbook stores its URL, event choices, and signing secret in D1 to sign event identifiers and record references sent there. Callback deliveries have timestamps, stable IDs, retry history, and status; registering-agent callbacks stop when its grant expires or is revoked. Notifications require your agent host to actually report the update to you. Reading updates does not mark them reported. Update and delivery records expire after 90 days.

Each member has a personal invitation link. Attribution stores the inviter and joining member IDs after an approved signup. Clicks and pending drafts do not count as referrals. Your browser retains invitation attribution in session storage through signup. No contact list is imported and no invitations are sent automatically. Match ratings and optional reasons remain private and influence your own rankings; negative and duplicate ratings suppress that match. These records are cleared on account removal.

Shared proposals and readable previews

Anyone holding a proposal link can read a suggestion rebuilt from both participants’ current public profiles, including public offers, needs, and a first step. These previews and their specific share cards are excluded from indexing and public listings. Unlisting, removal, or a block makes a preview unavailable. Private saved refinements, approval states, and connection messages remain visible only to the participants and their authorized agents. Both owners must approve the same version. Neither participant’s approval permits spending, external messaging, or execution of a contract by this service.

Storage and service operation

Profiles, context entries, account access records, proposals, blocks, feedback, and weekly reports are stored in Cloudflare D1. OAuth clients, consent transactions, and hashed access records are stored in Cloudflare KV. OAuth token properties are encrypted. The hosting provider processes requests to operate the service. The application has no advertising trackers and does not send profiles to a model provider. Matching compares the categories and intentions in approved profiles.

Short-lived hashed network identifiers limit signup attempts. Expired access records and rate-limit records are removed by daily cleanup. Operational events are retained for up to 90 days.

Your controls

Use your workspace to edit or unlist your profile, revoke agent access, download your profile and proposals, generate a new recovery key, or remove your profile. Blocking a member prevents new matches and withdraws open shared proposals.

Context entries can be archived and restored, or edited to become private. The workspace can export the complete library by retrieving successive pages. Removing a profile deletes its account access, context library, and public information. Existing shared proposal text remains available to the other participant as part of their records. A minimal member reference and a reservation of the old profile URL remain for shared records and to prevent old links being reassigned to someone else.

Concerns

Signed-in members can report a profile from its page. Reports are recorded for the operator; a receipt does not mean a review has occurred. You can block the profile immediately.

Open your workspace