Privacy

Privacy Policy

Effective 19 October 2026

This Policy explains how Leptex handles personal data. It distinguishes carefully between data we determine the purposes for ourselves and data we process only on a customer's instructions, because that distinction decides who is accountable for what.

1. Who this Policy covers

This Policy is issued by Lianda Labs LLC, a Washington limited liability company located in Bellevue, WA 98007, United States ("Leptex", "we", "us").

It applies to the Leptex platform: the merchant workspace, links used by end customers, the cross-merchant end customer portal, the Leptex iOS app once it is available, and this website, including its business search.

Leptex hosts merchant store pages, including those on a merchant’s own domain, and the store chat a merchant can embed on its own website. This Policy covers Leptex’s processing there, while the merchant’s own privacy notice covers the merchant’s use of the information it receives. This Policy does not apply to the rest of a merchant’s own website or to third-party websites linked from a merchant’s material.

2. Our two roles: controller and processor

Leptex as controller. We determine how account, billing, support and service-security information is used to operate Leptex. We also manage end customer portal accounts, business search on this website and job applications. The processing role depends on the purpose, not just on which screen you use.

Leptex as processor. Where a merchant instructs us to handle its uploaded materials and customer conversations on its behalf, that processing is subject to our Data Processing Agreement (DPA). The merchant determines its purposes and must provide its own notice.

Where an end customer saves conversations to their own portal account and asks the portal assistant about them, Leptex handles those saved conversations as controller, at the end customer’s request and to provide that service. For merchant-controlled information, you can contact the merchant or ask us to route your request.

3. Personal data we process

Account and security information — name, email, sign-in credentials or identity-provider identifiers, account membership, permissions, sign-in events, the IP address and browser or device user agent recorded with each sign-in session, and, if you allow notifications in the iOS app, the device push token.

Billing information — agreement and invoice details, subscription status, payment identifiers and payment history. Payment card entry is handled by the payment provider; Leptex does not store full card numbers.

Content — uploaded materials and files, messages, attachments and information generated from them, including AI-generated summaries and analyses of conversations. Content also includes the names, phone numbers, delivery or service addresses and notification email addresses given for orders and bookings. Images are re-encoded on upload, which removes embedded metadata; files a merchant delivers with a product or an order are stored as uploaded. Merchants supply their materials; end customers and account members supply their messages and order details. Only upload information you have authority to share.

Email verification and acceptance records — the email address entered to save a conversation, verification requests, and the versions of the Terms and Privacy Policy presented when you confirm. We record the verified account, confirmation time, language and document fingerprints. These records do not include a copy of your conversation.

Service use and support — feature usage, visits to merchant pages and promotion links, billing measurements, server logs that record IP addresses and the web addresses requested, error information and information you send when contacting us. The recipient of a support request may see the details you include.

Website search — the terms you enter in business search on this website, which are sent with your IP address to the Leptex platform to return results and limit abuse.

Job applications — information you send to our careers address, used to assess your application and communicate with you.

Sources — you and your organisation, merchants you contact, authorised identity/payment providers, and information collected while operating and securing the service.

4. Purposes and lawful bases

Service and billing. We use information needed to provide your account, requested features and purchases. Where GDPR applies, the basis is the performance of our contract with you.

Saving a conversation. We use the address you enter to send a verification link. Sending the link alone does not create an account, save the conversation or subscribe you to marketing. The recipient must confirm on the linked page; confirmation signs them in and creates an account if needed. We record their acceptance of the Terms and acknowledgement of this Policy. This acknowledgement is not consent to unrelated processing or marketing.

Website search. We use the terms you enter to return business search results and your IP address to limit abuse. Where GDPR applies, the basis is our legitimate interest in offering a search that works and is protected from misuse.

Job applications. We use the information you send to assess your application and to communicate with you about it. Where GDPR applies, the basis is taking steps at your request before entering into a contract, and our legitimate interest in recruiting.

Legal obligations. We retain or disclose information where applicable tax, accounting or other law requires it.

Security and administration. We use necessary information to protect accounts, investigate misuse and respond to support requests. Where GDPR applies, the basis is our legitimate interest in keeping the service secure and in answering the people who contact us.

