Privacy Policy

Idaho Pro Digital, LLC operates litecommerce. This policy explains how we handle personal information when you visit our websites, contact us, request access, or use the platform as a merchant, staff member, or developer. It also explains our role when we provide checkout and customer-account services for a merchant through litecheckout.

We act as the controller for information we use for our own business, such as responding to inquiries, managing platform accounts, billing merchants, and protecting the service. This means we determine the purposes and means of that processing.

When a merchant uses litecommerce to handle its shoppers' information, the merchant is the controller and we process that information on its behalf. This includes information collected during merchant-hosted and litecheckout-hosted purchases and account activity. The merchant's privacy policy explains its use of that information and the choices it offers. Our separate cookie and storage notice describes the technology used on the hosted checkout you visit.

• Inquiries and access requests. When you contact us, we receive your name, email address, any company name you provide, your message, and the correspondence that follows. An access request also includes the business name, selected plan, and signup source.
• Merchant accounts and team members. We receive account and business contact details, sign-in information, staff invitations, roles, and membership information. A merchant can supply these details when it invites you to its team. We also record account settings, API usage, administrative actions, and changes to access permissions.
• Platform billing and payment setup. Where applicable, we receive billing contacts and addresses, tax location, plan and invoice records, and transaction amounts, status, and references. When a merchant connects its payment account, we receive account identifiers and connection status from the payment provider. The merchant's customer payments and its fees for litecommerce are separate transactions.
• Merchant and shopper records. A merchant, its storefront, or a shopper using checkout or customer accounts can provide names, email addresses, phone numbers, billing and shipping addresses, basket items, orders, payment references, and returns. We can also receive reviews, communication preferences, notification requests, and information included in uploaded records or documents.
• Technical and usage information. When a browser or integration connects to our services, we receive technical data such as IP address, browser or device information, request times, pages or API routes requested, response status, and information about errors. Login and administrative activity can be associated with an account or organization.

Some fields are necessary for the feature you choose. For example, we need a reply address to respond to an inquiry and a shipping address to calculate delivery for a physical order. Leaving out required information can prevent that request or transaction from continuing.

• Respond to inquiries, review access requests, set up and administer accounts, and communicate about the service.
• Provide the platform and merchant-configured functions such as checkout, payment confirmation, order management, fulfillment, returns, customer accounts, and transactional messages.
• Manage platform billing, reconcile transactions, and keep records needed for accounting, taxes, disputes, and legal obligations.
• Authenticate users, enforce permissions, prevent abuse and fraud, investigate incidents, fix errors, and improve service reliability. Some signup and abuse checks run automatically.
• Send optional communications you choose to receive and record your preferences. On a merchant's behalf, we also process choices such as confirmed newsletter signups and back-in-stock requests where offered.

Where applicable law requires a legal basis, we use the following bases for information we control.

• Contract. We process information to perform a contract with you, such as providing access and handling billing, or to take steps you request before entering a contract.
• Legitimate interests. We respond to business inquiries, administer relationships with merchants and their staff, and use activity and diagnostic records to protect and maintain the service. We rely on these interests where permitted in light of your rights and interests.
• Legal obligations. We keep required accounting and tax records and respond to valid legal requirements.
• Consent. We rely on consent where required for optional communications or other optional processing. You can withdraw consent at any time for future processing.

A merchant may run checkout on its own storefront or send you to a litecheckout page operated for that store. When hosted checkout loads or updates shipping options, it can send your entered delivery address to litecommerce before you place an order. Hosted checkout can save a valid email address and any name or phone number you have entered as you type, before you select Continue. As you continue to payment, checkout can send the contact, delivery, and billing details it needs, along with any marketing choice you make. Your browser can separately save a draft in the current tab so you can continue after a reload.

When you enter card details in Stripe-hosted payment fields, Stripe receives the full card number and security code directly. We receive information used to process or reconcile the payment, such as payment references, the amount, status, and limited payment method details such as card brand and last four digits when available. Stripe and other financial institutions may also use transaction information for purposes such as fraud prevention, payment network compliance, or legal obligations. See the Stripe Privacy Policy.

If you choose to save a payment method where offered, the payment provider stores the payment details. We use a provider reference and limited display information to present the saved method in your account and support later payments you authorize.

A storefront can send an unfinished basket record containing items, quantities, totals, and a browser or session identifier. Depending on the integration, that record can also contain a contact email. Hosted checkout can retain progress even if you do not complete the purchase. Saving progress is separate from choosing to receive promotional email.

If you use a merchant's customer account, we use sign-in information to verify access and retrieve the account's orders, addresses, and returns. If you submit a review, the merchant can publish the review with a display name. We can match the email address you provide against the merchant's paid orders to display a verified purchase badge. The email address used for that match is kept private. The merchant uses the contact information it collects to operate its store and handle your requests.

Our services use cookies and browser storage for functions such as signing in, keeping a checkout session, preserving information in the current tab, and protecting transactions. Public signup and contact forms use Cloudflare Turnstile for bot protection. Cloudflare processes signals such as IP address and browser or device information to verify requests. See the Turnstile Privacy Addendum.

