Privacy Policy

We store the email you enter, the answers you type into the checklist, the order record, and the delivery record. The answers include the state, an optional file number, and a due date where the state requires one.

The order record includes the plan, the amount, the currency, the status, and the timestamps. It is used to deliver the product, to answer support questions, and to keep accounting records.

We do not store a card number. We do not store a phone number because the site does not ask for one.

We keep a record of the emails we send and the delivery result so support can tell whether a checklist left the system. That record includes the address, the message type, and a timestamp. It does not include the content of a reminder beyond the state and the date. The record is kept for support and accounting, not for marketing.

We use a first-party attribution cookie that lasts one year to see which page referred a purchase. It records the visitor id, the first referrer, the first landing page, and a campaign source if one is present.

The account session cookie is HTTP-only, secure, and same-site. It is set after a successful 6-digit code check at checkout and expires 30 minutes later.

We do not use advertising cookies and we do not run cross-site tracking. If you clear your browser cookies, the attribution record stops updating for that browser.

The attribution record is a first-party record. It tells us which page introduced a visitor and which campaign, if any, brought them. It is not used to build a profile of sites visited elsewhere, and it is not shared with an ad network.

Card numbers are handled directly by our card payment processor. The card details go to the processor, not to this site. We receive the result of the payment and the order reference, not the card.

The processor may require its own fraud checks. Those checks are governed by the processor policy. We do not add a card form to this site and we do not keep a card vault.

If a payment fails, we may see a failure reason from the processor. We do not see the full card number in that message.

Transactional emails and scheduled reminders are sent from support@llcdeadline.com. Each reminder carries a one-click unsubscribe link, and the link stops future reminder emails for that schedule.

We do not add a buyer to a marketing list. The reminder emails are part of the yearly plan, not a separate newsletter.

If a message hard-bounces or the address asks to stop, we suppress the address so we do not keep sending. A suppression does not delete the payment record.

Email support@llcdeadline.com to delete your reminder schedule or your account profile. We complete deletion within 7 days while retaining required payment accounting records.

You can stop reminder emails yourself with the unsubscribe link in any reminder, or by emailing support@llcdeadline.com. Stopping emails does not cancel a charge that already happened.

You can ask what we store about your order. We answer from the same address used for support.

Deleting an account profile does not cancel a yearly plan that is still active. Email support@llcdeadline.com to cancel the plan first if you want both the deletion and the end of future charges. We tell you in the reply which of the two actions has been completed.

Checkout confirms your address with a 6-digit code sent to the email you enter. The code expires five minutes after it is sent. One request is allowed per minute and three per hour; a fourth request inside the hour is refused, and five wrong entries retire the code. When a code is accepted, the challenge is deleted rather than left on file.

The code is not stored in readable form. We keep a hash of it alongside a server-side secret, so a copy of the database alone does not produce a working code. A correct code creates a session that lasts 30 minutes. The session is carried in an HTTP-only, secure, same-site cookie and is used only to show the address on the account page. It is not a password, it is not a membership, and it does not unlock a PDF, because the PDF is not stored in the account.

The order record is kept for accounting: the plan, the amount, the currency, the state, the stored date, and the timestamps. The delivery record is kept so support can answer whether a message left the system, and it holds the address, the message type, and a timestamp. The attribution cookie lasts one year. A session lasts 30 minutes. A code challenge is deleted when it is used.

A deletion request removes the reminder schedule or the account profile within 7 days, and the payment record that accounting requires stays. Support messages are kept while the question is open and are not added to a marketing list. If a message contained a detail you did not mean to send, ask for it to be deleted and the reply will confirm the deletion.

Three roles touch order data. The payment processor takes the card details and returns a result and an order reference; we never receive the card number. The email service on the hosting platform sends from support@llcdeadline.com and receives the address, the subject, the text, and the attachment for each message. The hosting platform runs the site and stores the order and session rows in its database.

None of those roles buys data. There is no advertising network, no cross-site tracker, and no lead broker in the list, and the checkout form has no phone field to fill. If you ask which categories of provider received data for your order, the reply names them.

We share what is necessary with the payment processor to take a payment, and with the email provider to deliver a message. We do not sell or rent data to a contractor, a lead broker, or an advertiser. We also do not ask for a phone number, and the checkout form has no field for one.

The site is intended for adults. You must be 18 or older to purchase. We do not knowingly collect data from a child.

If you believe a child has submitted data, email support@llcdeadline.com and we will delete it.

The email provider and the payment processor are service providers, not data buyers. They receive what they need to send a message or take a payment, and their own terms govern that processing. We do not add a fourth party for advertising or analytics beyond the first-party attribution record.

A visitor who only reads a state page still receives the one-year attribution cookie if the browser accepts it. That cookie records a first-touch identifier. It does not record the state fee, the form name, or the text of the page. Buying a plan adds the order fields described above. Reading does not. You can refuse cookies in the browser, and the free pages still load. The paid checkout needs the email you type, not the cookie.

No data is sold, and no checklist answer is used to train a model that we sell or license to anyone. You can also ask which service providers received data for your order, and we will name the categories in the reply.