• Product
    U.S. Pay Run Owner Payroll Year-end and quarterly forms Paying contractors
  • Solutions
    S corporation owners Small employers Seasonal and occasional payroll Bookkeepers and accountants
  • Pricing
  • U.S. States
  • Canada 🇨🇦
    Canada Payroll Pay RunUp to 5 employees · Canadian statements and employer records Province & Territory Rules 2026 Canada Pay Statement Database Bonus & Final Pay
  • Resources
    Payroll Calculators FAQ Pay Stub Checker About LeoFolio Research Methodology Independent Reviews 2026 Wage Statement Database Contact Us
My PayrollStart a Pay Run
My PayrollPricing
Product
U.S. Pay Run Owner Payroll Year-end and quarterly forms Paying contractors
Solutions
S corporation owners Small employers Seasonal and occasional payroll Bookkeepers and accountants
U.S. States
All U.S. States 2026 Wage Statement Database
Canada 🇨🇦
Canada Payroll Pay Run Province & Territory Rules 2026 Canada Pay Statement Database Bonus & Final Pay
Resources
Payroll Calculators FAQ Pay Stub Checker About LeoFolio Research Methodology Independent Reviews 2026 Wage Statement Database Contact Us
Start a Pay Run

Legal

Privacy Policy

Last updated: October 21, 2026

Payroll Data Access & Privacy Disclaimer

LeoFolio is designed so that LeoFolio personnel cannot—and will not—view, retrieve, or browse your employer or employee payroll data through the current LeoFolio system.

Payroll information you enter into a Pay Run may include employer information, employee information, compensation, hours worked, deductions, withholding elections, payroll history, and calculated payroll amounts. LeoFolio uses this information only as necessary to perform supported payroll calculations, validations, record generation, and related Pay Run functions.

Your payroll records are not stored in a LeoFolio staff-accessible payroll database

LeoFolio does not currently maintain an administrative payroll database, customer payroll dashboard, employee-record repository, or other operator-facing system through which LeoFolio personnel can retrieve and inspect your employer or employee payroll information.

LeoFolio personnel therefore cannot use an internal LeoFolio dashboard to look up an employee's name, address, hourly rate, salary, hours worked, withholding elections, deductions, year-to-date payroll amounts, calculated taxes, gross pay, net pay, or previously saved Pay Runs.

LeoFolio will not intentionally create staff access to employer or employee payroll data for browsing, profiling, marketing, sale, advertising, or unrelated business purposes.

Browser storage and Pay Run processing are different things

Pay Run drafts and saved Pay Run records may be stored locally in the user's browser. Those browser-stored records are not automatically synchronized to a LeoFolio customer account or payroll-record database.

LeoFolio cannot remotely browse the collection of Pay Runs stored in a user's browser.

However, when a user performs an operation that requires LeoFolio's payroll processing services, the active Pay Run may be transmitted to LeoFolio's automated backend systems for the limited purpose of completing that requested operation. This may occur, for example, when performing supported payroll calculations, validations, record generation, checkout preparation, verification, or related Pay Run functions.

Accordingly, LeoFolio does not represent that payroll information “never leaves your browser.”

The distinction is important: LeoFolio's automated systems may process an active Pay Run, but LeoFolio personnel do not have a staff-accessible repository through which that payroll information can later be browsed or retrieved.

No intentional payroll-data logging or staff review

Under the current implementation, LeoFolio does not intentionally write complete U.S. or Canada Pay Run payloads into application logs for staff review.

LeoFolio does not intentionally retain employer or employee payroll details in application logs, administrative dashboards, or a persistent LeoFolio payroll-record database.

Ordinary application and infrastructure logs may nevertheless contain technical information associated with use of the service, such as request times, routes, response status information, error information, IP or network-related information, browser/device information, and similar operational metadata.

LeoFolio does not treat such technical information as an employee payroll record.

Payment information is handled separately

Payment processing is provided through Stripe.

LeoFolio may have access through Stripe to information associated with a payment or customer transaction, such as the customer's email address, transaction amount, transaction status, date, product purchased, customer information collected by Stripe, and limited payment-method information made available by Stripe.

LeoFolio does not receive full payment-card numbers or card security codes from Stripe.

Detailed employer and employee payroll information is not intentionally supplied to Stripe as ordinary LeoFolio checkout metadata. LeoFolio may provide Stripe with non-payroll transaction identifiers or technical values associated with a Pay Run, such as a product identifier, transaction reference, cryptographic digest, or similar checkout-verification information.

Hosting and infrastructure providers

LeoFolio relies on third-party infrastructure providers to operate the service, including hosting and payment-processing providers.

Because an active Pay Run may pass through hosting infrastructure when the user requests server-side processing, those infrastructure systems necessarily participate in the technical transmission and processing of the request.

This does not mean LeoFolio personnel have a payroll database available for inspection.

Third-party infrastructure providers may process technical request information according to their own security, infrastructure, logging, and data-processing practices. LeoFolio cannot truthfully represent that no infrastructure provider ever technically handles data transmitted through the service.

