Terms of service

1. What this service is

Resolens builds business data to order. You describe what you need in plain English; we compile that into a specification and price it, and if you agree to the price, we run it and deliver data about companies and the people behind them, together with a certificate or receipt describing what we delivered and what we could not.

This is a business-to-business service. It is offered for business use, to organisations, and it is not a consumer product.

What runs today. You can ask for, and receive:

• Contact lists: companies and the people at them, one row per person.
• Company records: what we hold on one company you name, section by section, each fact dated where its record has a date.
• Ownership maps: who is behind a business, from its own filings, and the other businesses tied to it.
• Screenings: a list of businesses you bring, with whether we found each one, its standing, and the latest thing filed against it.
• Named-person lookups: the businesses a named person is behind, for a business purpose only, or whether we can reach one named person at work (section 5).

Standing watches can be quoted and set up, but their subscription and per-alert prices are not set yet, and the quote says so. We do not charge for work that does not run.

2. Pricing, and what is metered

Quoting is free. Counting, estimating and pricing an ask are never billed and never paywalled, so an ask you decide against costs you nothing. Only delivery is a product.

The meter is the delivered row. Attempts, searches, verification probes and misses are our cost, not your line item. A row we could not get is not a row you pay for.

• Misses are never billed. You are charged for what we delivered, at the per-row rate shown on your account page, and for nothing else.
• A blocked delivery ships zero rows and bills zero. Our audit step can refuse a whole delivery that fails our quality bar. When it does, you receive no rows and you are charged nothing.
• One ask, one charge. A re-run against the same job cannot bill you twice; the charge is recorded once per job and repeating it is refused by our systems, not by our diligence.
• The price is bound to the ask before anything runs. A run cannot start without a quote you have already seen, and starting one requires repeating the exact price that quote returned. If the numbers do not match, the run is refused. The quote holds the ask as we compiled it, so what runs is what was priced. A later quote cannot change an earlier one, however similar the wording.

Balances are held per workspace and charged when a run delivers. A balance may go negative: this is a normal, visible state, shown on your account page, and it means work has been delivered that has not yet been paid for. We will contact you about it; we will not hide it.

3. Where the data comes from

Our data is assembled from public records, publicly published web pages, and data licensed from partners we buy from. Coverage is focused on the United States.

We do not claim that every byte behind an answer is ours. Some sources are partners; where that is true, it is true, and telling you otherwise would be the first thing here you could catch us on.

Every row says where it came from. On the contact list that is a source in plain words on every row: our records with the date a fresh listing confirmed them, our records that this run could not re-check (the row says so), or this run's own web search with the date it was found. If we cannot say where something came from, we do not ship it.

The word "verified"

We use "verified" in one sense only: an email address that has been checked against the receiving mail server and carries a dated verdict. A contact attributed to a named person is a named-person contact, a different and weaker claim, and we do not apply the word "verified" to it. We hold that distinction in our own code, not just in this paragraph.

4. What you may do with what we deliver

You may use delivered data for your own business purposes, including research and outreach, subject to the laws that apply to you. You are responsible for your own use of it: we do not send messages on your behalf, and we cannot know what your outreach says or whether you have a lawful basis for it where you operate.

You may not resell or redistribute delivered data as a data product of your own, and you may not use it to build a competing corpus.

You must honour suppression and deletion requests that reach you about individuals in data we delivered, and you must stop contacting anyone who asks you to. If a request reaches us instead, we will act on it on our side and, where we can identify the delivery, tell you that we have.

5. Refusals are a legitimate outcome

Some asks we will not run. A question about a named individual compiles honestly and is never silently rewritten into a question about a company. A question about what a named person is behind runs only for a business purpose, and only under these rules:

• You state the purpose. Before a lookup about a person runs, you confirm it is for a business purpose and not for credit, employment, insurance, housing or tenant screening. Without that confirmation the run is refused and nothing is charged.
• Suppression is honoured. A person who has asked, through our do-not-contact form, not to be looked up is never answered about by that name, however it is written: in any order, with or without accents, and with or without a middle name or middle initial. A request that gives a state covers the name in that state. The refusal reads the same whatever the reason.
• Every lookup is logged. Who asked, the name, the place and when are recorded before the lookup is made. A lookup we cannot record is not made.
• Strangers are never merged. Other people with the same name are counted, never named and never billed.

An ask to reach one named person at work reads the same do-not-contact list, and a person on it is never looked up. We would rather refuse an ask than answer it in a way we cannot stand behind.

An ask we cannot price says which part of it we could not price. An ask for something we do not run yet says so. Neither is billed.

6. What we do not promise

This section exists because the things a data vendor is tempted to claim are the things a customer is least able to check.

• We do not promise completeness. "89 delivered of 1,000 requested" is a normal and honest answer here. Your certificate states requested against delivered, the audited sample and its verdicts, and where our gate recorded them, the reasons the rest did not ship. Read it before treating a result as complete.
• We do not promise that any particular fact is current. A row carries the date we checked it where we did; a row we could not re-check says so, with the date on our record when there is one. Data about businesses goes stale; the dates are there so you can judge it rather than assume.
• We do not hold a SOC 2, ISO 27001 or any other security certification, and we will not imply one. Delivered files are stored in private, encrypted object storage, and downloads are served either through our authenticated API or as short-lived links that expire. That is a description of what we do, not a certification.
• We do not promise uptime. There is no service level agreement attached to these terms. Batch work is deferred by design and does not block.

7. Accounts, keys and access

Access is per workspace. API keys are issued to a workspace, are shown to you once at creation, and are stored by us only as an irreversible hash: we cannot show you a key again and we cannot recover one for you. Treat a key as a password: anything holding it can spend your balance.

You can revoke a key at any time from your account page. Revocation takes effect on the very next request. If you believe a key has been exposed, revoke it and create another; tell us and we will help you work out what it was used for.

8. Ending the relationship

You can stop using the service at any time. Charges already incurred for delivered rows remain payable; work not yet run is not charged. We can decline or stop serving an account for non-payment, for use that breaks section 4, or for asks we are not willing to run, and we will say which.

Ask us to delete your account data and we will, subject to the records we are required to keep for accounting. See the privacy page.

9. Liability, plainly

We provide this service as described on this page and make no other warranties. Our total liability to you for any claim is limited to the amount you paid us for the delivery the claim concerns.

Data is evidence, not certainty. Decisions you make from it (who to contact, who to lend to, who to hire) are yours.

10. Governing law and changes

These terms are governed by the laws of the United States and of the state in which we are incorporated. The specific jurisdiction is named in the final version of this document; it is deliberately not guessed at here.

If we change these terms materially we will say so and date the change. This draft carries no effective date because it has not been adopted.

Questions about billing, key rotation, data removal or permissible purpose are for a human. Contact us at support@supersoniq.co, or use the do-not-contact form if you want us to stop holding or using an address.