Legal

Privacy policy

10Scan LiveScan handles two very different kinds of information: the fingerprints and personal details of applicants printed by the businesses that use it, and the ordinary account and visit data of those businesses and this site. This policy says what we collect, why, how long we keep it, and what we never do with it. It is written to be read, not skimmed.

1. Who we are and who this covers

10Scan LiveScan is operated by TenScan LLC, PO Box 40, Hale, MI 48739, United States. This policy covers the public site at livescan.10scan.com, the operator app under /app, and the 10Scan LiveScan desktop application. It applies to three groups of people: visitors to this site, the businesses that hold an account and their operators ("customers"), and the people whose fingerprints a customer captures ("applicants").

For applicant data, the customer that captured the record decides why it is collected and where it is sent; we process it on that customer's instructions to provide the service. In the language of most privacy laws the customer is the controller and we are the processor or service provider.

2. Applicant data, including biometric data

When a customer fingerprints an applicant, the service holds, for that customer only:

• Fingerprint images (PNG and WSQ), the NFIQ 2 quality score of each impression, and the record of any finger that could not be captured.
• The demographic fields the applicant record requires: name, date of birth, sex, race, height, weight, eye and hair colour, place of birth, citizenship, residence address, and, where the agency requires it, Social Security number and the agency's reference numbers (for example the Arkansas CHCL payment confirmation number).
• The files generated from them: the FD-258 card PDF and the NIST/EBTS (EFT) file.
• The submission record: when it was sent, to which agency, the agency's acknowledgement or rejection, and the operator who captured it.

Fingerprints are biometric identifiers. We collect them only because the customer uses our service to capture them for a lawful applicant purpose (a concealed carry license, employment, licensing or similar screening the agency defines), and we use them only to build the card, the file and the submission the customer asked for and to show the customer the result. The customer is responsible for giving the applicant whatever notice and obtaining whatever consent its state requires before capture; our intake screen leaves room for that step and never hides it.

3. How long we keep applicant data

Applicant data is deleted on a fixed schedule that runs automatically; nobody has to remember to do it.

• Fingerprint images and NIST/EBTS files: 30 days after the agency acknowledges the submission.
• Fingerprint images and files for a record that is never submitted: 90 days after capture.
• FD-258 card PDFs: 90 days after they are generated.
• The submission log (dates, agency, status, operator, transaction number, no images): kept with the customer's account as its audit record, and deleted with the account.

A customer can delete a record earlier from the operator app. When an account closes, every applicant record it holds is deleted within 30 days. Backups that may contain deleted data are overwritten on their own rotation within a further 30 days and are never restored for any purpose other than disaster recovery.

4. What we never do with biometric data

• We do not sell, lease, trade or otherwise profit from fingerprint images, templates or any applicant data. Not to anyone, not in aggregate, not anonymised.
• We do not use applicant data for marketing, analytics, product research or to train any model.
• We do not disclose applicant data to anyone except the agency or channeler the customer directs the submission to, the service providers in section 8 who host and transmit it on our behalf, or where the law compels us (and then we tell the customer unless the law forbids it).
• We do not build or keep a database of fingerprints that can be searched across customers. Every record belongs to one customer account and is invisible to every other.

5. Account and operator data

To run an account we hold the business name and address, the owner's and each operator's name, username, email and phone, the names of locations and stations, machine identifiers of paired station PCs, and the usual login records (times, IP addresses, success or failure). We use these to provide the service, send invoices and service emails, answer support requests, and keep accounts secure. We keep them while the account is open and for as long afterwards as tax and accounting rules require for billing records.

6. Payments

Card numbers never touch our servers. When a customer adds a card, the card details go from the browser straight to our payment processor, Authorize.Net, which stores them and gives us a token. We keep the token, the card's last four digits and expiry, and the invoice history. State and agency fees are paid to the agency and never pass through us.

7. Visits to this site and cookies

The public pages set no advertising or analytics cookies and load no third-party trackers. Our web server keeps ordinary access logs (IP address, browser, page, time) for a short period to keep the site secure and working. The operator app sets only the cookies it needs: one to keep an operator signed in and one to protect forms against forgery. The fonts on this site are loaded from Google Fonts, which receives the request for the font file.

8. Service providers and agencies

These are the only parties that handle customer or applicant data on our behalf, each under a written agreement and only for the purpose named:

• Our hosting provider, on servers we administer, for storage and transmission.
• Authorize.Net (Visa), for card storage and charges.
• Postmark, for invoice and account emails (never fingerprint images).
• The state agency or FBI channeler the customer submits a record to, under that agency's own rules; once a submission is received, the agency's retention and use of it is governed by the agency, not by us.

9. Security

Everything travels over TLS. Fingerprint images and files are encrypted at rest with keys we hold separately from the data, and are served only through signed links that expire. Each customer's data is isolated at the database layer so that a request from one account cannot read another's. Staff access to customer data happens only to answer a support request or to keep the service running, is limited to the people who need it, and is logged. Submissions to agencies use the credentials and secure channel the agency issues to us.

10. Your choices and rights

If you are an applicant and want to know what a business holds about you, or want it deleted, contact the business that fingerprinted you: it controls the record and can delete it from the app at once. If you contact us instead, we will point you to that business and help it respond. Some states give you specific rights over biometric data; we support the customer in honouring them and never stand in the way.

If you are a customer, you can see, correct and delete your account data and your applicant records from the operator app, and you can close the account at any time. Email us for anything the app does not cover.

11. Children

The service is for businesses, and we do not knowingly collect information from anyone under 13 through this site. A customer may fingerprint a minor only where the agency's program allows it and with the consent that program requires.

12. Changes to this policy

When this policy changes we post the new version here with a new effective date, and we email account owners before a change that affects applicant data or retention takes effect.

13. Governing law and contact

This policy and our handling of data are governed by the laws of the State of Michigan and applicable United States federal law. Questions, requests and complaints go to support@10scan.com, (989) 312-3369, or TenScan LLC, PO Box 40, Hale, MI 48739.