Analytics and advertising access

The current LeoFolio Pay Run interfaces are designed without third-party advertising or behavioral-analytics scripts embedded in the payroll-entry experience that intentionally receive employer or employee payroll fields.

LeoFolio does not intentionally transmit employee wages, deductions, withholding elections, payroll history, or other Pay Run financial details to advertising networks for profiling or targeted advertising.

This statement describes the current LeoFolio implementation and should be updated if the application's third-party script configuration materially changes.

Sensitive identifiers

Users should not enter information that a LeoFolio workflow does not request.

In particular, users should not enter Canadian Social Insurance Numbers, bank-account numbers, routing numbers, direct-deposit credentials, passwords, or other unnecessary highly sensitive credentials into free-text fields or other portions of a Pay Run.

LeoFolio's payroll workflows are not intended to function as a repository for those credentials.

What LeoFolio does not do with payroll data

LeoFolio does not sell employer or employee payroll information.

LeoFolio does not intentionally use employer or employee payroll information for advertising profiles.

LeoFolio does not provide LeoFolio personnel with a customer payroll dashboard containing employees' wages, deductions, withholding elections, or payroll history.

LeoFolio does not currently maintain a persistent payroll database from which LeoFolio personnel can retrieve a customer's historical Pay Runs.

LeoFolio does not use the Pay Run workflow to move employee wages, access employee bank accounts, initiate direct deposits, remit payroll taxes, or file payroll tax returns unless a particular service expressly states otherwise.

Payroll calculations and records

LeoFolio is a payroll-preparation and records platform.

LeoFolio prepares supported calculations and records based on information supplied by the user. Users remain responsible for reviewing the information they enter and the resulting calculations and records before relying on them.

LeoFolio does not independently know whether employer or employee information entered by a user is complete, accurate, current, or legally sufficient.

A generated payroll record should not be interpreted as proof that wages have been paid, taxes have been remitted, a payroll return has been filed, or a government obligation has been satisfied.

Your responsibility for devices and downloaded records

Payroll records stored in a user's browser, exported from LeoFolio, downloaded as files, printed, emailed by the user, backed up by the user, or otherwise transferred outside LeoFolio are under the user's control.

Users are responsible for protecting devices, browser profiles, downloaded files, backups, email accounts, shared computers, and other locations where payroll information may be stored after creation.

Clearing browser data, changing devices, using private-browsing modes, reinstalling software, or other local actions may remove locally stored Pay Run information where no separate user backup exists.

Security limitations

LeoFolio is designed to minimize unnecessary access to payroll information, but no website, browser, hosting system, network connection, or computer system can be represented as absolutely immune from unauthorized access, software defects, malware, compromised devices, infrastructure failures, or security incidents.

The statement that LeoFolio personnel cannot access payroll records through the current LeoFolio system does not constitute a guarantee that unauthorized access is technologically impossible under every conceivable circumstance.

It describes the intentional architecture and normal operating model of the service.

Future architectural changes

This description applies to LeoFolio's current Pay Run architecture.

If LeoFolio later introduces features such as cloud payroll storage, user accounts containing payroll history, employer dashboards, employee portals, payroll synchronization, persistent server-side payroll records, or staff-assisted payroll support requiring access to payroll data, the applicable privacy disclosures should be updated before those features are used to collect or retain such information.

LeoFolio will not silently treat a future architecture that provides staff access to stored payroll records as equivalent to the current architecture.

Plain-language summary

Your Pay Run data is yours.

LeoFolio's automated systems may temporarily process the active payroll information necessary to perform the Pay Run functions you request. However, under LeoFolio's current architecture, your employer and employee payroll records are not stored in a LeoFolio staff-accessible payroll database, and LeoFolio personnel cannot—and will not—browse or retrieve your employees' financial information through an internal LeoFolio system.

LeoFolio may have access to payment and customer information supplied through Stripe and to ordinary technical information generated in operating the website and its infrastructure. That is separate from having access to a database of your employer and employee payroll records.

Information We Collect

When you use our Service, we collect:

  • Information you provide: Name, address, employer details, income figures, and other data you enter into our document generator forms.
  • Payment information: Processed securely by Stripe. We never see or store your full card number. We receive only the last 4 digits and card brand for reference.
  • Email address: Used to deliver purchased documents, respond to support requests, and — only when you opt in — send occasional LeoFolio updates, discounts, and product announcements.
  • Support chat information: If you use live chat, we may receive the messages you send, contact details you provide, and basic technical information needed to provide support.
  • Usage and security data: Standard server logs such as IP address, browser type, pages visited, and timestamps. For abuse prevention on the free generator, we also process limited pseudonymous security identifiers and an opaque first-party browser identifier. These security identifiers are used to enforce rate limits and detect automated or repeated abuse without storing the underlying email address or IP address in the security event log.