Consent. We do not currently send marketing. We do not use third-party analytics or advertising trackers; merchants see first-party counts of visits to their pages and promotion links. If we start optional tracking, we will ask for your consent first where the law requires it. Withdrawing consent does not affect earlier lawful processing.

Merchant-directed processing. The merchant is responsible for its lawful basis and notices. A DPA governs our instructions; it does not itself provide the merchant’s lawful basis.

5. Data-use boundaries

Advertising. Business search on this website can show listings that merchants pay for; they are labelled Sponsored and are chosen from the search, not from information about you. This website does not include behavioural advertising or optional analytics trackers.

Private content. An end customer’s access to a conversation does not grant access to a merchant’s private workspace materials.

Sale and sharing. We do not sell personal data, and we do not share it for cross-context behavioural advertising. We disclose it only to the recipients described in section 6, including services a merchant chooses to connect.

AI providers. We do not use personal data to train models, and the providers we use to generate AI responses are not permitted to train models on customer data. We remain responsible for how our providers handle personal data on our behalf, as the law and our DPA require.

6. Sub-processors and recipients

We disclose personal data to service providers in these categories, each acting on our instructions: cloud hosting, storage and AI model services; network delivery and security, including bot protection; email; push notifications; shipping rate quotes; and payment processing. We require each provider to protect personal data at least as well as this Policy describes and to use it only to provide its service to us. The current list of the providers we use is available on request from privacy@leptex.com.

For shipping quotes, USPS receives the origin and destination ZIP codes and the parcel’s size and weight, not names or street addresses. For push notifications in the iOS app, Expo and Apple receive the device’s push token and a short notification text. If you choose to sign in through an identity provider, that provider confirms your identity to us; if you sign in with Apple, Apple gives us your email address, which may be an Apple private relay address. Payment providers may separately act as controllers for fraud prevention and legal obligations.

Our AI model provider is Google Cloud (Vertex AI, Gemini models). To generate replies, summaries, translations and search results, we send it the messages, conversation history and merchant materials each task needs. Google processes this data as our service provider, and some requests are processed outside the United States.

Our email delivery provider, Resend, receives each recipient’s address and the content of the emails we send: sign-in and verification links (with the merchant label), order and booking emails (which can include the items, amounts, buyer name, contact number, delivery or service address and a link that reopens the conversation), and notifications to merchant team members (which can include up to 300 characters of the buyer’s latest message). Verification emails do not include the conversation transcript or order details.

Conversation messages shared with a merchant are visible to that merchant and its authorised team. Workspace administrators may manage members and access content within their permissions. Authorised Leptex staff can access customer data only as needed, as section 9 describes.

A workspace owner can connect a personal AI agent of their choice to the workspace. Within the access the owner grants, the agent can read buyer conversations, AI summaries and order cards, reply to buyers and confirm or decline orders. What the agent reads passes to the agent’s provider and is handled under the merchant’s arrangement with that provider, not under this Policy. Connector tokens expire after 90 days and the owner can revoke them at any time.

If a merchant adds YouTube videos to its pages, the videos and thumbnails load from Google when the page opens, so Google may receive your IP address and browser information.

We may disclose information when lawfully required or as part of a business transfer, subject to applicable notices and safeguards. We tell merchants before we add or replace a sub-processor, as the DPA provides.

7. International transfers

Leptex operates the service from the United States, where platform data is stored. Our AI requests are processed through Google’s global endpoint and may be handled outside the United States; some other providers may also process personal data in other countries. If you use Leptex from outside the United States, your information is transferred to and processed in the United States.

Where the law restricts such a transfer, we rely on a transfer mechanism it recognises, including the standard contractual clauses in our providers’ data processing terms and, for merchants, in the DPA. You can ask privacy@leptex.com for a copy of the relevant safeguards.

8. Retention