At hosted checkout, Stripe may use its own browser technologies to operate and protect payments. When a merchant has configured Google Analytics on an eligible checkout, the merchant's analytics property can receive events such as checkout starts and purchases, along with transaction details such as order reference, amounts, and items. Whether analytics uses browser storage depends on the checkout's configuration and applicable controls. The Cookies & storage link in the checkout footer gives details about the technologies, data, and lifetimes for that checkout.

Merchant storefronts may have their own analytics, advertising, and preference controls. Consult the merchant's policy for those uses and check the controls on each site you visit. You can also manage cookies and site data in your browser. Blocking essential cookies can affect signing in, checkout, and other features that depend on them.

• Merchants and authorized staff. The merchant and its authorized users can access the records needed to serve its shoppers, such as orders, delivery details, and return requests.
• Infrastructure and communications providers. We use Vercel for application hosting and request handling, Supabase for database, authentication, and storage services, Resend for email delivery, Sentry for error and performance monitoring, and Cloudflare for form security. These services handle the information relevant to their functions, such as request content and metadata, account records, uploaded files, recipient details and message content, error context, and verification signals.
• Company correspondence. Resend delivers messages submitted through our contact form. We use Google Workspace to receive and manage business correspondence, including inquiries, support and privacy requests, and related replies.
• Payments, tax, and shipping. Payment and tax providers such as Stripe receive transaction and address information needed for their functions. A merchant and its selected fulfillment, shipping, or returns services may receive contact and delivery information and shipment details.
• Merchant-selected services. A merchant can direct information to integrations it chooses, such as support and analytics services. The information involved depends on the integration and the merchant's settings.
• Legal, safety, and business purposes. We may disclose information when required by law or valid legal process, to protect rights and safety or investigate abuse, or in connection with a proposed or completed transfer of the business. Recipients can include authorities, advisers, and parties to a business transfer.

Retention depends on why we collected the information, the merchant's instructions where applicable, and legal and operational requirements. We use the following criteria to determine how long records are kept.

• Inquiries and account records. We keep information needed to respond, maintain the business relationship, administer accounts, and address later support, security, or legal matters.
• Orders and financial records. These records may be needed after a purchase or account closure for fulfillment, returns, chargebacks, tax and accounting duties, or disputes. Merchant data follows the merchant's instructions and applicable service terms.
• Unfinished baskets and checkout. These records serve a different purpose from completed orders. They can be replaced by newer activity or removed through the applicable deletion process. Clearing your browser removes the local copy. Server records follow their own retention process.
• Logs and backups. Operational and security records are kept for troubleshooting, abuse prevention, and investigation. Their rotation depends on the system and type of record. Copies in backups can remain until those backups expire or are overwritten.
• Communication preferences. We may retain a record of a choice or opt-out as needed to honor it and document the request.

We are based in the United States. Our service providers and merchant integrations may process information in the United States or other countries where they operate. The laws in those countries can differ from the laws where you live. Contact us for information about the locations and safeguards relevant to a particular transfer. For data handled on a merchant's behalf, the applicable processing arrangements govern those transfers.

We use authenticated access, organization-scoped permissions, and activity records to help protect information. Payment forms use provider-hosted fields where supported. Merchants manage their team access and the integrations they connect. Use the appropriate account or checkout flow when sharing sensitive information and keep credentials and full payment card numbers out of ordinary messages.

Your rights depend on where you live and the law that applies. You may be able to ask us to confirm or provide access to information we hold about you, explain its sources, uses, and disclosures, correct it, delete it, or provide a portable copy. You may also have rights to restrict or object to processing, withdraw consent, or challenge how we have handled your information.

Where applicable, U.S. state privacy laws can provide choices about sales of personal information, sharing for cross-context behavioral advertising, targeted advertising, certain profiling, or use of sensitive information. They may also provide a right to appeal a decision and protection from discrimination for exercising your rights. Ask us about choices for information we control. For a merchant's advertising or other uses, refer to that merchant's disclosures and choices.

Use the unsubscribe option provided in promotional messages or contact the sender to change your preferences. A merchant newsletter signup and your choice to receive a restock notification serve separate purposes. Service messages, such as security notices and receipts, can still be needed to operate an account or complete a transaction.

Depending on your jurisdiction, you can also raise a concern with your privacy regulator, including your local data protection authority in the EEA, the Information Commissioner's Office in the UK, or the applicable federal or provincial privacy authority in Canada.

For a request about a purchase, account, or other information held for a merchant, contact that merchant through its store or privacy policy. It can verify the request and determine how to respond, with assistance from litecommerce where appropriate.

For questions, complaints, or requests about information litecommerce controls, email privacy@litecommerce.io or write to the address below. Tell us what you are requesting and how we can identify the relevant account or interaction. We may ask for information reasonably needed to verify your identity. If you act through an authorized agent, we may also need to verify their authority. Include an appeal in your message if your law provides that option. Keep passwords, verification codes, and payment card numbers out of your request.

Minors. Our merchant administration, developer tools, and signup materials are intended for business users. If you believe a child has provided us with personal information directly, contact us using the details above. For information submitted through a merchant's store, contact that merchant.

We post updates here as our services or data practices change. For material changes, we provide any additional notice and choices required by applicable law.