How We Use Your Information

  • To generate and deliver the document you requested or purchased
  • To send your document via email after payment
  • To respond to questions through live chat or other support channels
  • To process your payment through Stripe
  • To improve our Service, troubleshoot issues, and understand aggregate site usage through Google Analytics
  • To protect the free generator from automated abuse, apply usage limits, validate security challenges, and investigate service-integrity issues
  • To send optional marketing emails only when you affirmatively opt in. You may unsubscribe or request removal at any time.
  • To comply with legal obligations

Data Retention

Form data entered during document generation is stored only as needed to generate and deliver your document. Paid checkout payloads may be stored temporarily in secure server-side storage for document delivery. Lead records from our former complimentary statement tool, which no longer accepts submissions, may retain an email address, submission source, consent status, and timestamp so we can document past delivery and marketing consent. We do not maintain a permanent database of your detailed payroll, employment, or tax form entries. Generated PDF files are not stored long-term on our servers.

Third-Party Services

Optional review invitations: After a document email is delivered, we may send one follow-up asking for honest feedback about LeoFolio. These requests do not contain your document or financial details. We use Resend delivery notifications and limited records in Upstash Redis (recipient email, delivery reference, scheduling status, and an opaque unsubscribe token) to prevent duplicate invitations and honor opt-outs. These invitation records expire after 90 days. A hashed email suppression preference is retained to prevent future invitations. Use the unsubscribe link in a follow-up email or contact support to stop review invitations; this does not stop document delivery.

  • Stripe: Handles all payment processing. See Stripe's Privacy Policy.
  • Resend: Used for transactional email delivery. See Resend's Privacy Policy.
  • Trustpilot: Our reviews page embeds Trustpilot's Review Collector and links to our public profile. Loading the widget sends standard browser connection information to Trustpilot. If you choose to write a review, you submit it directly to Trustpilot under its policies. We do not send your document, payroll information, or customer email list to Trustpilot. See Trustpilot's Privacy Policy.
  • Vercel: Hosts our platform. See Vercel's Privacy Policy.
  • Upstash Redis: Used for short-lived checkout payload storage, lead and consent records from our former complimentary statement tool, rate limiting, and usage quotas.
  • Cloudflare Turnstile: Used on the free generator to distinguish legitimate submissions from automated abuse. Turnstile processes technical request information needed to provide the security challenge.
  • Google Analytics: Used to measure aggregate website traffic, page usage, and performance so we can improve the Service.
  • tawk.to: Used to provide live chat support on selected pages. Live chat may process messages you submit and basic device/browser information needed to operate the chat widget.

Cookies

We use essential cookies and similar technologies needed for site functionality, checkout, security, and document delivery. The free generator may set an opaque first-party browser identifier used only for abuse prevention and usage-limit enforcement. We also use Google Analytics to understand aggregate website usage and tawk.to to provide live chat support on selected pages. Google Analytics may set analytics cookies such as _ga to distinguish visits and measure site activity, and tawk.to may use cookies or similar technologies to keep chat sessions available across pages. We do not use Google Analytics or live chat tools to process payments or create documents, and we do not sell personal information.

Your Rights

You may request deletion of personal data we hold, including free paystub lead records and marketing consent records, by emailing support@leofolio.com. Requests are processed within 30 days.

Contact

Privacy questions: support@leofolio.com

10630 Little Patuxent Pkwy
Columbia, MD 21044
United States
On this page
Payroll Data Access & Privacy Information We Collect How We Use Your Information Data Retention Third-Party Services Cookies Your Rights Contact
Home Payroll Blog FAQ
LeoFolio

Payroll without the subscription. Prepare a pay run for up to five employees, review every figure, and pay only when you complete it.

Contact support
10630 Little Patuxent Pkwy
Columbia, MD 21044
United States

Start a Pay Run
Product
  • U.S. Pay Run
  • Canada Pay Run
  • Owner Payroll
  • Pricing
  • My Payroll
  • Paying contractors
Solutions
  • Small employers
  • Seasonal payroll
  • S corporation owners
  • Bookkeepers and accountants
  • Employers in Canada
Free tools
  • Payroll calculators
  • Pay stub checker
  • Employer cost calculator
  • Embeddable tools
Research
  • State payroll guides
  • Canada province guides
  • 2026 Wage Statement Database
  • 2026 Canada Pay Statement Database
  • How we calculate
  • Calculation changelog
Company
  • About LeoFolio
  • Blog and guides
  • Customer reviews
  • Editorial standards
  • Corrections
  • Contact us
Popular statesCaliforniaTexasNew YorkFloridaAll 50 states
CanadaCanada payroll hubOntarioQuebecBritish Columbia
LegalTermsPrivacyRefundsAccessibilitySecurityDisclaimer

© 2026 LeoFolio. All rights reserved.

Secure checkout by Stripe. No subscription, no account.

LeoFolio prepares payroll calculations and records from the information employers enter. It does not pay wages, remit payroll taxes or file returns, and it is not a substitute for professional tax or legal advice. Employers are responsible for the accuracy of their inputs and for meeting their own payroll obligations.