Trust & security

Everything we send, you can check.

Intakra works from records you can check and links every lead to where it came from. We hold your data to the same standard.

Public evidence, explained

Intakra reads records about companies: job posts, SEC filings, federal contract awards, layoff notices (WARN filings), company web pages, and public DNS and certificate records (the technical records that show when a company sets up a new website or app). We never track your prospects: no cookies on your buyers, no website visitor identification, no contact lists. Each lead identifies the role to look for and why, with a LinkedIn search link. When people-data features are enabled for a workspace, a lead may also name a person and a backup, as described under “People we name” below. After you allow optional analytics, we use PostHog to see how visitors and customers use Intakra: the pages viewed, clicks, and session recordings with typed inputs masked (not recorded on sign-in, code-entry, checkout or settings pages). That activity is linked to your email once you submit the Roadmap quiz or sign up. Meta website audiences let us show our ads to people who visited our public pages before. We also collect error telemetry (Sentry). Saying No on the analytics banner, or a browser privacy signal, turns the optional analytics off, and the privacy policy has the full detail.

Every lead comes with its sources

Each thing we find carries the date it happened, the date Intakra first saw it, and a link to the source. We keep a copy of the page, so you can always see what the source said that day.

Nothing sent on your behalf

Intakra does not write or send email to your prospects. It emails you (and optionally Slack) when a company on your list starts something relevant, and pushes the ones you choose to your CRM. What happens next is up to you.

Separate workspaces

Every customer has their own workspace, and every read is limited to it. What we find in records about a company can be shared across customers, but your account list, what you sell, and what you push to your CRM or mark “Not relevant” are never visible to anyone else.

How your data is handled

What we collect

Your account and workspace details, what you tell us you sell, the accounts on your list, what you push to your CRM, mark “Not relevant”, or snooze, and any data you connect (for example, CRM records you import). We don’t buy or use website visitor identification or shared topic-intent data.

How the LLM sees it

Model calls go through OpenRouter. Text from the records we read is sent to group related findings into one project, and your description of what you sell is sent to check whether that project fits you. We don’t use your data to train models.

People we name

Role guidance and a LinkedIn search link do not require a named contact. When people-data features are enabled for a workspace and a match is available, a lead may name up to two people: the person who most likely owns the project and a backup. For each we keep their name, role, LinkedIn page, and a business email when our provider rates it verified or likely deliverable. We start with the public proof itself, such as an officer named in an SEC filing or a leader on the company’s own website, and may use our people-data provider, MoltSets, where provider access is enabled, or Apollo when MoltSets has no match. A named person or business email is not guaranteed on every lead. We never store phone numbers or personal emails, never show an email for people at companies based in the EU, EEA, UK or Switzerland, and delete these details after 30 days, or the same day a workspace cancels. Anyone can ask us to remove their details and not name them again at hello@intakra.com.

Access, control & deletion

CRM connections use OAuth with limited scopes, and you can revoke them from Settings at any time. You can request an export or deletion of your workspace. Payment card data is handled by Stripe and never stored by Intakra.

Subprocessors

Services Intakra uses to operate and support enabled features, by role:

Cloud hosting & databaseCloudflare (application and snapshot storage), Neon (Postgres database)
LLM processingOpenRouter, through Cloudflare AI Gateway (groups what we find on the record into projects and checks whether each one fits what you sell)
Email deliveryResend (sign-in codes, lead emails and account email)
CRM connectionsComposio (holds OAuth tokens for the CRMs you connect)
PaymentsStripe (subscription billing; card data never touches Intakra servers)
Product analytics & errorsPostHog (product analytics), Sentry (error monitoring)
People dataMoltSets (name, role, LinkedIn page and business email where workspace people-data features and provider access are enabled)
People data, fallbackApollo (one person with a verified business email where provider access is enabled, only when MoltSets has no match)
Job listingsTheirStack (job posts for companies whose own job page we cannot read)
News searchExa (cited news such as new executives, funding and expansions, after free news sources)
Technology historyBuiltWith (when a tool was first and last seen on a company website)

Security review & DPA

Enterprise conversations can include a security review and a Data Processing Agreement. If your procurement team needs to run diligence before you buy, we’ll meet you there.

Questions about security or data handling? Email hello@intakra.com and we’ll get you what you need. See also our Privacy and Terms.