Privacy Policy

Last updated: 12 October 2026. This policy covers the Peek Chrome extension, the website at https://peekbeside.com, and the paid plans sold for Peek.

Peek is operated from that website. Contact: support@peekbeside.com.

The published extension sends account data, messages, and page text only over HTTPS to https://peekbeside.com. It does not send that data to a raw IP address over HTTP.

What we collect

We collect data only when you use Peek. We do not read pages you have not sent, and we do not keep a browsing history.

• Account. If you sign in with Google or Apple, we receive the name, email address, and account id that you approve. A guest on this browser is merged into that account when you sign in. We store the plan, the day’s platform-message count, the day’s web-search count, and any top-up balance.
• Chats. We store the messages in a chat so you can reopen it. That includes text you type, text you select on the page, an image you paste, and a screenshot you ask Peek to take of the visible tab.
• Website content. When “include this page” is on, or you ask Peek to read the page, the title, URL, and page text of that tab are sent for that turn and stored with the chat. Peek does not collect the content of tabs you do not ask about.
• Request metadata. If you ask about the calls the page made, Peek can list method, path, status, and a short response preview. Cookie and Authorization headers, and headers whose names look like secrets, are removed in the browser. Those values are not sent to the model and are not stored.
• Authentication secrets. If you add your own model key, or headers for an MCP server, Peek encrypts them and stores them on your account. A sign-in ticket and an install id stay in this browser. The install id is also stored as a cookie on peekbeside.com so the same browser can be recognized after the extension is reloaded. Peek does not read cookies on the pages you visit.
• Things you add. Skills, knowledge-base documents, MCP server addresses, and feedback you write are stored on your account. Feedback can include an email address if you type one. The current page is not attached to feedback.
• Payments. Paid plans are billed by Creem. We store Creem’s customer id and subscription id. We do not receive or store your card number.
• Usage counts. The website records a page view. The extension records that the side panel was opened (at most once a day) and that a message was sent. Those events do not include the page address, the page text, or the message text.

How we use it

• To answer the message you sent, including reading the page, request list, screenshot, knowledge base, skill, or MCP server you turned on for that turn.
• To keep your chats, settings, and plan on your account.
• To enforce daily limits and to apply a subscription or top-up after Creem confirms payment.
• To read feedback you send us.
• To count visits and messages, so we can see whether the product is used. We do not use that count to advertise to you.

Who receives it

We share data only as listed here. We do not sell personal information.

• Peek. Account data, chats, skills, knowledge bases, MCP settings, feedback, and billing ids are stored on the servers that host peekbeside.com.
• Google. When you choose Google sign-in, Google receives the sign-in request and returns the name, email, and account id you approve. Google Analytics for Firebase, operated by Google, receives the website page view and the extension events described above. Those events are sent to https://www.google-analytics.com and do not include page content or message text.
• Apple. When you choose Sign in with Apple, Apple receives the sign-in request and returns the name, email, and account id you approve.
• The model provider for that turn. The prompt for that turn, which may include the page text, selected text, screenshot, and earlier messages in the chat, is sent to the provider of the model you are using. That is either Peek’s platform model provider, or the provider behind a key you added (for example OpenAI, Anthropic, DeepSeek, or another address you enter).
• Tavily. When the question is not answered by the current page, the search query is sent to Tavily at https://api.tavily.com. Reading a public link you gave does not use Tavily. That read is a request to the site in the link, without your cookies.
• An MCP server you add. If you connect an MCP server, the tool arguments for that turn are sent to the URL you configured. That operator is chosen by you.
• Creem. When you subscribe or buy a top-up, Creem (https://www.creem.io) receives the checkout, charges the card, handles tax, and sends the receipt. Creem is the seller of record. Peek does not send your page content or model key to Creem.

How we protect it

The published extension and this website transmit user data over HTTPS. Model keys and MCP headers are encrypted at rest and are decrypted only to make the call you asked for. They are not shown again in the side panel. Card numbers are not stored by Peek.

How long we keep it

We keep account data, chats, and files you added while the account exists. Email support@peekbeside.com to ask for the account and its chats to be deleted. We aim to answer within 3 business days. Payment records that Creem must keep are kept by Creem under its own policy.

Children

Peek is not directed at children under 13, and we do not knowingly collect their information.

Changes

If this policy changes, the date at the top of this page changes. The current text is always at https://peekbeside.com/privacy. The side panel links to that page from the account screen.