Privacy Policy

Last updated 18 November 2026

This policy explains how ScreamX Inc., doing business as opensignals (“opensignals”, “we”, “us”), collects, uses, shares and protects personal information when you visit opensignals.so, use the opensignals app, or use our API and MCP server, including from AI apps such as Claude, ChatGPT, Codex and Cursor (together, the “Services”). It sits alongside our Terms of Service. Questions: hello@opensignals.so.

1. Who we are and our role

opensignals is operated by ScreamX Inc., 1007 N Orange St, Wilmington, DE 19801, USA.

When we are the controller. For your account, billing, support and website data, we decide how the information is used and we are responsible for it.

When we are your processor. For the content of your workspace — the people and companies in it, their signals, your LinkedIn conversations, lists, scores and workflows — your organisation is the controller and we process it on your behalf to provide the Services (see section 7). If you need a data processing agreement, email us.

2. What we collect

  • Account information. Your name, work email and password (stored only as a one-way hash by our sign-in provider), your workspace and role, and your teammates.
  • Connected LinkedIn accounts. The session cookies needed to act as that account (encrypted), a browser profile (user agent, screen size, time zone) so LinkedIn sees a consistent device, the network address it uses, its public profile details and plan, and the account’s own LinkedIn activity that you switch on as signals: messages, connection requests and invitations, profile views, follows, and engagement with your posts and company page.
  • Workspace content. Professional information about people and companies — name, job title, employer, location, LinkedIn profile and public post activity, work email and phone where you request them, company size, industry and technology — and the scores, tags, notes, lists, columns, workflows and history you create.
  • AI app connections (MCP). Which apps you connect, the access level you chose, and a log of every change each app makes in your workspace. We receive only the requests the app sends to opensignals, never your conversation with that app.
  • Integrations and API. Credentials for tools you connect (stored encrypted), webhook addresses, and access tokens (stored only as one-way hashes).
  • Payment information. Card details are collected and stored by Stripe, never by us. We keep plan, wallet and invoice records.
  • Technical information. Our hosting and sign-in providers keep standard logs (such as IP address, browser and time of request) to run and secure the Services. The website uses Pirsch, a cookie-free analytics service.

3. How we use it

  • To provide the Services you ask for: find and score signals, build lists, enrich records, run the workflows you start, show your inbox, and answer the requests of AI apps you connect.
  • To keep the Services and connected LinkedIn accounts safe: limits, pacing, warm-up and abuse prevention.
  • To bill you, support you, and tell you about changes to the Services.
  • To improve the product from aggregated usage. We don’t sell personal information, we don’t use it for advertising, and we don’t use your workspace content to train AI models.

4. AI features and AI apps

Some features use AI models to classify posts, judge buying intent, answer copilot requests and fill AI columns. Only the information the task needs is sent to the model provider, and providers don’t use it to train their models.

When you connect an AI app through our MCP server, it acts as you, only in the workspace you choose and only within the access level you grant. What the app does with the information it reads is governed by that app’s own privacy policy. You can see everything an app changed, and disconnect it, in Settings › AI apps.

5. Who we share it with

We share personal information only with service providers that process it for us under contract and on our instructions:

  • Railway: hosting for our app and background workers. Supabase: database, sign-in and file storage.
  • Stripe: payments. Resend: sign-in, notification and billing emails.
  • Anthropic, Google (Gemini) and TypeSafe AI: AI features (section 4).
  • Apify and data providers (such as Apollo, LeadMagic, MillionVerifier and Crustdata): collecting public LinkedIn activity and enriching records you ask us to enrich. When you connect your own provider key, that provider processes the request under your agreement with them.
  • Proxy providers: each connected LinkedIn account’s traffic passes through a dedicated network address.
  • Services you connect: Slack, Saleshandy, webhooks, Zapier, n8n and AI apps you authorise through our MCP server receive the data you set up for them. Their own privacy policies govern what they do with it.
  • Other cases: when the law requires it, to protect the rights and safety of our users or the public, or as part of a merger or sale (we’ll tell you before your information becomes subject to a different policy).

