Privacy Policy — Quan
Effective: January 27, 2026 · Telegram / bots section updated: September 3, 2026 · Service: Quan and related Telegram bots operated for Quan, Fresh House Network, and Amplify Systems at https://quan.is
This is a product privacy policy for transparency, Stripe checkout, and Telegram BotFather / third-party app disclosures (see telegram.org/privacy-tpa). It is not a claim of attorney review or a substitute for counsel when required by law.
1. Who we are (Developer)
The Fresh House LLC operates Quan, doing business as Amplify Systems, The Fresh House Network, and Quan. These are product lines of the same company, not separate unrelated businesses. Quan provides AI-assisted experiences, partner context, optional prepaid wallet billing, and Telegram bots / Hermes operator agents used for product and internal operations.
Our Telegram bots and mini apps (when offered) are independent third-party services. They are not maintained, endorsed, or affiliated with Telegram Messenger Inc. Operational contact: support@quan.is. Billing and payment questions: billing@amplifysystems.io.
2. Scope — Quan app vs Telegram bots
- Quan web / app (https://quan.is): accounts, wallet billing, AI tools, and related product surfaces.
- Product / community bots: Telegram bots that interact with members or partners as part of Quan or Fresh House Network product flows (for example entitlement-aware Quan ask routes). Some of these are live; others are planned. Where a bot is DM-only or group-disabled, that is an intentional product setting, not a claim that we process group message history by default.
- Operator / Hermes capsule bots (Lake Keeper fleet and similar): bots such as
@fhn_ecology_bot,@sky_command_bot,@fhn_lakekeeper_bot, and related operator agents are primarily DM-oriented operator tools for Sky Fresh Singh / Fresh House Network staff and authorized operators. They are not public member routers. BotFather metadata for this fleet points at this page (/legal/privacy). Fleet paste pack (internal): Creator Capsule workflow BOTFATHER-FLEET-METADATA-PACK-2026-09-03.
3. What we collect
3.1 Quan account & product
- Account & identity: email and identifiers needed to sign in; links to partner or contact records where applicable.
- Usage: prompts, tool calls, and telemetry needed to run Quan, meter usage, prevent abuse, and improve reliability — under access controls and partner isolation (RLS) where configured.
- Payments: billing details are processed by Stripe; we receive Customer IDs, payment status, and transaction metadata — not full card numbers on our servers.
3.2 Data from Telegram (bots / API)
Consistent with Telegram's platform rules and Standard Bot Privacy Policy, when you use our bots we may receive:
- Platform-limited identifiers Telegram makes available to bots (for example Telegram user id, username if set, language code, and chat / message metadata needed to reply).
- Content you send the bot: text messages, voice/audio, photos, documents, and other files you upload or forward to the bot.
- Optional shares you initiate: contact, phone number, location, or other personal information only if you choose to share them with the bot.
- Anonymous / aggregated diagnostics (for example error rates) that are not linked to you when feasible.
We do not claim access to your full Telegram account, contacts list, or private chats with other people beyond what Telegram delivers to a bot you message (or to a group, if a given bot is later enabled for groups and you interact there).
4. Why we process data
We process personal data only as needed to:
- Provide Quan and bot features you use (replies, session context, operator workflows).
- Authenticate users, allocate usage to the correct wallet and partner, and settle prepaid balances.
- Detect and address security, abuse, and reliability issues.
- Meet legal obligations (for example accounting records for payments).
We do not sell Telegram or Quan user data. We do not monetize user data for unrelated applications outside the scope of these services unless we clearly state that purpose and obtain any consent required. We do not use bot DMs as a general advertising network.
5. Cookies & similar technologies
On the Quan web app we use cookies and local storage where needed to keep you signed in and protect the service. Those are treated as essential. There is no marketing cookie banner on this app; optional analytics would be listed here before any non-essential scripts run. Telegram clients are governed by Telegram's own privacy policy; our bots do not set browser cookies inside Telegram.
Other Fresh House Network / Amplify Systems properties (HighLevel-hosted pages, Quan Chat on chat.quan.is, partner funnels) may use additional cookies under their own notices. Questions: support@quan.is.
6. Sharing & processors
We do not sell personal data. We share data only as needed to operate the service, for example:
- Infrastructure / vendors: hosting, databases, logging, email, payments (Stripe), and AI model providers that process prompts/responses to deliver the feature you requested — under contracts and access controls appropriate to the service.
- Within The Fresh House LLC product lines: Fresh House Network, Amplify Systems, and Quan may share account context needed to provision related access (disclosed on product signup / legal pages). That is same-company operation, not sale to an unrelated third party.
- Lawful requests: when required by law (for example a valid court order).
We do not freely pool private bot conversations across unrelated bots or partners without a product reason you would reasonably expect (for example the same operator continuing a Hermes session), partner isolation rules, or your direction. Partner community surfaces use partner-scoped isolation (RLS) where configured — see also our partner-community policy documentation in the Fresh House Network legal docs set.
7. Retention & security
We retain data as long as needed for the purposes above and as required by law (for example billing records). Operator bot session logs and message content used for Hermes / Lake Keeper workflows are kept for operational continuity and security review, then deleted or minimized when no longer needed. Exact retention windows vary by surface and may change as products mature; we will update this page when stable defaults ship.
We use technical and organizational measures including access controls and encrypted transport in transit where standard for our hosts. No system is perfectly secure.
8. Your rights & requests
Subject to applicable law, you may:
- Request a copy of personal data we hold about you in connection with Quan or our bots.
- Request deletion of that data, except where we must retain essential records (legal obligations, fraud prevention, accounting).
- Request correction, restriction, or object to certain processing; withdraw consent where processing was consent-based.
- Lodge a complaint with a data protection authority that has jurisdiction.
Email support@quan.is with the subject line Privacy request, and include your Quan account email and/or Telegram username / user id if the request concerns a bot. We may verify identity before fulfilling requests and may impose reasonable rate limits to prevent abuse. We aim to respond within the timeframes required by applicable law and, in any event, within 30 days of a complete request where the Telegram standard bot policy expectation applies.
You can also stop bot processing by blocking or deleting the chat with the bot in Telegram and discontinuing use of Quan.
9. Children
Quan and our operator bots are not directed at children. Do not use these services if you are under the age required by Telegram and by applicable law in your jurisdiction.
10. International users
We may process data in the United States and other countries where our providers operate. If you access the services from elsewhere, you understand data may be transferred to those locations with safeguards appropriate to the providers we use.
11. Changes
We may update this product privacy policy from time to time. Changes take effect when posted on https://quan.is/legal/privacy (and the same content at /privacy). Material changes for Telegram bot users will be reflected on this page; continued use after posting constitutes acceptance where permitted by law. Telegram's own default TPA policy remains at telegram.org/privacy-tpa and does not replace this Developer policy once we publish ours.
12. Contact
support@quan.is · billing@amplifysystems.io · Terms of Service
Product privacy policy for Quan and related Telegram bots. Not attorney-reviewed. For payment-provider and BotFather URL requirements only — obtain counsel before relying on this as your sole legal instrument.