Your research. Your privacy.

Service operator

CapWake is operated by Famplified LLC.

Contact and scope

For questions about CapWake’s data handling, contact info@email.famplified.com. This notice covers CapWake’s service. An AI client, source website or other service you choose to use has its own privacy practices.

Information we handle

• Account information: email address, verification status and an account identifier, used for secure sign-in.
• Research information: submitted event text, selected coverage and companies, saved watchlists, generated results, optional history labels, event types and timing, dates, fiscal periods or years, and review assessments with cited public-source passages.
• Service records: account allowance, usage, request identifiers and limited status information needed to run and protect the service.
• Support messages: information you choose to send to our contact address.

Hosting and authentication providers also process network and device information needed to deliver and secure requests, such as an IP address and browser details.

Why we use it

We use this information to authenticate you, maintain your watchlist, process requested research, display results, enforce allowances, prevent misuse, investigate faults and respond to support or privacy requests. CapWake does not sell your research inputs or use them for advertising.

Service providers and AI processing

Amazon Web Services (AWS) hosts CapWake and stores account and research data. OpenAI processes submitted events or extracted terms and relevant public source passages to provide the requested research. Private research is not added to CapWake’s shared source library.

AI requests disable stored responses where supported. That is not a promise of zero retention by a provider: separate abuse-monitoring or legal retention may apply. See OpenAI’s API data controls and AWS’s privacy notice for their practices.

CapWake’s application infrastructure is in the United States. Provider processing may involve other locations. Only submit information you have permission to share with these services.

Browser storage and cookies

The sign-in flow uses short-lived browser session storage to verify the login request. The authentication provider may use essential cookies on its sign-in domain.

Connecting an AI client uses an essential, secure cookie on mcp.capwake.com and a matching one-use approval record. Both expire after ten minutes. The record contains connection parameters, not your password or tokens; expired records become eligible for eventual database cleanup. Connector permission lasts 14 days and can be disabled in your workspace.

An essential, secure HttpOnly cookie on capwake.com restores your website sign-in after a page refresh for up to 12 hours from sign-in. The cookie contains a random session identifier, not your password or research. Refresh credentials are held in encrypted private server storage; signing out removes them from the session. Expired session records become eligible for eventual database cleanup. Short-lived access tokens and unsubmitted event text remain in page memory, not long-term browser storage.

Website analytics

CapWake uses Google Analytics to understand page visits across the website, including sign-in and workspace pages. Google receives the page’s general name and address, visit timing, a browser-generated identifier, and browser, device and network information. Analytics cookies help distinguish visits and sessions.

CapWake removes URL queries and fragments and uses fixed page names. We do not send research text, results, watchlists, email addresses, account identifiers, passwords or sign-in codes to analytics. Automatic form, search, click and scroll tracking, Google signals and advertising personalization are disabled. CapWake does not use advertising pixels.

Google processes analytics data under its own privacy policy. You can block analytics through your browser settings or use Google’s Analytics opt-out browser add-on. Blocking analytics does not prevent you from using CapWake.

Retention and deletion

Submitted text is removed from active research records when the analysis completes, fails or is deleted. Results, optional labels and event timing metadata become unavailable seven days after submission unless deleted sooner. Cleanup can be delayed by outages, and backups have a separate recovery window. See the data and deletion page for the detailed boundaries.

Account information and watchlists remain while the account is active. Contact us to request account closure, deletion, access or correction. We may need to verify account ownership before acting. Minimal records may need to remain for security, accounting or legal obligations; we will explain relevant limits when responding.

External AI clients

A connected AI app can receive and retain the research you request, including in its conversation history. Deleting a result in CapWake does not delete a client’s transcript. Review the client’s permissions and privacy settings separately.

Updates and requests

We will update this page when CapWake’s data handling changes. Use the effective date above to identify this version. Send privacy requests to info@email.famplified.com; do not include passwords, tokens or unnecessary sensitive documents.