This addendum explains how UCCdata.ai (“UCCdata,” “we,” “us”) handles personal data. It is read with the Terms of Use and the Privacy Policy. It adds no warranty. The liability limits in the Terms apply to everything in this addendum. It is not legal advice for your outreach, and it is not a certification.
1. Two kinds of data
Account data is what you give us about yourself as a customer: name, work email, company, and the details of an order or a sample request.
Dataset data is business contact information in the files we compile and license: for example a work email or a mobile number, with the company and filing details we attach to it.
2. Roles
Account data. We decide why we keep it: to take an order, deliver a file, keep the export history an account needs, prevent fraud, and answer you. For that data we are the controller. Under US state privacy laws that use the word, we are the business. Payment, hosting, and email vendors process it for us.
Dataset data. While a contact sits in our database, we are an independent controller of it. We decide to collect it, compile it, and license it. From the moment we deliver a file, you are an independent controller of your copy. You decide whether to email, call, or text anyone in it. We do not send those communications for you.
We are not your processor, your service provider, or a joint controller for your use of a delivered file. You will not describe us that way to a person you contact, to a vendor, or to a regulator.
A file you send us. We do not run a standing service on lists you upload. If we agree in writing to look at data you send for a specific request, we do only that task, and we may refuse it. That agreement does not make us your processor for our database, and it does not make us responsible for what you do with a file after we deliver it.
3. Why we hold dataset data
We compile business contact details from public business filings, including UCC filings, and from our own research. The purpose is to license that compilation for a customer’s internal sales, marketing, and analytics.
Where a privacy law asks us for a legal basis, the basis we rely on for our own database is our legitimate interest in building and licensing business contact data for business-to-business use. That is a statement about our database. It is not a statement that your campaign has a lawful basis, and it is not a statement that any person consented to be called, texted, or emailed by you.
We do not obtain consent from each person for your outreach, and we do not claim that we have it.
We may use automated means to match, research, and check business contacts. That work does not decide anyone’s eligibility for credit, insurance, employment, housing, or a similar outcome. A dataset is not a consumer report.
4. What you take on
From delivery, your copy is yours to use and yours to answer for. You are responsible for your own legal basis, notices, and any consent a law requires before you call, text, or email. You are responsible for do-not-call rules, the TCPA, CAN-SPAM, and the other outreach rules named in the Terms. Buying a dataset is your agreement to act in good faith.
If a person asks you to stop, that request is yours to honor. We do not monitor your use of a file, and we are not responsible for it.
You assess for yourself whether a file may be used in the places you use it, including any rule on moving personal data across borders after you download it.
5. How we prepare contacts
We work to keep the dataset to business contacts and to check them before a file goes out. We try to screen mobile numbers against TCPA litigator lists that are publicly available. Those lists are not complete. Not every risk is public. Do-not-call and similar risks remain. Occasional errors are normal for this kind of product.
None of this promises that a contact is accurate, current, consented, or appropriate for you to use. Screening does not move your outreach responsibility onto us. Quality and any replacement or refund are governed by the Terms.
6. People in the dataset
A person or a business in our enrichment may ask to be left out of future files. The request goes to hello@uccdata.ai and should include:
- Full name
- Company name
- State, if known
- The email and/or mobile number to suppress
- A short note that this is a removal request
We review it. If we accept it, we suppress the contact we match from future datasets. We decide what matches. We do not promise how long the review takes. We do not recall a file already delivered. We cannot remove a filing from a state’s public index. A backup or an older copy may persist for a limited operational period.
A complaint about your email, call, or text is for you to handle. If it reaches us, we may tell the person to contact you, and we may also suppress the contact from future datasets. We do not take over your reply.
Where a law gives a person a right in respect of our database, they write to us, and we handle that request for our database. We do not handle rights requests about your copy.
7. Account data
We use account data to run the account, deliver files, keep export history, take payment, and respond to you. We do not license your account identity as a contact in the datasets we sell.
You may ask us to access, correct, or delete account data we hold about you as a customer, at hello@uccdata.ai. We may refuse or narrow a request where the law allows, and we may keep what we need for delivery records, accounting, fraud, and disputes. If we delete the export history on an account, later deduplication has no history to use. The Terms describe that limit.
8. Vendors
We use vendors to host the service, send email, take payment, and check contacts. For account data, and for checks we commission on our database, they act for us. We choose them. We may add or replace them without notice to you.
You have no right to approve those vendors, to object to a change, or to audit our systems or theirs. This addendum does not create the rights a customer has under a processor agreement.
9. Where we process
We operate from the United States, and we process personal data there. This addendum does not itself transfer personal data under the EU standard contractual clauses, the UK addendum, or a data-privacy framework certification. We do not claim those mechanisms on this page. A separate written agreement is required before any of them applies.
10. Security and incidents
We use reasonable technical and organizational measures to protect the site and account data. This addendum states no certification.
If we confirm that someone gained unauthorized access to your account data, we notify you where the law requires that notice. A notice is not an admission of fault. Beyond what the law requires of us for our own database, we do not promise a particular notice to you about dataset data.
11. How long we keep it
We keep account and order records for as long as we need them for delivery, export history, accounting, and disputes. We keep a dataset contact while it remains in the product. Suppression stops that contact from going into future deliveries. It does not require us to erase every historical copy at once.
12. Responsibility
Each of us answers for our own role. We are not responsible for your outreach, or for a claim that a person should not have been contacted by you. Your indemnity in the Terms covers that use. Nothing in this addendum raises the cap on our liability or adds a remedy the Terms do not already give.
13. Changes and contact
We post updates on this page. We have no duty to notify you of a change, and no duty to keep or provide an earlier version.
hello@uccdata.ai · Wilmington, DE.