Legal
Privacy policy.
How Canopy collects, uses, stores and shares information for sign-in, accounts, deposits and integrations, and how to manage your information.
Last updated 3 October 2026
1. About this policy
This policy explains how Canopy at canopypay.io handles information when you visit our websites, create or use an account, make a deposit through a business using Canopy, use our API, connect an AI assistant through our MCP server, or contact support. You can contact the Canopy team about your information at jack@canopypay.io or through our support form.
A business using Canopy decides why it takes your deposit and what it records about you in its own systems. Its privacy policy covers those activities. This policy describes the information Canopy receives and processes to provide deposit, routing and settlement services.
2. Google sign-in: access, collection and use
If you choose Continue with Google, Canopy requests the email and basic profile permissions needed to sign you in. Google provides a unique account identifier, your email address and its verification status, and basic profile information such as your name and profile photo when available. Canopy does not request access to your Gmail messages, Google Drive files, calendars or contacts.
Supabase, our authentication provider, receives and stores the Google identity and profile information in your authentication record. Canopy links that authentication identity to your Canopy account and uses your authentication identifier and email address to recognize you, create or access your account, maintain your sign-in session and send account or service emails. Google sign-in does not automatically publish your Google name, photo or email on a Canopy public profile.
Google authorization is handled through Supabase. The sign-in callback and authentication session may contain Google provider tokens. These are separate from the hashed API keys and MCP authorization tokens described below. The application does not use Google sign-in to read other Google products or to give an AI assistant access to your Google account.
Google identity information is processed by Supabase for authentication and storage, and by our hosting infrastructure as part of account requests. Resend processes the email address and message content needed to deliver service emails. For an embedded wallet, Canopy passes its application authentication identifier to Openfort to associate the wallet with the account; it does not pass the raw Google profile for that purpose. Authorized Canopy staff may access account information when needed for support, security or legal obligations.
We do not sell Google user data, use it for advertising or creditworthiness assessments, or use it to train AI models. We do not share Google sign-in data with an AI assistant simply because you connect that assistant to Canopy. We use and share Google sign-in information only to provide the account features you use, maintain security, respond to your requests or meet legal obligations.
Canopy’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. You can review or remove Canopy’s Google connection in your Google Account connections. Removing that connection does not delete information already held by Canopy or Supabase. To request its deletion, contact us as described in section 10.
3. Account and integration information
We store your account email address and its link to the authentication record. If you verify an email address with a one-time code, we store a hash of that code and its expiry. We also store account settings and the status of your account.
We store wallet addresses you connect or nominate, including a sign-in wallet, a default payout wallet, wallets that authorize payment routes and any embedded wallet identifier provided by Openfort. These identifiers are used to authenticate wallet-based actions, configure routes and deliver funds.
If you create a public profile, the username, display name, bio, links and wallet information you choose to publish are visible to visitors. Public profile information is distinct from the Google profile received during sign-in.
For integrations we store API credential records, webhook endpoints, encrypted webhook signing secrets, allowed website origins and related configuration. Secret API keys are stored as hashes and cannot be retrieved in their original form after creation.
4. Payments and public blockchain information
Payment records include the deposit address, destination wallet, relevant chains and tokens, any requested amount, payment status, references, metadata and the business’s identifier for its customer. Canopy checkout does not require the payer to provide a name or email address, but a business may include personal information in its customer identifiers or payment metadata. Canopy receives and stores that information when the business sends it.
When a deposit arrives, we record transaction hashes, sending and receiving addresses, token and amount, routing and settlement transactions, fees and the net amount delivered. We use these records to detect deposits, route funds, reconcile payments and display account activity.
The business that created the payment intent can view its payment status, deposit addresses, amounts and transactions, and receive webhook notifications containing payment identifiers, transaction details, fees, net amounts and its own reference or metadata. Blockchain and settlement providers receive the addresses, amounts and transaction details needed to monitor or carry out the transfer.
Blockchain transactions are public. Wallet addresses, amounts and transaction hashes can be viewed by others on the relevant network and may remain available permanently. Canopy cannot erase information written to a public blockchain.
5. AI assistants and Canopy MCP authorization
Canopy’s MCP server lets an assistant perform permitted account actions, such as creating a payment intent or reading payment status. Canopy receives the arguments sent in each tool call and returns the result to the connecting application. We do not receive the rest of your conversation unless the assistant includes it in the data it sends to Canopy. Payment references and metadata sent through a tool call may contain personal information.
If you connect an assistant through Canopy OAuth, we store the application registration details, redirect addresses, client metadata URL where applicable, the Canopy account that approved it and the permissions granted. Canopy authorization codes and access and refresh tokens are stored as hashes. Authorization codes expire after 60 seconds, access tokens after one hour and refresh tokens after 30 days, or earlier on revocation. Expiry limits their validity; it does not itself erase the stored records.
This authorization grants permissions for Canopy’s service. It does not grant access to Gmail, Drive or other Google APIs. The assistant provider processes your conversation and the tool results it receives under its own privacy policy. You control whether to connect it and what you ask it to send to Canopy.
6. Support, usage information and cookies
When you use the support form, we receive the name, email address and message you enter, together with any payment or account details you include. We use these to investigate and respond to your request. Resend processes the submitted information to deliver the support message. Avoid sending wallet private keys, recovery phrases or unnecessary sensitive information.
Our page-view logging records the page path, referring site’s host, whether a request appears automated and a pseudonymous visitor identifier. That identifier is a keyed hash derived from the request IP address and browser user agent. The raw IP address is not written to that page-view log. Hosting and security services also process request information such as IP addresses and browser details to deliver and protect the service.
We use Vercel Analytics for website usage measurements. Application logs record operational and error events to help us diagnose issues. Our application logging uses an allow-list of fields and truncates wallet addresses. We also count requests per IP address or credential in rate-limit counters that expire after two rate-limit windows.
We use cookies and authentication storage to keep you signed in and protect account actions. Wallet verification sessions expire after 15 minutes, account session cookies can last up to seven days, and Supabase authentication sessions are maintained and refreshed by its authentication system. Session expiry and signing out do not delete the underlying account or payment records. We do not use Google sign-in information for advertising or advertising tracking.
7. Why we use information and who receives it
We use information to authenticate account holders, issue deposit addresses, detect and route deposits, settle funds to the destination a payment intent names, calculate fees, notify the relevant business and provide account activity. We also use it to deliver support and service emails, measure website use, troubleshoot the service, prevent fraud and abuse, protect accounts and meet legal obligations. We do not sell personal information.
Service providers process the information needed for their role: Supabase for database storage and authentication; Vercel and Railway for hosting and background services; Axiom for application logs; Vercel Analytics for website measurements; Upstash for rate limiting; Temporal for job orchestration; Resend for email delivery; and Openfort for embedded wallets. Blockchain access and monitoring providers include Alchemy, Helius and other RPC providers. Relay, Circle and deBridge process relevant transfer addresses, amounts and transaction details when used for routing or settlement.
Providers receive information relevant to the service they perform, rather than unrestricted access to all Canopy information. A payment business receives its own payment records. An assistant receives the results of the Canopy actions you authorize. Authorized staff access information for operations, support and security. We may disclose information when required by law, to respond to valid legal process or to protect the service and its users from fraud or abuse.
Canopy and its providers may process information in countries other than the country where you live. Provider systems and the public blockchain networks used for a payment may operate across borders. You can contact us for information about the providers involved in your account or a privacy request.
8. Storage, retention and account closure
Account and authentication information is stored in Supabase. Payment records and integration configuration are kept in Canopy’s database, while operational logs and analytics are processed by the relevant providers listed above. We retain information to operate your account, provide and reconcile payments, investigate support or security issues and meet applicable legal obligations.
Email verification codes, rate-limit counters, sessions and Canopy MCP credentials have the expiry rules described above. An expired code, token or session can no longer authorize the relevant action, but expiry does not necessarily delete its database record or related logs. Operational logs and page-view records are retained for troubleshooting, security investigations and website measurement. Retention also depends on the provider storing them; contact us about a specific record or deletion request.
Closing an account marks it closed and unlinks its sign-in association. It does not automatically erase the account record, stored email address, authentication identity or payment ledger. There is currently no automatic erasure schedule for those closed-account records. They remain available for past-payment reconciliation, support, security and applicable legal obligations until a deletion request is assessed or a separate retention action is taken.
To request deletion, contact us using section 10. We will assess which personal information can be removed and which records need to be retained for the purposes above or legal requirements, and explain any limitations. Information already on a public blockchain cannot be removed by Canopy. Removing a Google connection or an assistant connector does not itself delete your Canopy account information.
9. Security
We use HTTPS for the public service and authenticated, account-scoped database access. Supabase encrypts stored customer data at rest and in transit, including the authentication and account information it holds for Canopy. We hash secret API keys, Canopy MCP credentials and email verification codes, and encrypt webhook signing secrets. Google profile information is stored as account data rather than as a hashed credential.
Access is limited according to account permissions and operational needs. No system can guarantee complete security. Keep your wallet keys, recovery phrases, devices and account access secure, and contact support if you suspect unauthorized access.
10. Your choices and privacy requests
You can update the account and public profile settings available in your dashboard and revoke API keys. You can remove the Google connection through Google Account connections. To disconnect an assistant, remove its Canopy connector in the assistant and contact Canopy if you also need its server-side authorization revoked. These actions are separate from a request to delete retained account information.
For access to your information, a correction, deletion or a question about retention, email jack@canopypay.io or use the support form. State the account email or relevant payment identifier and what you would like us to do. We may need to verify your authority over the account before providing or changing information. Do not send private keys or recovery phrases.
Depending on the law that applies to you, you may have rights to access, correct or delete personal information, restrict or object to processing, request a portable copy, withdraw consent where processing relies on consent, or complain to a privacy regulator. Contact us to exercise applicable rights. Some records may need to be retained for security, payment reconciliation or legal obligations, and public blockchain records cannot be erased.
Canopy is not directed at children. If you believe a child has provided personal information to Canopy, contact us so that we can investigate and handle it appropriately.
11. Changes to this policy
We may update this policy as the service or its data practices change. The date at the top identifies the latest version published on this page. We will notify users of material changes to how we use Google user data and obtain any required consent before using that data for a new purpose. Review this page for the current policy.
12. Contact
Contact the Canopy team at jack@canopypay.io or through our support form for privacy questions or requests. For a question about the business’s goods, services or reason for collecting a deposit, contact that business first. Include only the account or payment details needed to help with your request.