Privacy policy
Your conversations live in Google Drive. CommentLane connects your browser to Google so you can keep notes and discussions beside the webpages they refer to.
What this policy covers
This policy covers the CommentLane Chrome extension and the website at commentlane.com. The extension is currently being prepared for public release. The website’s labeled example conversations are fictional and run in your browser; trying that preview does not connect your Google account.
Information the extension uses
- Your Google account: your account identifier, email address and any display name Google supplies, used to show which account is connected and keep accounts separate.
- Webpage context: the address and title of a page you comment on, selected text and nearby text, or a description and location reference for a selected image or element. This context helps place a comment when you return.
- Conversations: the comments and replies you submit, their Google identifiers, authors, dates and resolved status, and the corresponding records read from your connected group documents.
- Group access: document identifiers, names and permissions, including participant names or email addresses returned by Google. If you explicitly share a group, Google receives the recipient addresses you enter.
- Local activity: drafts, read/unread state, display preferences, group organization, cached conversations and information needed to recover or retry a save.
The extension reads supported pages after you activate it or allow access to that site. Captured source context is sent to Google when you submit a conversation. A page address or selected passage can itself contain private information, so review the audience before posting.
Google access and storage
Google handles sign-in. CommentLane requests access to your email identity and the Drive files you create with, or authorize for, CommentLane. It uses Google Drive and Docs APIs to create or load your CommentLane folder and documents, read and write native comments and replies, maintain a readable document index, and manage sharing that you explicitly request.
Google access tokens are handled by Chrome and the extension’s background process. They are not included in exported comment files or sent to the websites you annotate. CommentLane does not receive your Google password.
Posted conversations are stored in your Google documents. The extension also keeps a cache and recovery data in your browser profile. CommentLane does not operate a separate server or database that receives your Google conversations. Google processes the data sent to its services under Google’s privacy policy.
Who can see a conversation
“Only me” uses a personal document whose ownership and sharing are checked before private writes. A group uses a separate document. People with access to that document can see its conversation history, including the source context you submitted. They may also read and reply through Google Docs.
Google document permissions determine access. Changing permissions directly in Google can change who can read a document. Sharing a document does not grant access to a private source website. People who can read your comments may retain their own copies.
CommentLane uses Google user data to provide these commenting, synchronization and sharing features. We do not sell Google user data, use it for advertising, or use it to train AI models. CommentLane’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Your controls and retention
- Website access: use Chrome’s extension settings to change or remove site permissions. CommentLane also lets you pause its display on a page.
- Disconnect: stops the active account connection and clears downloaded groups and conversations from the extension. Account-specific drafts, preferences and recovery records remain on that device. Disconnecting does not delete Google files or revoke Google authorization.
- Export: the Library can download the active account’s currently loaded conversations and drafts as JSON. The export can be incomplete if some groups have not finished syncing.
- Drafts: discard an unsent draft from the Library. A save with an uncertain Google result must be reconciled first to avoid concealing a message that may already exist.
- Google data: manage document sharing and deletion in Google Drive or Docs. Revoke CommentLane’s authorization through your Google account connections.
- Device data: uninstalling the extension removes its local extension storage from that Chrome profile. Export any unsent drafts first. Downloaded exports and copies held elsewhere must be managed separately.
Google records remain subject to your document settings and Google’s retention processes. Local drafts and recovery records remain until you remove the relevant local data. Removing the extension or revoking its access does not erase your documents from Google Drive.
The website and support
The public website is hosted by Vercel, which processes network requests to serve it. Production pages use Vercel Speed Insights to measure page performance. Vercel describes those measurements as anonymous; they include page URL, browser/device information, country and timing metrics. These website measurements do not receive your extension comments or Google access tokens. Read Vercel’s Speed Insights disclosure and Vercel’s privacy notice.
If you email support, we receive your email address and what you choose to send. We use that information to respond and investigate your request. Support correspondence is kept as needed to handle the request and maintain the service. You can contact us about access to or removal of information you sent to support. Please omit passwords, access tokens and private document content unless it is necessary and you intend to share it.
Changes and contact
We will update this page and its date when our data practices change. For privacy or support questions, contact contact@commentlane.com.