Account information is kept while the account is active. You can delete your account in Settings or by writing to privacy@leptex.com. If you are the only owner of a workspace, the account cannot be deleted in Settings, because the workspace must be closed as well; write to us and we will close the workspace and delete the account. Deletion signs out all of your sessions at once. For 30 days you can sign in again and restore the account; after that we delete or anonymise your account profile in the running systems. Information held separately for transactions or other purposes follows the rules below.

Portal assistant chats and push-notification registrations are linked to your email address and are not currently removed automatically when an account is deleted; we delete them when you ask at privacy@leptex.com.

Private conversations are shared records, not separate copies for each participant. Saving one links it to your verified account; the original browser keeps access until its private chat cookie expires, 30 days after the chat was opened. A buyer can permanently delete it from the chat or portal. A merchant must first archive and close it before permanently deleting it; archiving stops further messages. Archived conversations become eligible for automatic deletion 90 days after archiving, and scheduled cleanup removes them in batches.

Conversation deletion removes the conversation and messages from the running database for both participants. Associated caches and attachments used only by that conversation are queued for cleanup; failed cleanup is retried. Orders, bookings, transaction records and files that are independently needed for those services are handled separately and are not deleted by deleting the conversation. Records the merchant keeps that were created from the conversation, such as its customer list entry, order records and AI reports that quote messages, are not deleted with the conversation either; they are deleted when the merchant deletes them or its workspace is deleted. Copies already received or exported by a recipient are outside this in-product deletion.

Public page chats on a merchant’s website are kept while the merchant’s workspace is active and are deleted with the workspace; we delete an individual chat when the merchant or you ask. Assistant chats in the workspace and portal are kept until you delete them or ask us to delete them.

Verification data includes an email address bound to the conversation after the first admitted verification request. Further requests for that conversation can be sent only to that address. The address is removed from the conversation when it is deleted; after a confirmed save, the merchant’s records also keep the address, as described above. Sign-in and verification links expire after 15 minutes; team invitation links expire after 7 days.

Acceptance evidence is kept with the account while it is active and through its 30-day account deletion recovery period, then removed by the account cleanup process. It is independent of the conversation and does not retain its contents.

Customer content is kept while the merchant’s workspace is active. A merchant can delete documents, images, private chats and team members, and can archive products, services, links and pages. When a workspace is closed at the end of the agreement or at the merchant’s request, its content is deleted from the running systems 90 days later. After the agreement ends, we return or delete content as the DPA provides.

Billing records, such as invoices and payment records, are held by our payment provider for the periods tax law requires; the billing records we keep in our own systems are deleted with the workspace.

Security records include sign-in session records, each with its IP address and user agent; a session record is kept while you stay signed in and for up to 7 days after your last activity. Server logs that record IP addresses and the web addresses requested are kept for up to 30 days. Temporary rate-limit and abuse-prevention counters expire automatically according to their security window.

Job applications are kept only as long as needed to assess the application, communicate with you and meet recordkeeping obligations, and are then deleted.

Backups are kept for up to 14 days and then expire; information deleted from the running systems can remain in a backup until it expires.

Legal holds may require retaining limited information for a dispute or legal duty; such retention must be restricted to that purpose.

9. Security

Leptex uses access controls to restrict private workspace information to authorised accounts and roles. Security also depends on how production systems and third-party services are configured and operated.

No system can be guaranteed completely secure. Please keep credentials private and report suspected unauthorised access or security vulnerabilities to security@leptex.com.

The measures in place include encryption of data in transit and at rest and access controls that limit data to authorised accounts. Leptex staff access customer data only as needed to provide the service, investigate faults, handle reports, respond to a merchant’s request or meet a legal obligation. Access through our administration console requires a company account, and each request is logged; these logs are kept for a limited period.

10. Personal data breaches

We assess personal data incidents and make notifications required by the law applicable to our role. Where GDPR requires authority notification, its 72-hour rule and conditions apply.

For merchant-controlled data, the DPA requires notification to the merchant without undue delay after awareness of a personal data breach, with information supplied as it becomes available.

11. Your rights

Subject to the conditions in applicable law, you may request access to your personal data, correction, erasure, restriction of processing, portability, and you may object to processing based on legitimate interests.

