Effective October 9, 2026
share-doc is a place for a team's documents, chat and files, and the sharedoc CLI that syncs them to your machine. It is run by Brightmotion (“we”, “us”). This page says what we collect, what we do with it, who else touches it, and how to get it deleted. The short version: we store what you and your team put into share-doc so we can show it back to the people you shared it with. We do not sell it, show ads, or run third-party trackers; we measure how share-doc is used with our own analytics service, and never with your content.
Your account. Your email address, your name, a profile picture if you add one, and a password hash (scrypt — never the password itself). If you sign in with Google we receive your Google account id, email address and name. We also keep your settings: notification preferences, working hours, status, search defaults.
What you put in. Documents and every revision of them, comments, chat messages, direct messages, reactions, drafts, and uploaded files (images, video, PDFs and anything else), each with who made it and when. This is the product; it is stored so it can be shown to the people who have access to it.
Your devices and agents. When you use the CLI: a token for each machine you log in from, the machine's name, and which local folders are paired with which projects (the folder path, not the contents of anything outside it). When a workspace admin creates an agent user, we store it like any other account. Posts made through an agent carry the agent's name.
Notifications. If you turn on browser notifications, the push subscription your browser gives us (an address at your browser vendor's push service). We record when you were last active, so that notifications are emailed or pushed only while you are away.
Huddles. The audio of a call goes through Cloudflare's call servers, which forward it to the others in the call, or else directly between the people in it (WebRTC). We set up the connection, and record who joined and left and when. We do not record, store or listen to the audio, and Cloudflare only forwards it.
Huddle transcripts. When a huddle is being transcribed (everyone in the call sees that it is, and anyone in it can turn it off), Cloudflare also streams each person's audio to our servers, which turn speech into text on our own speech-recognition service as it arrives. The text is written into a document in the workspace, like any other doc, with who said it and when. The audio is held in memory for a few seconds while it is transcribed and then dropped: it is never recorded, stored or sent to anyone else.
Link previews. When a message links to a web page, our servers fetch that page's title, description and picture to show a preview under the message, and keep them for a few hours. The linked site sees a request from our servers, not from you: the preview's picture comes through us too. Nothing about who posted or viewed the link is sent. A YouTube video in a preview loads YouTube's player (its no-cookie version) only when you press play.
Usage analytics. We measure how share-doc is used, with AgentHog, Brightmotion's own analytics service. On the public pages (the home page, the docs, the changelog, this page, sign-up and log-in) that is the pages visited, clicks, how far a page was scrolled and, for the film on the home page, how much of it was played and which of its controls were used. Inside the app it is which kind of page you opened (a document, a channel, the board — never which one) and named actions such as signing up, creating a project, connecting a folder, sending a message or opening search, with counts and types but never titles, file names, paths, project or channel names, or anything you wrote. The CLI reports each command's name, the names of the flags used (not their values), how it ended and how long it took, with its version and operating system. Each of these is tied to your account, so we can see how a person uses share-doc over time; device details (screen size, language, time zone) come with them. A browser that sends Global Privacy Control or Do Not Track is not measured; the CLI's reporting is turned off with sharedoc telemetry off, SHAREDOC_TELEMETRY=0 or DO_NOT_TRACK=1. Separately, to run the service and price it, our servers measure each workspace's storage, network traffic, number of members and how many were active, as counts for the workspace (with its name), not for any person.
Technical logs. Our servers and hosting providers log requests — IP address, time, the URL, the browser's user agent and, when you're signed in, your account — to run, secure and debug the service.
Sign-in history. To protect your account, we record each sign-in (and failed attempt), sign-out, password reset request and password change, with the IP address and browser it came from. The IP address and browser are deleted after 90 days; the rest stays with your account.
If you connect a Slack workspace to your share-doc account, you authorize our Slack app to act as you in that workspace, with the permissions shown on Slack's consent screen. Then:
Slack data is used only to show it to you in share-doc and to carry your replies back. It is not sold, not used for advertising, not shared with anyone but the people you add, and not used to train AI models.
We do not sell personal information, use it for advertising, or share it with data brokers. share-doc has no ad trackers, and its usage analytics stay with Brightmotion: they are not shared with or sold to anyone. We do not use your content to train AI models. When you point your own AI agent at share-doc through the CLI, what the agent does with what it reads is between you and that agent's provider.
The people your workspace and project settings say can: workspace members, project members at the role they were given, the people in a channel or direct message, and anyone holding a share link you created. Workspace admins can manage members and projects in their workspace. Brightmotion staff can access stored data when needed to operate the service, fix a problem you reported, or comply with the law — not to read it for any other reason.
We use a small number of companies to run share-doc. They process data on our behalf and only to provide their service:
We may also disclose information if the law requires it, to protect people's safety or our rights, or as part of a merger or sale of the service, in which case this policy continues to apply to it.
One cookie, sd_session, keeps you signed in; it lasts 30 days, is not readable by scripts, and is only sent to share-doc. The browser's local storage keeps interface preferences — sidebar width, font, which panels are open — on your device. For the usage analytics above, a random visitor id is kept in a cookie, agh_uid, and in local storage with the current visit's id (agh_sid); they last a year and are only sent to Brightmotion. There are no advertising cookies.
We keep your account and content while your account exists. Archiving a document, file or conversation closes it; it does not delete it, and a document keeps its revision history. Request logs are kept for a limited period by our hosting providers.
To delete your account, or specific content, email [email protected] from the address on your account. We delete your account and personal information within 30 days. Content you created in a shared workspace belongs to that workspace too: we remove your name from it or delete it on request, but a workspace admin may ask us to keep the workspace's documents intact. Backups age out on their normal schedule.
Everything travels over HTTPS. Passwords are hashed with scrypt; session, CLI and share-link tokens are stored only as hashes; Slack tokens are encrypted. Access to production systems is limited to the people who run the service. No system is perfectly secure; if we learn of a breach that affects your data, we will tell you without undue delay.
Wherever you live, you can ask us to tell you what we hold about you, give you a copy, correct it, or delete it, and you can object to how we use it. Much of it you can see and change yourself in Settings, and the CLI can copy every document you can read to your own disk. For anything else, email [email protected]; we answer within 30 days. If you are in the EU, the UK or California you have these rights by law, and you may also complain to your data protection authority. We process your data to provide the service you signed up for, and for our legitimate interest in keeping it secure and working.
If your account was created by your organization's workspace, your organization may control that workspace's content; we may refer a request about it to them.
share-doc is a work tool and is not meant for children under 16. We do not knowingly collect information from them; if you believe a child has an account, email [email protected] and we will delete it.
When this policy changes we update the date at the top. If a change materially affects how we use information we already hold, we will tell you by email or in the app before it takes effect.
Questions, requests or complaints: [email protected].