Skip to content
ignaru
Book a demoStart free

Privacy

Last updated 17 October 2026

Who we are

Ignaru is run by Ignura Ltd (in formation), a company being set up in England and Wales. Company number: registration pending. Registered address: registration pending. Until Ignura Ltd is incorporated, the data controller for Ignaru is [controller until incorporation].

Questions about your data, or a request to use any of your rights: email [privacy contact email] or book a call.

The short version

  • Ignaru helps a team find leads, write outreach and book calls. To do that it stores your account, your team’s work and the leads your team adds.
  • No email goes to a lead unless an Admin on your team says yes. Every one names the sender and can be stopped with one click.
  • We do not sell personal data, show ads, or train AI models on your data. AI requests go only to hosts that keep nothing and train on nothing.
  • Your data is stored in London. Some of the services we use are based outside the UK, and this page names them.
  • You can ask to see, correct or delete your data. Self-serve export and deletion are not built yet, so for now we do it by hand.

Two roles

Your account. For your sign-in, billing and how you use the service, we decide what happens to the data. We are the controller.

Your team’s workspace. Leads, drafts, replies, calls, notes and chat belong to your team. Your team decides who to contact and why, so your team is the controller and we process that data for it, on its instructions. The processing terms are in our terms.

What we collect

  • Account. Your email and name, and the team you belong to with your role (Admin, Operator or Viewer). Ignaru gives you an avatar and a colour. When you ask for a sign-in code, your IP address and browser details go to WorkOS, our sign-in provider, to protect the account.
  • Your team’s work. Workspaces and their steps, comments and drawings, leads, drafts, replies, booked calls, the Brain (facts Iggy learns about your business), Iggy chat with any text files you attach, team chat and direct messages, marketing assets, an activity log, and your team’s settings.
  • Leads. For each person your team adds or Iggy finds: name, work email, role, company, website, LinkedIn address, why they fit, and what public pages and your connected tools say about them.
  • Connected apps. When you connect Gmail, new messages in that inbox reach us through Composio. We keep the text of a message only when it comes from one of your leads (as a reply, with the quoted history removed). For any other message we note that mail arrived, with no sender, subject or text.
  • Keys and tokens. If you add your own AI model key we store it encrypted (AES-256-GCM) and show only its last four characters. API tokens are stored as a one-way hash.
  • Billing. Your plan, credit balance and history, and the Stripe customer and subscription ids. Card details go to Stripe and never reach us.
  • Technical. Server logs, with emails, tokens and keys removed before they are written. Error reports (see Error monitoring). Rate limits count requests per IP address in memory and do not store them.
  • Landing page questions. Questions typed to Iggy on our home page go to an AI model for an answer and are not stored.

Why we use it, and the lawful basis

  • To run the service you signed up for: sign-in, workspaces, drafting, sending what you approve, billing. Basis: our contract with you.
  • To keep it secure and working: rate limits, abuse prevention, logs and error monitoring. Basis: our legitimate interest in a safe, reliable service.
  • To keep billing and tax records. Basis: legal obligation.
  • Lead data: we process it for your team. Your team needs its own lawful basis to contact each person, usually legitimate interests for business outreach.

We do not send marketing email. We do not use your data for advertising.

AI

Iggy uses AI models to read your website, research and score leads, write and rewrite drafts, sort replies, prepare call briefs, answer in chat and make marketing assets. The text a task needs goes to the model: for example your site’s pages, a lead’s details, your Brain facts and a reply you received.

  • Work paid in credits goes through the Vercel AI Gateway. The models are DeepSeek V4.1 Flash (the default), DeepSeek V4 Pro and Claude Haiku 5.5. Every text request asks the gateway for hosts with zero data retention (they keep no prompts or answers) and no training on your data, and names the only hosts it may use. For these models no host in mainland China is used, including DeepSeek’s own API.
  • Today that means DeepInfra, Morph and Parasail for DeepSeek V4.1 Flash; Azure, DeepInfra and Baseten for DeepSeek V4 Pro; and Anthropic, Amazon Bedrock and Google Vertex for Claude. Voice, if your team turns it on, runs on OpenAI, which does not train on it but does not offer zero retention.
  • If your team adds its own key (Anthropic, OpenAI, Google Gemini or OpenRouter), chat turns where you pick that model go to that provider on your account. Workspaces, background drafting, and Iggy in comments and team chat still use the gateway.
  • We do not train or fine-tune any model on your data.
  • Iggy can score and rank leads. It never sends on that basis alone: a person approves every email.

What gets sent on your behalf

  • An email to a lead needs an Admin’s yes, either on the Approve screen or when Iggy asks in chat. Iggy cannot send email when no one is there to say yes.
  • Approved emails go from your team’s connected Gmail (or the team’s Glasa campaign), so your team is the sender.
  • Every email sent through Ignaru ends with the sender’s name, company and postal address and a one-click unsubscribe link. Nothing is sent until an Admin has entered that address.
  • In Auto mode, which only an Admin can turn on, Iggy can act in your other connected apps without asking each time, for example posting a Slack message or updating a CRM record. Email and public posts still need an Admin’s yes.
  • Calendar invites are sent by an Admin, and Google emails the guest.
  • Sign-in codes and team invitations are emailed by WorkOS. Ignaru sends no other email of its own.

