Privacy

Record Retention stores the answers you submit through its records check in our database on Cloudflare. The schedule generator and the I-9 calculator run in your browser. We use Cloudflare Web Analytics without cookies. We never sell personal data.

This page covers this website only. It does not cover the business records a company might later propose to license, or the terms of another website’s application process.

What runs in your browser

The schedule generator, the I-9 retention calculator and its batch mode run in your browser. The record groups you tick, the dates you enter and the PDF you download stay on your device. The generator saves your choices in the browser so they are there when you return, and clearing your browser’s site data removes them. The I-9 calculator saves nothing. Its batch list takes an optional employee ID with each date, so use IDs rather than names.

The records check

The records check asks for the company’s full-time headcount category, its status as operating, closing or closed, its main market, and the types of records it holds. We store those answers in our database on Cloudflare and use them for the initial fit result. With each submission we also store the result, the decision page and the first landing path (without its query or fragment), your country (Cloudflare works it out from your IP address), how you reached the site as one broad class such as google, chatgpt or direct, a hash of your IP address that limits repeat submissions, a random lead token, and, for a result saved with JavaScript, a random key that prevents duplicate saves of that result.

The check does not ask for your email address. The check asks for categories of records and does not ask for their contents. Do not include customer details, employee information, passwords or confidential documents.

A result is preliminary. It does not confirm ownership of records, signing authority or acceptance by a buyer. You can read every guide without using the check.

Apply clicks

When you click an Apply button, the click goes through our own apply address and then on to the buyer’s site. We record the time, the site, the page and button the click came from, the partner, your country, whether the visitor looks like a bot, how you reached the site as one broad class, and a hash of your IP address. We also store the first landing path and, when available, the lead token to link the click to its completed check. That record holds no raw IP address, no name and no email address, and it sets no cookies. We use it to see which pages lead to registrations.

The hash is made from your IP address and a random salt that changes every UTC day. The hash is used for abuse controls and submission limits, never as a visitor identifier or to join checks, page views or clicks. Anyone who holds the salt could test an IP address against the hash, so we treat it as personal data.

How long we keep it

We keep each Apply click, and each records check submission, for 90 days from the day it was recorded. After that we add it to a daily total and delete the record. The deletion runs once a day, so a record can stay up to a day past its limit. A click total holds the day, the site, the page, the button, the partner, whether the visitor looks like a bot and the broad class for how you reached the site, plus a count. A records check total holds the day, the site, the page, the result, the headcount, status and market answers and the same broad class, plus a count. Neither holds a country, IP hash, email address, lead token, result key, first landing path or record number.

We clear the IP hash, result key and first landing path from a records check submission after 90 days. We delete each day’s salt, which the click and records check hashes use, when the first click or form of the next UTC day is recorded.

We also count save acknowledgements from the server and save outcomes observed by the page, separately. These counters hold only the day, site, source (server or page), saved or failed outcome and count; they contain no visitor fields and are deleted after 90 days. Deletion-run totals contain no visitor fields and are kept indefinitely. They count attempts, while completed checks are answer submissions; email-only follow-ups are separate. Entry context is added to the internal page link you follow when you interact with it, without cookies or browser storage. An arrival from outside the site starts its own context. The random result key stays in page memory and is sent only with the save; the lead token on the result URL and Apply link refers only to that check.

Cloudflare keeps point-in-time backups of our database, which it calls Time Travel, for the last 30 days. A record we delete can stay in a backup for up to 30 days after we delete it, and so can a day’s salt. See Cloudflare’s Time Travel documentation.

Website analytics

We use Cloudflare Web Analytics to understand website use and page performance. Cloudflare says the service does not use client-side state such as cookies or localStorage to collect usage metrics, and that it does not fingerprint individuals. See its Web Analytics page. Its documentation says the beacon collects metrics using the browser’s Performance API.

Referral links and other websites

Our Apply buttons lead to the buyer’s own application process. What you enter on the buyer’s site is handled under that site’s privacy policy, so read it before you share company details there. Our referral disclosure explains the arrangement. A possible company-data license is a separate transaction that needs its own scope, authority and privacy review.

Next steps

Read about this site for how we check information. Before you submit anything, check that it is limited to what the form asks for.

Contact: Ingenious Digital LLC, (954) 834-3426