Where processing rests on consent, you may withdraw it at any time without affecting the lawfulness of processing before withdrawal.

Where California privacy law applies to Leptex and your information, additional rights may include knowing, deleting and correcting information, opting out of sale or sharing, and limiting certain uses of sensitive information, without unlawful discrimination. Authorised agents may submit requests subject to appropriate verification.

Send requests to privacy@leptex.com. We provide a copy of your personal data when you ask for one; there is no self-service export. You can delete your account as section 8 describes. We may need proportionate verification to protect your information. Applicable response deadlines and permitted extensions depend on your jurisdiction. You may complain to the relevant data protection authority.

For data we hold as a processor, we will route your request to the merchant who controls it and assist them in answering.

12. Cookies and similar technologies

This marketing website does not currently set cookies. When you choose a language on the website, or arrive through a link that names one, the choice is kept in your browser’s local storage under the name leptex-locale until you change or clear it, or your browser removes it. It does not currently include optional analytics or advertising trackers. You can change the language on the website or clear the stored choice through your browser.

When you use the platform, it stores the following in your browser. A sign-in cookie keeps you signed in for up to 7 days after your last activity. A private chat cookie lets the browser that started a private chat continue it for up to 30 days, including after it is saved to an account. Language cookies remember your language for up to a year. If you arrive through a merchant’s promotion link, two cookies record that visit for the merchant’s statistics for 30 minutes. Merchant pages keep chat and page tokens and a list of recently viewed pages in local storage, and the workspace keeps your name, email and display settings there until you sign out. A pending save link may be held temporarily in session storage during sign-in, with a 15-minute validity check.

Clearing these items removes that browser’s access; it does not delete the conversation or the account’s access. A conversation link sent in an order email or shared by the merchant reopens the chat in any browser, so keep it private. Use a trusted device for private conversations. The iOS app keeps your sign-in token in the device keychain until you sign out or the session expires.

Merchant pages can show YouTube videos and thumbnails, loaded from Google when the page opens, and sign-in pages use Cloudflare bot protection. External sign-in and payment services may process device information on their own pages. We do not sell or share personal data for cross-context behavioural advertising and do not track you across third-party websites, so browser Do Not Track and Global Privacy Control signals do not change how we process your data. See Cookie information in the footer for this website’s current storage notice.

13. Automated decision-making and AI

AI assistants use information available for the selected conversation or task. AI output may be inaccurate. Confirm important claims, prices and commitments with the merchant or a qualified professional.

Conversation summaries and inferences, such as buying stage, interests, an intent score and a likely role, support the merchant’s judgement; they should not be treated as verified facts. Do not use them alone to decide matters that have legal or similarly significant effects on a person.

On a merchant’s public page, an AI review classifies chats as likely customers, competitors, automated traffic or spam. Chats classified as competitors, automated traffic or spam are not offered the in-chat order or booking option and are not shown in the merchant’s default inbox, but you can still contact the merchant. In a private chat, the assistant can prepare, update or withdraw a draft order from what you write; only the merchant confirms an order.

Every Leptex chat on the web tells you that replies may come from an AI assistant. In chats opened from a merchant’s link, each message is labelled as written by the AI assistant or by a person. Text a merchant sends, including text adapted from an AI suggestion or sent through an agent the merchant has connected, is shown as the merchant’s reply. We do not make decisions about you by automated means alone that have a legal or similarly significant effect on you.

14. Children

The service is not directed to or designed for children. You must be 18 or over to create an account. If we learn that we hold a child’s personal data, we delete it, or, where a merchant controls the data, we ask the merchant to delete it. If you believe a child’s information has been submitted inappropriately, contact privacy@leptex.com.

15. Changes to this Policy

We will post any change here and update the date above. For material changes we will give account holders advance notice by email.

16. Contact

Privacy questions and data requests: privacy@leptex.com

Leptex has not appointed a data protection officer or a representative in the European Union or the United Kingdom. Write to privacy@leptex.com on any data protection matter.

Location: Bellevue, WA 98007, United States

This Policy is published in English and Chinese. Where the two differ, the English version governs, unless mandatory local law provides otherwise.