Privacy Policy

The short version

ipLamb reads public web pages about a business and shows you where they disagree. To do that it stores your account details, the businesses you ask it to track, and dated copies of the pages it read.

• We do not sell your data, or share it for advertising. There is no exception to opt out of.
• There are no analytics or tracking scripts on this site. No Google Analytics, no advertising pixels, no session recording. The marketing pages set no cookies at all.
• ipLamb only fetches domains you have proved you control and then explicitly approved. It cannot be pointed at a site you do not own.
• You can get a copy of everything, or have it deleted, from inside the product. Both are built and working, not promises.

Who we are

ipLamb is operated by Ayraa Informatics Inc., a company based in Toronto, Ontario, Canada. For anything in this policy, including requests about your data, write to contact@iplamb.com.

What we collect

Your account

Your email address, a workspace name, and your role in that workspace. Your password is held by Clerk and never reaches ipLamb.

What you ask us to track

The businesses you add and their identifying details — names, domains, phone numbers, addresses, and similar — along with the source addresses you approve for checking.

What we read from the web

Dated copies of pages fetched from domains you have proved you control and explicitly approved, the facts extracted from them, and the exact sentence each fact came from. These copies are the evidence behind every finding, which is why they are kept rather than discarded after reading.

Billing

Your plan, and Stripe's identifiers for your customer and subscription records. Card numbers go to Stripe and are never stored by, or visible to, ipLamb.

Records of what happened

An audit trail of actions taken in your workspace — who did what, to what, and when — plus usage counts for enforcing plan limits, and any support or privacy requests you submit.

We do not ask for, and have no use for, government identifiers, health information, or financial details beyond what Stripe needs to take a payment.

Pages we read, and why we keep them

An ipLamb finding is only worth acting on if you can see what it was based on. So when ipLamb reads a page, it keeps a dated copy of that page as it looked at the time, and records the exact sentence each extracted fact came from. When the page later changes, the evidence behind the finding survives.

ipLamb fetches a domain only after you have demonstrated control of it — by publishing a DNS record, a meta tag, or a file at a known path — and then approved it as a source. It identifies itself as ipLambBot/1.0 (+https://iplamb.com). It reads whether a page asks search engines not to index it and reports that back to you as a finding, but it does not treat that as permission to stop: you have told us this is your site and asked us to check it.

Who else receives data

ipLamb is built on other companies’ infrastructure, and the honest list of who sees what is below. Each entry says what actually reaches them, not what they are capable of receiving.

Built but not switched on

These are implemented in the product and currently receive nothing. They are listed so that this page is already accurate on the day one is enabled, rather than quietly becoming wrong.

• Google PageSpeed Insights — Core Web Vitals measurement (built, not currently switched on). Would receive: The address of the page being measured, and nothing else. No account data and no page content.

Where your data is stored, and the border it crosses

Ayraa Informatics Inc. is a Canada company, but the service runs on Microsoft Azure in East US 2, which is in the United States. Your data is therefore stored and processed outside Canada, and outside the EU, EEA, and UK.

This matters in two practical ways, and we would rather you heard them from us. Data held in the United States is subject to lawful access requests under that country’s laws. And where the GDPR or UK GDPR applies to you, the transfer relies on the standard contractual clauses in our providers’ data processing terms. If this is a problem for your organisation, say so before you load data in rather than after.

How long we keep it

• Account and workspace data — for as long as the account is open.
• Stored page copies, extracted facts and findings — until you delete them, or until the workspace is deleted. They are not expired on a timer, because a historical record that silently thins out is not a record.
• The audit trail — retained after a deletion request, but redacted. What survives is the shape of what happened: that an action of a certain kind occurred, when, and against what. The contents are removed. We keep this because an audit log you can erase on request is not an audit log.

Your rights, and how to actually use them

Two of these are built into the product rather than handled by email, so they do not depend on anyone getting round to them:

• Get a copy. Request an export and the service assembles a machine-readable file containing your entities, identifiers, extracted facts, sources, findings and recommendations.
• Have it deleted. Request deletion and the service removes the workspace’s data, redacts the audit trail as described above, and marks the workspace closed.

A deletion request can be held if we are under a legal obligation to preserve the data — a live dispute or a lawful order. If that ever happens, the hold and the reason for it are recorded against the request, and we will tell you.

For correction, objection, restriction, or anything the buttons do not cover, write to contact@iplamb.com. We aim to respond within 30 days. We will not ask you to prove who you are beyond what is needed to be sure we are not handing your data to someone else.

Who can see your data at ipLamb

Nobody, by default. Staff access to a customer workspace requires an explicit, time-limited grant recorded against a specific case reference, with a stated reason and scope. A grant expires automatically and cannot exceed eight hours. Issuing one, using it, and revoking it are each written to the audit trail, which means the question “did anyone look at my data?” has a real answer rather than an assurance.

Cookies

The public pages of this site — including this one — set no cookies. Once you sign in, Clerk sets the session cookies that keep you signed in. There are no advertising, analytics, or preference cookies anywhere, so there is no cookie banner to dismiss.

Children

ipLamb is a business tool and is not intended for anyone under 16. We do not knowingly collect their information.

Which laws apply

Canada — PIPEDA

The Personal Information Protection and Electronic Documents Act, the federal statute governing private-sector handling of personal information in Canada. Complaints go to the Office of the Privacy Commissioner of Canada.

EU and EEA — GDPR

Where the GDPR applies, ipLamb is the processor for the business data you load into a workspace and the controller for your own account data. Complaints go to your national supervisory authority.

United Kingdom — UK GDPR

The same rights as above, with complaints going to the Information Commissioner's Office.

California — CCPA/CPRA

ipLamb does not sell personal information and does not share it for cross-context behavioural advertising. There is no such disclosure to opt out of, because none takes place.

India — DPDP Act

The Digital Personal Data Protection Act, 2023. Grievances may be raised with the contact address below, and thereafter with the Data Protection Board of India.

Changes to this policy

If we change something that matters, we will move the date at the top and tell account holders. We will not quietly broaden what we do with your data and rely on you re-reading this page to find out.