6. Shared business facts

Public professional facts we look up about a person or company — for example a current job title or a company’s size — may be reused to answer the same lookup for another customer, so it isn’t fetched twice. Your private workspace content — your lists, scores, notes, messages, workflows and LinkedIn sessions — is never shared with other customers.

7. The people in your workspace

The people in your lists and inbox are your contacts. You decide why and how their information is used, and we process it only to run the Services for you. You are responsible for having a lawful basis to contact them, for telling them about your processing where the law requires it, and for honouring their opt-outs. If you are someone an opensignals customer holds information about and you want to know what they hold or want it deleted, contact that customer directly. If you contact us instead, we’ll pass your request to them and help them answer it, and we’ll delete any shared business facts we hold about you (section 6).

8. Security

Each workspace’s data is kept separate from every other customer’s. Connections are encrypted in transit. LinkedIn sessions and integration credentials are encrypted at rest with AES-256-GCM, and access tokens and API keys are stored only as hashes. AI apps act only with the access you grant and only inside your workspace. Access to production systems is limited to the people who need it. No system is perfectly secure, so use a strong, unique password and tell us at once if you suspect a problem. If a breach affects your personal information, we’ll notify you and the authorities as the law requires.

9. How long we keep it, and deleting it

We keep your account and workspace content for as long as your account or workspace is active. AI app access tokens expire after one hour and are deleted or revoked when you disconnect the app. A connected LinkedIn account’s session is deleted when you disconnect it.

Deleting. To delete a workspace or your whole account, email hello@opensignals.so and we’ll do it within 30 days. Copies in backups are removed as the backups expire. We keep what the law requires, such as billing and tax records.

Exporting. You can export your records to CSV in the app or read them through our API. For a fuller copy, email us.

10. Where your data is stored, and international transfers

ScreamX Inc. is based in the United States, and our providers may process data in the United States and other countries. When we transfer personal information from the European Economic Area, the United Kingdom or Switzerland, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses (and the UK addendum) or the provider’s certification under the Data Privacy Framework.

11. Your choices and rights

Depending on where you live, you may have the right to:

  • know what personal information we hold about you and get a copy of it, in a portable format;
  • correct it, or have it deleted;
  • object to or restrict how we use it, and withdraw any consent you gave;
  • opt out of marketing emails;
  • appeal our decision on your request, and complain to your local data-protection authority.

EEA, UK and Swiss residents have these rights under the GDPR and UK GDPR. US state residents (including California, Colorado, Connecticut, Virginia, Texas and other states with privacy laws) have the right to know, access, correct and delete their information and to opt out of its sale, sharing for cross-context behavioural advertising, and profiling with significant effects. We don’t sell or share personal information in those senses, and we don’t make decisions with legal or similarly significant effects by automated means alone. We honour browser opt-out signals such as Global Privacy Control. We won’t treat you differently for using your rights.

To use any of these rights, email hello@opensignals.so. We may need to verify your identity first. We reply within 30 days (45 days where US state law allows) and tell you if we need longer. If the request concerns a customer’s workspace data, see section 7.

12. Cookies and local storage

On opensignals.so we use Pirsch, which sets no cookies, and no advertising or cross-site tracking scripts. In the app we use only what the Services need: sign-in cookies to keep you logged in, and your browser’s local storage for the workspace you have open, display preferences and a cache that makes the app load quickly. Signing out or clearing your browser data removes them.

13. Children

opensignals is a business tool and isn’t meant for anyone under 18. We don’t knowingly collect information from children. If you believe a child has given us information, contact us and we’ll delete it.

14. Changes to this policy

We’ll update this policy as opensignals changes and as the law requires. When we make a change that matters, we’ll tell you in the app or by email before it takes effect, and change the date at the top of this page.

15. Contact

Questions about privacy or your data, or a request about your rights: hello@opensignals.so. By post: ScreamX Inc. (opensignals), 1007 N Orange St, Wilmington, DE 19801, USA.