Privacy Policy

Last updated: September 26, 2026

This Privacy Policy explains how Frequency ("Frequency", "we", "us", or "our") collects, uses, processes, stores, and shares information when you use the Frequency web application and the Frequency Chrome extension (together, the "Services").

1. Scope and purpose of the extension

The extension's single purpose is to learn how a user prefers to work with Claude and apply the resulting personalization context to that user's Claude preferences. It does this by analyzing prompts the user submits, generating derived communication and working-style signals, displaying those signals to the user, and synchronizing generated personalization text to Claude when that feature is available.

2. Information we collect and how we collect it

2.1 Submitted Claude prompt text

When a signed-in Frequency user submits a prompt on Claude by pressing Enter, submitting the composer form, or clicking Claude's Send button, the extension temporarily reads the submitted prompt text. The text is held only in extension runtime memory long enough to perform local analysis with the machine-learning model packaged inside the extension.

Frequency does not transmit raw Claude prompt text to Frequency servers, AWS, an external AI provider, an analytics provider, or an advertising provider. Frequency also does not read or collect Claude's responses, complete conversation histories, unrelated page content, content from other websites, or password fields on websites. The extension does not record continuous keystrokes; it reads the composer value when the user submits the prompt.

2.2 Derived prompt and preference signals

Local analysis converts a submitted prompt into derived characteristics such as prompt-length and structure measurements, interaction depth, and communication or working-style signal labels. The extension sends these derived signals to https://api.tryfrequency.com together with the user's Frequency identifier, a session identifier, and a timestamp. The transmitted record does not contain the raw prompt text.

2.3 Account and authentication information

We collect account information that a user provides, which may include name, email address, organization, department, job title, profile image, and preference answers. When a user signs in through the extension, the email address and password are sent over HTTPS to the Frequency authentication service for verification. The extension does not save the password in Chrome storage. It stores the returned user identifier, access token, refresh token, token-expiration information, and session identifier locally so the user can remain signed in.

2.4 Profile choices and feedback

We collect preference answers, confirmations, corrections, and other profile feedback that a user intentionally submits through the Frequency extension or web application. We associate this information with the user's Frequency account to create and improve the user's profile.

2.5 Claude preference synchronization

Frequency may generate a personalization block, also called tool context, from the user's derived signals and stated preferences. To provide the synchronization feature, the extension opens a background Claude settings tab, places that generated text into the relevant Claude preference field, saves it, and verifies that it persisted. This action shares the generated personalization text with Anthropic through the user's Claude account. It does not share the user's raw prompts with Anthropic separately from the prompts the user independently submits to Claude.

2.6 Technical and service information

When the extension or web application communicates with Frequency's service, our server may automatically process standard request and security information such as IP address, user-agent or browser information, requested API endpoint, request time, response status, and error or diagnostic information. We use this information to operate, secure, debug, and measure the reliability of the Services. The extension also keeps limited local operational state, such as synchronization status, timestamps, failure reasons, and notification state.

2.7 Support communications

If a user contacts us, we collect the email address, message contents, and any other information the user voluntarily includes so we can respond to the request.

3. How we use information

• Authenticate users and maintain secure account sessions.
• Convert locally derived signals and submitted preferences into a Frequency working-style profile.
• Display profile insights, preference questions, progress, and confirmations requested by the user.
• Generate and synchronize personalization context with the user's Claude preference settings.
• Operate, secure, maintain, debug, and measure the reliability of the Services and prevent fraud or abuse.
• Respond to support requests and important service communications.

We do not use extension data for personalized advertising, retargeting, credit or lending decisions, data brokerage, or purposes unrelated to Frequency's disclosed user-facing features.

4. Where information is stored

• On the user's device: Chrome extension local storage holds account identifiers, authentication tokens, session information, synchronization state, locally applied context identifiers, and notification state. Raw prompt text is not written to Chrome storage.
• On Frequency's systems: Account information, derived signals, user-submitted preferences and feedback, generated profile information, synchronization state, and limited server logs are stored on infrastructure operated for Frequency through Amazon Web Services.
• In the user's Claude account: Personalization text that the extension writes into Claude preferences is stored and processed by Anthropic as part of the user's Claude account.

5. Parties with whom information is shared

As of the date of this policy, Frequency shares or makes information available only to the following recipients for the stated purposes:

Frequency does not sell personal information. We do not share extension data with advertising networks, data brokers, or independent analytics providers. If we add a new party that will receive user data, we will update this policy before that sharing begins.

6. Retention and deletion

• Raw Claude prompts: retained only temporarily in extension runtime memory while local analysis occurs and discarded after the derived signals are produced. They are not retained on Frequency servers.
• Local extension data: authentication and operational values remain in Chrome local storage until they expire, are replaced, the user signs out, or the extension is uninstalled.
• Account, profile, preference, and derived-signal data: retained while the account is active. Following a verified account deletion request, this data is deleted or anonymized within 30 days unless a legal obligation requires longer retention.
• Server, security, and diagnostic logs: retained for up to 30 days, unless a longer period is necessary for an active security, fraud, abuse, or legal investigation.
• Support communications: retained only as long as needed to resolve the request and meet applicable security or legal obligations, then deleted or anonymized.
• Claude preference data: personalization text saved to Claude remains subject to the user's Claude settings and Anthropic's retention practices. A user can edit or delete it from Claude settings.

7. Security

Frequency uses technical and organizational safeguards appropriate to the information processed. These include HTTPS encryption in transit, authenticated API requests, access controls, and operational monitoring. Authentication tokens are stored in Chrome extension local storage and are not exposed to ordinary web pages. No transmission or storage method can be guaranteed to be completely secure.

8. User choices and rights

• Users can sign out to clear locally stored authentication data.
• Users can manage the extension's site access through Chrome.
• Users can uninstall the extension at any time.
• Users can view or update available profile and preference information through Frequency.
• Users can edit or remove synchronized personalization text through Claude's settings.
• Users can request access, correction, export, or deletion of their Frequency account data by emailing support@tryfrequency.com. We respond to verified requests within 30 days.

9. Chrome Web Store Limited Use disclosure

Frequency's use of information received from Chrome and the extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use data only to provide or improve the extension's disclosed single purpose, maintain security, and measure the performance and reliability of that functionality. We do not permit humans to read raw Claude prompts because raw prompts are not transmitted to or stored by Frequency. Human access to other account data is limited to what is necessary for support with the user's consent, security or abuse investigation, legal compliance, or aggregate and anonymized internal operations.

10. International data transfers

Frequency and the service providers identified above may process information in countries other than the user's country. Where required, we use appropriate safeguards for cross-border data transfers.

11. Children's privacy

The Services are not directed to children under 13 or the higher minimum age required by applicable local law. We do not knowingly collect personal information from children.

12. Changes to this policy

We may update this Privacy Policy to reflect changes to the Services or legal requirements. We will post the revised policy at this URL and update the fixed "Last updated" date. If a change materially affects how the extension handles user data, we will provide an in-product notice or obtain consent when required before the new practice begins.

13. Contact

For privacy questions or data requests, contact Frequency at support@tryfrequency.com.