Hypermesh Privacy Policy
Effective date: November 16, 2026
This policy explains what information Fyber Labs collects when you use hyperme.sh, the Hypermesh portal, the host software, the Hypermesh CLI, and Visor (together, "Hypermesh"), and how we use and share it.
See also our Terms of Service.
1. Who we are
Fyber Labs TN LLC, a Tennessee limited liability company, operates Hypermesh and decides how this information is used. Contact: legal@hyperme.sh for privacy requests, security@hyperme.sh for security issues, bugs@hyperme.sh for bugs, sales@hyperme.sh for billing, refunds, and receipts, and hello@hyperme.sh or info@hyperme.sh for general questions.
2. Features we offer in some places
Some features, such as bringing your own model, are offered only where hyperme.sh or the portal says so. Where this policy describes one of those features, that part applies when you use it.
3. What we collect
Visiting hyperme.sh
- Display preferences. Your light/dark and reading-mode choices are saved in your browser's local storage, on your device. They aren't sent to us.
- Basic request information. Like most websites, our servers and our hosting and network providers receive your IP address, browser type, the pages you request, and timestamps. We keep server, access, and security logs for at least one year to support security monitoring, incident investigation, and audits, and then delete or archive them under our retention schedule.
- No ad trackers. We do not use advertising pixels or advertising session replay. Our product monitoring is first-party. Where page experiments and product analytics are offered, they require a separate opt-in; see section 6.
Your account
- Your email address and your first and last name. If you sign up with email, you also choose a password. Our sign-in service stores it in hashed form, never as plain text.
- If you sign in with Microsoft, GitHub, or Google, we ask that provider only for your basic profile: your name, email address, and an account ID. We also receive your GitHub username, or your organization's ID from Microsoft or domain from Google if you use a work account, plus any Microsoft directory roles. We use these to recognize your organization and set up your access.
- Billing address (street, city, state, ZIP code, and country). We keep it with your account to work out the sales tax on your purchases and to keep tax records.
- Blockchain wallet addresses you link to your account, for example to pay in USDC or receive payouts, and records of payments sent to or from them through Hypermesh.
- Sign-in sessions for the portal. If you sign in from the CLI or Visor desktop companion, your session is stored in your computer's system keychain, on your device.
Renting
- Your reservations, checkouts, leases, and receipts. A lease records what you rented (the model or hardware class), the host it ran on, the hours reserved, its status, and when it started and ended. A receipt shows the lease, the hours, whether the host was certified, its price in US dollars, the USDC amount, and whether a request ran on a public provider.
- Payment details. Hypermesh doesn't take card payments for leases. You pay in USDC through Stripe's stablecoin payment method, and Stripe processes the payment under its own privacy policy. If you buy USDC through Stripe's crypto onramp, Stripe collects your card details and any identity information it needs directly, also under its own privacy policy. We don't receive your card details. The personal information Stripe returns to us is your name and billing information, not your card details or identity documents. We separately keep transaction records to reconcile payments. We use your billing address with Stripe to calculate applicable US sales tax, and we keep a record of the amount and tax for each payment.
- Prompts and outputs. Not stored by default. See "Your prompts and outputs" below. Our monitoring is designed to keep prompts, outputs, and model files out of analytics.
- Uploaded models (where offered). Models and files you upload or link to, and the results of our checks on them. An uploaded model is kept only while it's in use. We delete it 1 year after it was last used, or within 90 days after your account is closed, whichever comes first. You can delete an upload yourself at any time. Uploads that fail our safety or format checks are deleted and aren't run. Models you link by URL are fetched when needed, and the copy is handled the same way.
- Wallet payments. Your registered wallet address and the signed message you used to register it. For each payment, Stripe gives us the paying wallet address, the network, the transaction ID, and the amount, and refunds go back to that paying wallet. Stripe screens payments for sanctions and anti-money-laundering risk.
Hosting
- Hardware details checked during installation, such as processor and GPU, memory, storage, and operating system.
- Device registration linking your host to your account.
- Host status reports the host software sends regularly, such as the software version, temperatures, disk space, the identifier of the model currently loaded, and uptime. They don't include renters' identities or prompts.
- Check results from our hardware, model, and health checks, and lease start and end times.
- Network information needed to connect your host to the network: its IP address and the private address of its encrypted tunnel.
- Public listing. On hyperme.sh/nodes we show a public label for your host (its hardware class and a short device ID, not your name), its hardware class, whether it's certified, and whether it's online and selling.
- Payout information. Your payout amounts and history. To pay you, Stripe Connect onboarding collects your identity and tax information (for example legal name, address, date of birth, tax ID, and bank account or payout wallet details) under Stripe's privacy policy, to verify you and issue tax forms such as Form 1099. The personal information Stripe returns to us is your name and billing information. Stripe collects identity documents, tax IDs and bank details through its own flow; it does not return those to us.
Visor
Visor runs on your own computer. When you run it, it can capture your screen and audio and see your keyboard and mouse input, so it can act for you. That information is processed on your computer. We don't receive it unless you connect Visor to a service that sends it, for example:
- sending prompts to a model on Hypermesh, or
- posting a session feed to the s3r.ch forum. That feed includes a screenshot and recent activity such as the focused app, typed text, key and mouse actions, tool names, prompts, file names, and secret names. It doesn't include secret values or file contents. See the s3r.ch Privacy Policy.
Optional crash reporting and product telemetry, where available in your Visor version, require their own consent. Declining crash reporting does not authorize upload; review the reporting controls in your version. Connected services receive information only through the features you choose to use. Visor downloads come from GitHub, which receives your IP address when you download.
When you contact us
What you send to legal@, security@, bugs@, sales@, hello@, or info@, including your email address and anything you attach.
Your prompts and outputs
Your prompts are how many AI companies make money and train their models. Hypermesh takes the opposite approach: nothing is kept or used for training unless you choose it.
- Not kept by default. We don't store your prompts or outputs beyond what's needed to run your request, and we never sell them.
- Saved history is opt-in. We keep your prompts and outputs as history only if you turn that on. We use saved history to show it to you, and for debugging and quality checks on Hypermesh. That isn't training. You can turn history off at any time, which stops saving new history, and you can delete what's stored. Deleting or turning off history doesn't delete prompts you submitted for training.
- Training is a separate opt-in. We don't use your prompts or outputs to train models unless you separately and explicitly opt in to training. Saved history is its own opt-in, and turning on history doesn't opt you in to training. Each can be turned off at any time. If you opt in, your prompts and outputs may be used to train models by Fyber Labs, or models offered on Hypermesh. A training opt-in must describe what information will be used before you choose it.
- Turning training off stops future use. It doesn't by itself delete prompts and outputs you already submitted for training. Those are deleted when you request deletion or within 90 days after your account closes. To request deletion, email legal@hyperme.sh. Anything already used to train a model can't be removed from that model.
- Keep personal information out of prompts. Do not send secrets or regulated personal information. We do not promise automatic removal of personal information from prompts or outputs.
- Prompt research is an enterprise opt-in. An organization can opt in to contribute prompts to research. Where this feature is offered, personal information must be removed before a contribution may be used. Do not assume the Service automatically removes it from your prompts. It is off unless the organization turns it on. This is separate from saved history and from the training opt-in above.
- Organization screening is opt-in. An organization can turn on request screening for its own people and agents. It is off unless the organization turns it on. Screening by itself doesn't store requests.
- Paid retention (coming in v1). On the public Hypermesh network, AIuditor will store an organization's requests only if that organization turns on a paid retention policy. That policy isn't available yet. Turning it on doesn't mean we review the stored requests. Data stored under that policy may be disclosed in response to valid legal process. If an organization deploys AIuditor itself, a similar optional retention setting stays under that organization's control. Fyber Labs never sees or stores that data.
Safety screening on the public network. On the public Hypermesh network, we run automated screening on requests for these categories: child sexual abuse material, credible self-harm risk, malware or intrusion tooling aimed at others, and violent extremism. If a request is flagged, we may record that session (the prompt, the output, and related metadata) so we can review it and respond. Requests that aren't flagged aren't kept because of screening.
We report apparent child sexual abuse material to the National Center for Missing & Exploited Children (NCMEC) when we have actual knowledge of it, as 18 U.S.C. § 2258A requires. That is the only report we are required to make. We may share information with appropriate authorities in a life-threatening emergency, where permitted by law. We don't promise routine reporting of other flagged categories. We may also disclose information in response to valid legal process.
We don't monitor all traffic. Screening is applied on a reasonable-efforts basis, may from time to time be temporarily unavailable, and isn't guaranteed to run on every request. When screening isn't running, a request may still be served, and checks for child sexual abuse material still run. Screening can also miss content, so we don't guarantee it will catch every prohibited request.
Flagged records of apparent child sexual abuse material are kept for one year, or longer only for the anti-exploitation purpose the law allows, in secure storage, with access limited to people who need it for that purpose. Other flagged records are deleted automatically when the review closes, and no later than 30 days after the request was flagged. Access to those records is limited the same way. To prevent a delayed retry from restoring deleted content, we keep a random record identifier and its expiry, without the request text or account details, through the original retention period.
Hosts. Requests run on an enrolled host's hardware, so the host's machine processes your prompt and the output to run the request. Requests reach the host over an encrypted connection, and the model runs in a locked-down container with no access to the internet or the host's local network. Hosts must not log, inspect, copy, or keep your prompts and outputs beyond running the request, and must not tamper with the host software that enforces this. Certified hosts have the same protections as other hosts. Certified only means the host passed our certification checks.
Outside providers. If a Full Model request is sent to an outside provider, that provider's own terms may also apply, and your receipt will say so.
4. How we use information
- To run Hypermesh: accounts, sign-in, listings, reservations, checkout, leases, receipts, host checks, and payouts.
- To calculate and collect applicable US sales tax at checkout through Stripe, and to keep financial records.
- To send and receive wallet payments, match blockchain transactions to your account, and keep records of them.
- To have Stripe verify identity and screen payments, payers, and hosts against sanctions lists where required (host payouts, onramp purchases, and stablecoin payments).
- To keep the Service and hosts secure, prevent fraud and abuse, and enforce our terms.
- To run automated safety screening on the public network, and to review and respond to flagged sessions.
- If an organization opts in to request screening, to screen that organization's requests. Screening by itself doesn't store requests.
- If an organization turns on a paid retention policy (coming in v1), to store that organization's requests under the policy it chose. We don't review those stored requests just because the policy is on.
- If an organization opts in to prompt research, to use prompts for research only after personal information has been removed.
- If you opt in to saved history, to show you your history and for debugging and quality checks. That isn't training.
- If you separately opt in to training, to train models with your prompts and outputs, with personal information redacted or masked where possible.
- To monitor and fix the Service, including bugs you report.
- To contact you about your account, leases, payouts, and changes to our terms or this policy.
- To comply with the law.
We don't sell your personal information, and we don't share it for cross-context behavioral advertising. We never sell your prompts or outputs, and we don't use them to train models unless you separately opt in to training (see "Your prompts and outputs"). Uploading a model to run it does not grant permission to use it to train other models.
5. Who we share it with
- Stripe, which processes lease payments and refunds (stablecoin payments), runs the USDC onramp, calculates sales tax, and handles host payouts and onboarding (Stripe Connect), including identity, sanctions, and tax checks. Stripe receives payment, onramp, and identity data under its own privacy policy, and your billing address for sales tax. See stripe.com/privacy.
- Hosting and network providers: Microsoft Azure, which hosts the site, the portal, and our sign-in service, and Cloudflare, which runs DNS for all our hostnames. Traffic to hyperme.sh itself also passes through Cloudflare's network for delivery and protection from attacks. Portal and sign-in traffic goes straight to Azure.
- Email providers: Microsoft 365, for our inboxes, and Mailgun, for account emails such as password resets.
- GitHub, which hosts our public code and some software downloads.
- Sign-in providers (Microsoft, GitHub, Google), if you choose to sign in with them.
- Hosts. When you rent or send a request, the host's machine processes your work, including prompts and outputs, to run it. Hosts must not log, inspect, copy, or keep it beyond that. The host gets the lease and the model to run. It doesn't receive your name, email, or payment details. Because your work runs on a machine the host controls, someone with full control of that machine could technically see it.
- Public model providers. A request that no certified host can serve may go to a third-party provider, and your receipt will say so. That provider's own terms may apply. See the provider identified for your request and its privacy terms before sending personal information.
- IPinfo, to check which country a payment comes from so we can follow sanctions rules.
- Other users, only what's public: host listings on /nodes.
- Public blockchains. When a payment or payout is made from or to a wallet, the wallet addresses, amount, and time are recorded publicly on that blockchain, as with any blockchain transaction. We don't publish your name or account with them.
- Model training (only if you opt in to training). See "Your prompts and outputs" for who trains on what you allow.
- Authorities. We report apparent child sexual abuse material to NCMEC when we have actual knowledge of it, as the law requires. We may share information in a life-threatening emergency, where permitted by law. We may also disclose information in response to valid legal process, or to protect rights, safety, or the Service.
- A buyer or successor, if Fyber Labs is involved in a merger, acquisition, or sale of assets.
6. Cookies and local storage
- hyperme.sh uses local storage for display preferences and session storage to remember download-Terms acceptance. When you opt in to page experiments and product analytics, it uses first-party consent and assignment cookies, with a maximum lifetime of 24 hours. Short-lived security cookies protect that opt-in flow. Cloudflare may set a strictly necessary security cookie if it needs to check for automated traffic.
- The portal uses only cookies needed for sign-in and security:
- an encrypted session cookie that keeps you signed in, for up to 30 days;
- short-lived security cookies used while you sign in, which last minutes or until you close your browser;
- a cookie that remembers how you signed in, for 7 days; and
- cookies set by our sign-in service, which end when you sign out or within 10 hours.
- The portal also keeps your display preferences and the organization you picked in your browser's storage, on your device.
- Stripe's onramp and payout pages set their own cookies for payments and fraud prevention, under Stripe's policy.
Optional page experiments and product analytics are off unless you opt in. Where offered, use “Turn off page experiments and delete pending events” to withdraw. Experiment events contain bounded experiment and assignment identifiers and performance or outcome measurements, not prompt text, names, email addresses, or wallet addresses. Pending events expire within 24 hours or sooner when consent expires. First-party monitoring uses Azure Application Insights; GrowthBook supplies experiment configuration. Turning experiments off stops new optional collection and removes pending events; contact legal@hyperme.sh to request deletion of information already delivered. You can clear display preferences and download-Terms acceptance in your browser. Sign-in and security cookies remain necessary for the features you use.
7. How long we keep it
- Account information, including sign-in links to Microsoft, GitHub, or Google: kept while your account is active, and deleted within 90 days after the account is closed or deleted, except where the law or the other items in this list require us to keep it longer.
- Payment, order, invoice, payout, and tax records (including receipts), including the paying wallet address for each payment: 7 years, then removed unless a legal obligation requires continued retention.
- Billing address: kept while your account is active. Because it's part of your tax records, it's also kept with those records for 7 years.
- Linked wallet addresses: kept while they're linked to your account, and deleted within 90 days after you unlink them or close your account, except where they're part of a payment, payout, or tax record above. We can't change or delete anything already recorded on a public blockchain.
- Host status reports and check results: treated as account data, so kept while your account is active and deleted within 90 days after the account is closed or deleted, unless they're part of a payment, payout, or tax record above.
- Server, access, and security logs: We keep server, access, and security logs for at least one year to support security monitoring, incident investigation, and audits, and then delete or archive them under our retention schedule.
- Email you send us (sales@, info@, hello@, bugs@, legal@, and security@): 2 years.
- Prompts and outputs: not stored beyond what's needed to run the request. If you opt in to saved history, kept until you delete them, and deleted within 90 days after your account is closed. Turning history off stops saving new history.
- Prompts and outputs you submit under the training opt-in: kept until you ask us to delete them by emailing legal@hyperme.sh, or until your account closes; account closure deletes them within 90 days. Deleting or turning off saved history, or turning training off, doesn't delete them. Anything already used to train a model can't be removed from that model.
- Sessions flagged for apparent child sexual abuse material: kept for one year, or longer only for the anti-exploitation purpose the law allows, in secure storage, with access limited to people who need it for that purpose.
- Other sessions flagged by automated safety screening: deleted automatically when the review closes, and no later than 30 days after the request was flagged. Access is limited the same way.
- Requests stored under a paid retention policy (coming in v1): kept according to the policy the organization chooses. Turning the policy on doesn't mean we review those requests. They may be disclosed in response to valid legal process. Data in a self-deployed AIuditor is never seen or stored by Fyber Labs.
- Uploaded models (where offered): an uploaded model is kept only while it's in use. We delete it 1 year after it was last used, or within 90 days after your account is closed, whichever comes first. You can delete an upload yourself at any time. Uploads that fail our safety or format checks are deleted and aren't run. Models you link by URL are fetched when needed, and the copy is handled the same way.
8. Your rights
Depending on where you live, you may have the right to:
- know what personal information we hold about you and get a copy;
- correct it;
- delete it;
- receive it in a portable format;
- object to or restrict certain uses; and
- withdraw consent where we rely on it.
California residents (CCPA/CPRA and CalOPPA). This part is our notice at collection under California law. We don't sell your personal information, and we don't share it for cross-context behavioral advertising, as California law defines those terms.
Notice at collection. The categories below are what this policy already describes. We collect a category only when you use the feature it relates to.
- Identifiers and account information. Your email address, first and last name, a hashed password if you sign up with email, and, if you sign in with Microsoft, GitHub, or Google, the sign-in details described in section 3. We collect this from you and from the sign-in provider you choose. We use it to run your account, sign you in, set up organization access, and contact you. We disclose it to that sign-in provider, to Microsoft Azure and Cloudflare (which host and deliver the Service), and to Microsoft 365 and Mailgun (which send and receive email). We keep it while your account is active, and we delete it within 90 days after the account is closed or deleted, except where section 7 requires us to keep it longer.
- Billing address. Street, city, state, ZIP code, and country, collected from you. We use it with Stripe to calculate sales tax and to keep tax records. We disclose it to Stripe. We keep it while your account is active, and we also keep it with tax records for 7 years.
- Commercial and payment information. Reservations, checkouts, leases, receipts, payment amounts and tax, your registered wallet address and the signed message used to register it, and the payment details Stripe gives us (paying wallet, network, transaction ID, and amount). We collect this from you and from Stripe. We use it to run leases, take and refund payments, pay hosts, and keep financial records. We disclose it to Stripe. Wallet payments also appear on the public blockchain. Hosts don't receive your name, email, or payment details. We keep payment, order, invoice, payout, and tax records for 7 years. Linked wallet addresses are kept while they're linked, and are deleted within 90 days after you unlink them or close your account, except where they're part of those records. We can't change or delete data already recorded on a public blockchain.
- Host and device information (if you enroll a host). Hardware details, device registration, host status reports, check results, network information used to connect the host, and the public listing on /nodes. We collect this from you and from the host software. We use it to run hosting, checks, listings, and payouts. The public listing shows a hardware class, a short device ID, certification, and whether the host is online and selling, not your name. We treat this as account data: kept while your account is active and deleted within 90 days after closure, unless it's part of a payment, payout, or tax record.
- Payout identity and tax information (if you receive payouts). Stripe Connect collects identity and tax information, such as legal name, address, date of birth, tax ID, and bank or payout wallet details, under Stripe's privacy policy. The personal information Stripe returns to us is your name and billing information. Stripe collects identity documents, tax IDs and bank details through its own flow; it does not return those to us. We use this to pay you and to issue tax forms. We disclose it to Stripe. We keep payout and tax records for 7 years.
- Internet and network activity. IP address, browser type, pages requested, timestamps, and server, access, and security logs. We and our hosting and network providers collect this when you visit. We use it to run and secure the Service, investigate incidents, and support audits. We disclose it to Microsoft Azure and Cloudflare. We keep these logs for at least one year, then delete or archive them under our retention schedule. Cookies and local storage are described in section 6.
- Prompts, outputs, and uploaded models. Prompts and outputs are not stored by default. We keep them if you opt in to saved history or training, if an organization opts in to prompt research or turns on a paid retention policy (coming in v1), or if a request is flagged by safety screening, all as described in section 3. Uploaded models are kept only where that feature is offered. We collect this from you. We use it to run your request and for the opted-in or safety purposes described in sections 3 and 4. To run a request, the host's machine processes prompts and outputs, and a public model provider may receive a request that no certified host can serve. We may report apparent child sexual abuse material to NCMEC, and we may disclose information in a life-threatening emergency or in response to valid legal process, as described in section 5. Retention follows section 7: saved history until you delete it, and within 90 days after account closure; training data until you ask us to delete it or within 90 days after account closure; CSAM flags for one year, or longer only for the anti-exploitation purpose the law allows; other flags deleted when the review closes and no later than 30 days after flagging; paid-retention data according to the organization's policy; uploaded models for 1 year after last use or within 90 days after closure.
- Messages you send us. Email to legal@, security@, bugs@, sales@, hello@, or info@. We collect this from you. We use it to respond and to support the Service. We receive it through Microsoft 365. We keep it for 2 years.
Sensitive personal information. Where we have it, we use sensitive personal information only for purposes California law permits. That includes account sign-in information used to run your account. Stripe handles payout identity documents and tax IDs itself; the personal information it returns to us is your name and billing information. We don't use it to infer characteristics about you. You have the right to limit use that goes beyond those purposes. Because we already limit our use that way, we don't offer a separate "limit" control today. If that changes, we'll update this policy and provide one.
Your California rights. You have the right to know what personal information we collect, use, disclose, or retain, and to get a copy; to correct it; to delete it, subject to legal exceptions such as tax records; to opt out of the sale or sharing of personal information; and to limit the use of sensitive personal information. We won't discriminate against you for using these rights. You may use an authorized agent. We may ask for your signed authorization, verify the agent’s authority, and confirm the request directly with you. We verify identity using information already associated with your account, proportionate to the request; we do not require a new account. Never send us a password, private key, or seed phrase. Opt-outs of sale or sharing do not require identity verification.
Opt-out preference signals. We honor Global Privacy Control (GPC) and other legally recognized opt-out preference signals as requests to opt out of sale and sharing. This includes the Sec-GPC request header and navigator.globalPrivacyControl browser setting. Because we don't sell or share personal information for cross-context behavioral advertising, honoring a signal does not change our current practices.
Do Not Track and third-party tracking. We do not use advertising pixels or advertising session replay. Optional first-party experiments and product analytics are described in section 6. We don't change our collection practices in response to browser Do Not Track (DNT) signals, because we already don't track you for advertising. Cloudflare may set a strictly necessary security cookie. Stripe's onramp and payout pages set their own cookies under Stripe's policy. If you sign in with Microsoft, GitHub, or Google, those providers may set their own cookies. We don't control cookies on those third-party pages.
Virginia residents (VCDPA). If you are a Virginia resident, you have the right to access your personal data, to correct it, to delete it, to obtain a portable copy, and to opt out of targeted advertising, the sale of personal data, and profiling in furtherance of decisions that produce legal or similarly significant effects.
We don't sell personal data, and we don't use it for targeted advertising. We don't profile you to make legal or similarly significant decisions about you. Sanctions, fraud, and security checks described in this policy still apply.
We don't intentionally collect sensitive data as Virginia law defines it, such as health data, precise geolocation, or personal data of a known child. Hypermesh is only for people 18 and older. If you include sensitive data in a prompt or a message, we handle it only as described in this policy. Stripe may collect identity and tax information for payouts and onramp purchases under Stripe's policy. Before knowingly collecting or processing sensitive data where Virginia law requires consent, we obtain your opt-in consent. Do not send sensitive data in unsolicited messages or prompts.
Appeals (Virginia). If we deny your request, you may appeal by replying to our decision, emailing legal@hyperme.sh with “Privacy appeal” in the subject, or writing to the postal address below. Include the request date and explain why you disagree. We will decide the appeal within 60 days and tell you the result. If we deny the appeal, you have the right to submit a complaint to the Virginia Attorney General.
How to make a request. Email legal@hyperme.sh from the email on your account, or write to Fyber Labs TN LLC, Attn: Privacy Requests, 116 Agnes Rd, Ste 200, Knoxville, TN 37919. For access, correction, and deletion, we verify your identity using existing account information; we do not require identity verification for sale or sharing opt-outs. We'll respond within 45 days. If we need more time, we may extend once by up to 45 days, and we'll tell you why. Some information may be kept where the law requires it, such as tax records. If we deny your request, you can appeal by replying to our decision. Virginia appeals follow the process above. Requests by mail get the same verification, timing and appeal process as email.
9. United States customers only
Hypermesh is offered only to customers in the United States. We do not accept international accounts. We close international accounts immediately; those accounts are unpaid and receive no payouts or refunds, except where applicable law requires otherwise. See our Terms of Service. Privacy requests remain available through the contact methods in section 8.
10. Children
Hypermesh is only for people 18 and older. No one under 18 may use it or create an account, and we don't knowingly collect information from anyone under 18. If you think someone under 18 has given us information, contact legal@hyperme.sh and we'll delete it.
11. Security
We use encryption in transit (HTTPS), access controls, and secret management for our systems. Flagged safety records and other sensitive records are stored with access limited to people who need them for that purpose. Card and bank details for buying USDC are handled by Stripe. Hosts are independent, and no system is perfectly secure, so don't send secrets or regulated data through Hypermesh. Report security issues to security@hyperme.sh.
12. Changes
We'll post changes here and update the effective date. If a change is material, we'll give notice on hyperme.sh or by email before it takes effect.
13. Contact
Fyber Labs TN LLC, 116 Agnes Rd, Ste 200, Knoxville, TN 37919, legal@hyperme.sh.