ATROVIA Policies

Add-on & Marketplace Terms

Effective 13 September 2026 · Version 2026-09-13

The App Store offers two different things, and the difference matters. Some add-ons are built by Atrovia. Others connect you to a third-party service that bills you separately and sets its own rules. This page explains which is which, and who is responsible when something goes wrong.

The short version

Atrovia add-ons — Operations, Finance, Studio and anything else marked as ours. Covered by your Agreement, billed by us, supported by us.

Third-party add-ons — packs that include an outside provider, such as the Real Estate Pack with BatchData and iSpeedToLead. You hold the account with that provider, they bill you directly, their terms govern their service, and refunds for their data or leads come from them under their policies.

1. The two kinds of add-on

Every add-on in the App Store shows what it includes. Where an outside provider is involved, it is named on the card before you buy, along with the fact that it bills separately. We would rather lose a sale than have you discover a second invoice afterwards.

2. Atrovia add-ons

Built and run by us. Your End User License Agreement, Privacy Policy and AI Disclosure apply exactly as they do to the rest of the platform. Billed on your Atrovia invoice, cancellable at any time, effective at the next renewal, per the Credits & Billing Terms.

3. Third-party add-ons

A third-party add-on wires an outside service into Atrovia so you can work in one place. What it does not do is make us the provider of that service.

The Atrovia fee shown for a third-party add-on, where there is one, is for the integration — the connection, the interface and the work of bringing that provider's data into your pipeline. It is not payment for the provider's data or leads.

4. How third-party billing works

ChargeBilled byAppears on
The add-on's monthly Atrovia feeAtroviaYour Atrovia invoice
Skip traces, list pulls, record lookupsThe data provider Your account with them
Each lead you buyThe lead providerYour account with them

What you pay a third-party provider depends on how much you use. These are usage-based services — skip traces, list pulls and per-lead purchases add up quickly, and the amount is set by them, not by us. Set a spending limit with the provider directly if they offer one.

We don't see, control or take a share of what you spend with them unless the App Store card says otherwise for that specific add-on.

5. Data quality, leads and refunds

Refunds for inaccurate data or bad leads are handled by the provider, under their own policies. Not by Atrovia. If a skip trace returns a wrong number or a purchased lead turns out to be junk, that claim goes to the company that sold it to you, and their refund policy decides the outcome.

We'll help you work out who to contact and what to send them. We can't overrule their decision.

No provider guarantees that a record is current or correct. People move, disconnect numbers and change names. Treat purchased data as a starting point to verify, not a fact. That is true of the best providers in the industry, and any vendor claiming otherwise is selling you something they can't deliver.

6. What purchased data may not be used for

The FCRA line

Property records, owner records and skip-traced contact data are marketing data. They are not consumer reports, and the providers are not consumer reporting agencies.

You may not use this data — or anything Atrovia produces from it — to decide whether to grant someone credit, employment, insurance, housing or tenancy, or for any other purpose covered by the Fair Credit Reporting Act.

This is not a formality. Using marketing data for a screening decision is an FCRA violation regardless of what the data cost or how accurate it turned out to be.

Contact data obtained through an add-on is also not consent to be texted or called. Everything in the Acceptable Use Policy still applies — consent, do-not-call scrubbing, opt-out, and the 8am–9pm window. A number you bought is a number, not a permission.

7. Data sharing when you enable an add-on

Enabling a third-party add-on authorises us to exchange data with that provider as the feature requires — for example, sending a property address to get back an owner record, or receiving a lead into your pipeline.

8. Turning an add-on off

9. Availability, previews and "Soon"

Everything else in your End User License Agreement applies to add-ons, including the disclaimers and the limitation of liability in sections 16 and 17.