Privacy policy

1. Who we are

Loppee operates a public business-trust registry and directory. For the purposes of this policy, Loppee is the controller of the personal information described below. Contact us at privacy@loppee.com with any privacy questions or requests.

2. Information we collect

• Account & authentication data. Depending on the account and enabled providers, sign-in may use a passwordless email magic link, an enabled OAuth provider, or a passkey. We process identifiers supplied by that provider and authentication events (such as sign-in timestamps, authenticator type, and multi-factor status) to operate accounts.
• Business information. Business owners and authorized agents may submit business details, documents, media, and verification evidence. Raw submitted documents remain private. Public Trust Cards expose only approved minimized business metadata; owner-provided insurance, when shown, carries this disclosure: “Insurance certificate provided by the business. Not independently confirmed by Loppee.”
• Submissions & requests. Information you provide through forms (for example, agent-access requests, claims, reviews, or messages).
• Optional AI-assisted support drafting. If this feature is enabled and an authorized Loppee support teammate explicitly requests a draft, we may process a bounded portion of the relevant support conversation and an optional drafting instruction. The feature does not send replies automatically, and AI-assisted replies are reviewed by a person and visibly labeled.
• Agent/API usage. If you use Loppee through an API key, MCP connector, OAuth-connected app, or third-party agent, we process request metadata, tool/action names, scoped credential and connection identifiers, the permissions you approved, account and selected-business scope, rate-limit events, and audit logs needed to authenticate, authorize, and secure those requests. We do not ask a connected agent to collect passwords, one-time authentication codes, payment-card data, or raw device coordinates. When a signed-in customer deliberately chooses “Use my location” on a short-lived Loppee location link for that same customer account, Loppee encrypts the device position and uses it only to apply nearby-business reach for that customer’s agent. The agent receives business results, not the coordinates or exact distance. The position does not become the customer’s saved home location, stops being usable after 15 minutes or 20 searches, can be stopped while the approval page remains open, and expired or revoked ciphertext is scrubbed by the location-retention cleanup. When OpenAI for ChatGPT, or another supported AI platform, supplies optional approximate location metadata with an individual tool request, Loppee treats it as untrusted, best-effort, request-scoped context. Loppee may use sanitized general-area information only to label an area or disambiguate duplicate literal business names; it does not persist those values or intentionally write them to ordinary application logs, and it never returns raw coordinates to the connected app. This metadata does not authenticate or bind an account, expand plan reach or entitlement, change candidate membership, alter trust or verification, affect quality ranking or commercial ordering, activate Sponsored placement, record an impression, or prove precise location. A customer-approved Loppee location handoff remains the sole external-agent authority for precise local discovery.
• Billing, jobs, and workflow data. Paid business features may involve subscription, invoice, and checkout metadata handled by our payment processor. Job applications, resumes, customer messages, and owner replies are stored privately and made available only through scoped account or business access.
• Usage & device data. Standard server logs, including IP address, browser/user-agent, pages requested, and timestamps, used for security, abuse prevention, and analytics.

3. How we use information

• To provide, maintain, and secure the Services and your account.
• To verify businesses and publish Trust Cards and directory listings.
• To operate public agent endpoints, MCP tools, scoped API keys, rate limits, and audit logs.
• To respond to your requests, claims, and messages.
• To process billing, subscriptions, job applications, reviews, and owner workflows.
• To detect, prevent, and investigate fraud, abuse, and security incidents.
• To comply with legal obligations and enforce our Terms of Service.

4. How information is shared

Published business information (such as Trust Cards and directory listings) is, by design, publicly visible and accessible to people and to AI agents. We also share information with service providers who process data on our behalf (for example, hosting through Render, database and authentication through Supabase, email delivery through Resend/SMTP, and payment processing through Stripe), under contracts that require them to protect it. When optional AI-assisted support drafting is enabled, the bounded conversation excerpt needed for a human-requested draft is also sent to the AI provider selected in Loppee's protected control plane, subject to that configured provider account's data-use terms. Third-party AI agents or connector clients may retrieve public registry data when they call public endpoints. We may disclose information if required by law or to protect rights, safety, and the integrity of the Services. We do not sell personal information.

When you deliberately connect a third-party AI app through OAuth, including an app in ChatGPT from OpenAI, the provider may receive the Loppee inputs and outputs needed for the tools you use within the permissions shown on the consent screen. Depending on the connection, that may include public registry data or private, scoped account or selected-business information such as messages, notifications, reviews, and job applications. A connected app may carry out only the actions you approved, and consequential actions require human confirmation. Applicant ranking or employment decisions are not delegated to the app: an authorized human owner must independently choose the exact status before the app can record it. The third-party provider handles the information it receives under its own terms and privacy policy. You can disconnect the app in Loppee to revoke its future access.

Loppee keeps customer-support conversation egress disabled unless an administrator has separately approved external processing and confirmed that the connected Gemini account receives Google's paid-tier data-use treatment. Google currently states that content on its free tier may be used to improve Google products, while paid-tier content is not used for that purpose. Provider terms can change, so administrators must review Google's current data-use terms before enabling this feature. Credential testing does not include a customer conversation.

5. Cookies & similar technologies

We use a small number of strictly necessary, privacy-preserving cookies and local-storage items to keep you signed in, remember your preferences (including your cookie choice), and operate core features. We do not use advertising or cross-site-tracking cookies. Because the cookies we set are strictly necessary for the Services to function, disabling them in your browser may break sign-in and other features. See the cookie notice shown on first visit for a summary.

6. Data retention

We retain information for as long as needed to provide the Services, comply with our legal obligations, resolve disputes, and enforce our agreements. Published business records may persist in the public registry until removed through our business-removal process. Scoped-key audit logs, moderation records, billing records, and security logs may be retained as needed to investigate abuse, prove authorization, resolve disputes, and meet legal or accounting obligations. Loppee's support-copilot control plane retains an immutable hash and authorization receipt for an AI-generated draft, but does not durably store the raw generated draft body in that receipt. A human-sent support message is retained as part of the support conversation under the ordinary message-retention rules. OAuth connection, permission, revocation, and audit records may be retained as needed to prove authorization, enforce revocation, prevent replay, and investigate abuse; disconnecting stops future access but does not erase records we must retain for security, legal, or accounting purposes.

7. Your choices & rights

Depending on where you live, you may have rights to access, correct, delete, or port your personal information, or to object to or restrict certain processing. To make a request, email privacy@loppee.com. Business owners can request changes or removal of a listing through our business-removal request process.

8. Security

We use technical and organizational measures designed to protect information, including transport encryption, access controls, and multi-factor authentication for privileged accounts. No method of transmission or storage is completely secure.

9. Children's privacy

The Services are intended for businesses and adults. They are not directed to children under 13, and we do not knowingly collect personal information from them.

10. Changes to this policy

We may update this policy from time to time. We will revise the "Last updated" date above and, where appropriate, provide additional notice.

11. Contact

Questions or requests: privacy@loppee.com.