Who we share data with

These providers process data for us. Each gets only what its job needs.

  • Vercel: hosting and running the app, in London. Also the AI Gateway above.
  • Supabase: our database and live updates, in London (eu-west-2).
  • WorkOS: sign-in, teams, roles and invitations.
  • The AI model hosts listed under AI.
  • Composio: connections to your apps. It receives what each action needs, for example the recipient, subject and body of an email you approved.
  • Stripe: subscriptions and credit packs.
  • PostHog (EU Cloud): error monitoring, and product analytics with your consent (see Cookies and analytics).
  • Glasa: cold email campaigns, only if your team connects it. It receives the leads and emails your team approves for a campaign.
  • Cal.com: the booking form at /call. What you type there goes straight to Cal.com.

Apps your team connects (Gmail, Google Calendar, HubSpot, Slack, Hunter, Apollo and others) run on your team’s own accounts under their own terms. We also fetch public web pages, such as your site and lead company sites, to read them.

We share data with others only if the law requires it, or to protect people or the service from harm.

Where it is stored, and transfers outside the UK

Our database is in London, and the app runs in London. WorkOS, Composio, Stripe, Vercel and some AI hosts are based in, or process data in, the United States or other countries outside the UK. PostHog processes our error reports and analytics in the EU. Where a provider handles UK personal data abroad, we rely on UK adequacy regulations (including the UK–US data bridge for certified companies) or the UK International Data Transfer Addendum in that provider’s data processing terms. We do not send AI requests to hosts in China; see AI above.

How long we keep it

  • Your team’s data stays until your team deletes it or asks us to delete the account. We have no automatic deletion yet.
  • Deleting a lead removes their drafts and replies. A sent email cannot be deleted on its own; it goes when its lead is deleted. Activity lines and chat messages that mention a deleted lead stay until someone deletes them.
  • Disconnecting an app removes the connection at Composio straight away.
  • API tokens expire after a year. Sign-in helper cookies expire after 10 minutes.
  • Billing records are kept as long as UK tax law requires.
  • Logs and error reports are kept for the period set by Vercel and PostHog for our plan.

Cookies and browser storage

  • wos-session: keeps you signed in. Strictly necessary. It lasts up to 400 days unless you sign out.
  • Sign-in helpers (ig_oauth_nonce, ig_auth_pending and a WorkOS one): protect a sign-in in progress. Strictly necessary. 10 minutes.
  • Browser storage for your interface choices, such as a collapsed sidebar, your last workspace, table columns and unsent chat text. It stays on your device.
  • ig_consent: remembers your analytics choice. Strictly necessary. Six months, then we ask again.
  • ig_region: holds only “eu” or “x”, from your country, so we know whether to ask. Strictly necessary. Ends with your browser session.
  • Analytics (PostHog, EU Cloud): pages viewed, clicks, and session replays in which every word on screen and every input is masked. It stores an identifier in your browser. In the UK, the EEA and Switzerland, or if we can’t tell where you are, none of it loads until you say yes. Elsewhere it loads unless you say no. A no clears what it stored.
  • The booking form at /call is a Cal.com frame and may set Cal.com’s own cookies.

We never capture shared boards, public demo boards or unsubscribe pages. Our server also records product events per team (for example, “a draft was approved”) with no personal data and no IP address. We use no advertising cookies.

Error monitoring

When something breaks we send an error report to PostHog in the EU so we can fix it. Before it leaves our server we remove emails, tokens, keys, cookies and the query part of web addresses. A report includes the page or route, your team id, your user id if you are signed in, and the error and where in our code it happened. It sets no cookies and records no IP address.

Security

Data travels over HTTPS. Every record belongs to one team, and the server checks your team and role on every request. Model keys are encrypted and API tokens are hashed. Only an Admin can approve sends, change billing or turn on Auto mode.

Your rights

Under UK data protection law you can ask us to:

  • give you a copy of your personal data;
  • correct it;
  • delete it;
  • restrict or object to how we use it;
  • give you your data in a format you can reuse.

Email [privacy contact email] and we will reply within one month. Self-serve export and deletion are being built. Until then we handle these requests by hand. You can disconnect an app or leave a team yourself at any time.

If you are unhappy with how we handle your data, you can complain to the Information Commissioner’s Office: ico.org.uk/make-a-complaint, or 0303 123 1113. We would like the chance to sort it out first.

If a team using Ignaru contacted you

That team chose to contact you and is responsible for it. Every email sent through Ignaru names the team and its postal address and has a one-click unsubscribe link. Using it, or replying that you are not interested, puts your address on that team’s do-not-contact list: Ignaru then refuses to draft for you or send to you from that team again. The team can also delete your details from Ignaru. You can also email [privacy contact email], and we will pass your request to the team and help it act on it.

Children

Ignaru is for businesses and is not meant for anyone under 18.

Changes

When this page changes we update it here and change the date at the top.