Overview
This Privacy Policy describes how MemberConsole processes information when you use MemberConsole websites and connected account, authentication, checkout, order lookup, receipt, subscription, support, security, and merchant-integration surfaces. It is intended to explain the platform layer. It does not replace the privacy notice of the business that sells you a product or service.
MemberConsole is designed so a verified customer can access eligible purchases while participating merchants remain separated by authorization boundaries. The information available to a merchant depends on that merchant's own relationship to the transaction and its permitted integration scope.
MemberConsole and participating merchants
MemberConsole operates shared account and commerce infrastructure used by participating businesses. A merchant remains responsible for its own storefront, product or service, customer promises, merchant policies, fulfillment, and business records that it controls independently. Depending on the context and applicable law, MemberConsole and a merchant may have different responsibilities for information associated with the same purchase.
When you need help with product quality, delivery, warranty, returns, merchant refund eligibility, or merchant-specific subscription terms, the merchant shown on the connected order is generally the right contact. MemberConsole support handles problems with MemberConsole account access, order access, receipt visibility, and platform functionality.
Information we process
Depending on how you use the service, MemberConsole may process account identifiers such as name and email address; authentication, verification, and session information; billing and shipping contact details; merchant, product, checkout, order, and item identifiers; pricing and currency records; payment status and safe payment-method summaries; receipt, refund, subscription, shipment, and fulfillment records; support and sales communications; merchant integration settings; webhook delivery records; and technical information used to operate and secure the service.
Technical information can include browser or device characteristics, network information, request metadata, security events, service logs, timestamps, and other information needed to prevent abuse, investigate errors, maintain session integrity, and keep the platform reliable.
Payment information
MemberConsole interfaces are designed to expose safe payment summaries and payment state rather than raw reusable card credentials. Full card numbers, card security codes, or equivalent sensitive payment credentials should be handled by the configured payment infrastructure and should not be stored as ordinary MemberConsole application records.
Connected records may include payment provider references, status, amount, currency, timestamps, refund state, and non-sensitive method details needed for receipts, customer support, reconciliation, or transaction history.
How information is used
MemberConsole uses information to authenticate users; verify ownership before exposing private orders; connect eligible purchases to verified customer identities; create and maintain canonical commerce records; provide receipts, subscriptions, order history, and payment status; route checkout configuration; support merchant integrations; deliver signed merchant events; respond to support and sales requests; prevent unauthorized access and abuse; investigate errors; secure the platform; and maintain service reliability.
Information may also be used to satisfy accounting, transaction-history, dispute-resolution, fraud-prevention, security, and legal obligations that apply to the platform or a connected commerce record.
Cookies and local storage
MemberConsole may use browser storage, cookies, or similar technologies when needed for authentication, session continuity, security, preferences, and reliable operation of the website. Some authentication flows may rely on short-lived browser state so the service can safely complete a sign-in or order-access request.
You can use browser controls to clear stored website data, but doing so may sign you out or remove local session information. Clearing browser data does not by itself erase canonical commerce records that must remain associated with a transaction.
Retention
Retention depends on the type of record and why it is needed. Account-facing information may be retained while an account is active or as needed to provide the service. Commerce, payment, refund, receipt, fulfillment, audit, security, integration, and support records may be retained longer when reasonably necessary for transaction history, accounting, legal obligations, dispute resolution, fraud prevention, system integrity, or enforcement of agreements.
Removing an account-facing profile or browser session does not necessarily remove a transaction or security record that must be preserved for a legitimate operational or legal reason.
Security
MemberConsole uses layered controls designed around authenticated access, privacy-preserving order lookup, merchant isolation, row-level database authorization, server-authoritative pricing, scoped merchant credentials, signed event delivery, server-side handling of secrets, and auditable commerce records. These controls are intended to reduce unauthorized access and keep merchant and customer boundaries explicit.
No internet service can guarantee absolute security. Customers should protect their email accounts and authentication links, and merchants should protect server credentials and webhook secrets. Suspected technical vulnerabilities can be reported to security@memberconsole.com.
International processing
MemberConsole and its infrastructure providers may process information in more than one country depending on where systems, service providers, merchants, or customers are located. Where applicable law requires safeguards for international data transfers, MemberConsole will use the measures required for the relevant processing relationship.
Choices and rights
Depending on where you live and the applicable law, you may have rights relating to access, correction, deletion, restriction, objection, portability, or other privacy choices for information controlled by MemberConsole. Some requests may be limited where records must be kept for transaction history, legal obligations, security, fraud prevention, dispute resolution, or other legitimate purposes.
Requests concerning a merchant's own product relationship, marketing, fulfillment records, merchant tax documents, or merchant-controlled data may need to be directed to that merchant when it is the appropriate decision-maker. For MemberConsole privacy requests, contact privacy@memberconsole.com.
Children
MemberConsole is not intended for children to independently create merchant or commerce accounts where parental or guardian authorization is legally required. Participating merchants remain responsible for age-related requirements that apply to the products or services they offer.
Policy updates
This policy may be updated as MemberConsole features, infrastructure, service providers, or legal requirements change. The effective date shown at the top of the page identifies the current published version. Material changes may also be communicated through an appropriate account, website, or merchant channel when required.
Contact
For privacy questions or privacy requests relating to MemberConsole-controlled information, email privacy@memberconsole.com. For ordinary account, sign-in, order-access, or receipt support, use MemberConsole support. For technical security reports, email security@memberconsole.com.