Data minimization
Buyers can purchase without creating a seller account. Sellers provide account and wallet information needed to operate a storefront and receive settlement.
PRIVACY · MYSECRETPASS.LINK
Privacy Policy
MySecretPass.link processes information that is reasonably necessary to operate seller and buyer experiences while accounting for account-free purchases and the public nature of blockchain transactions. This policy explains what information may be processed, why it is needed, and what data can remain when anonymous purchases or crypto payments are used.
Purpose limitation
We use information for account operation, purchase access, payment verification, settlement, security, support and reliable service operation.
Account-free purchases
Buyer access may rely on a random browser-linked identifier plus order and receipt data instead of a traditional buyer profile.
Public blockchain data
Wallet addresses and transaction signatures recorded on-chain can be public and may not be erasable by MySecretPass.
01
Purpose and scope of this Privacy Policy
This Privacy Policy explains how MySecretPass.link processes information through the website, seller tools, public listings, purchase and payment flows, settlement, customer support and related operations. It applies to sellers, buyers, Affiliate and Referral participants, people who contact us, and other users of the service.
MySecretPass includes purchase flows that do not require a buyer account. As a result, we do not require the same categories of personal information from every user, and the information needed depends on the features a person chooses to use.
02
Privacy principles
We aim to minimize data where practical and use information that is collected or generated for purposes connected to providing the requested functionality or maintaining the safety and reliability of the service. Access to account, payment, settlement and support records is limited according to role and operational need.
The service can involve public blockchains and external infrastructure. We distinguish data we control inside the service from information already recorded on public networks, and we do not require a user’s private key or recovery phrase in order to provide privacy, access or settlement functions.
03
Information we may process and where it comes from
For sellers, we may process email address, account status and settings, nickname, profile and storefront information, listing and preview or media metadata, payout wallet addresses, sales and settlement records, and support records. Listing content or protected destination information may be stored, encrypted or delivered as needed to provide the service.
For buyers, we may not require account creation. We may process order identifiers, listing and price information, payment status, receipt data, a browser identifier used for purchase access, transaction signatures, payment addresses and assets, and other information needed to verify a purchase and provide access. Limited request timing, technical logs and network or browser information may also be processed for security and error diagnosis. Sources of this information can include information you provide directly, data generated by your browser or device when you use the service, public blockchain data, data received from payment or infrastructure providers, and reports or messages submitted by users or third parties.
04
Why we use information
Information may be used to operate seller accounts and storefronts, create and display listings, create purchase orders, detect and verify payments, provide digital access, settle sellers and program participants, display receipts and purchase history, and respond to support, reports and disputes. Seller account email may also be used for necessary service, operational and security notices and, where permitted by applicable law, promotional or marketing communications. If separate marketing consent is required, accepting this Privacy Policy or the Terms does not by itself provide that consent.
We may also use information to prevent or investigate automated abuse, payment fraud, self-referral or program manipulation, improve service reliability, security, incident response and feature quality, and preserve records reasonably required for legal obligations or protection of rights. The service also uses automated technical checks for payment state, attribution eligibility, rate limits and abuse prevention. These checks support transaction processing and security; users can contact support when an order, access or program attribution appears incorrect.
05
Account-free purchases and purchase access
Buyers can purchase public listings without creating a seller account. In that case, MySecretPass may associate purchase history or access rights with order data and a random browser-linked identifier rather than maintaining a traditional buyer profile.
If browser cookies or site data are deleted, or the buyer changes browsers or devices, the local purchase list or automatic restoration may be limited. Keep receipts and order information for important purchases. Even when support is available, browser identifiers that have been deleted cannot always be reconstructed.
06
Payments, wallet addresses and blockchain data
To process or verify crypto payments, we may process order amount, payment asset, destination addresses, wallet addresses, transaction signatures, block or confirmation status, and identifiers related to conversion and settlement. This information is used for payment verification, investigation of mismatches, settlement, accounting, security and support.
Wallet addresses and transactions recorded on public blockchains such as Solana can become publicly visible and, because of how those networks operate, cannot be deleted, modified or made private by MySecretPass. A wallet address does not necessarily identify a person by itself, but it may become linkable to an individual when combined with other public information.
07
Cookies and browser storage — baseline notice
MySecretPass may use cookies or browser storage technologies to maintain seller login sessions, support account-free purchase access, display purchase history, remember user-selected safety or display preferences, and attribute eligible Affiliate signups. Different storage items have different purposes and durations.
Post-level Referral does not depend on a persistent Referral tracking cookie; it is evaluated from an eligible Referral URL and the related order. Affiliate attribution, buyer identification, localStorage and sessionStorage can have different purposes and retention patterns by feature; additional information is provided where relevant in the service or this policy.
08
Affiliate and Referral attribution data
For the Affiliate program, visiting a valid Affiliate link (`/ref/:code`) can store the Affiliate code in a secure first-party HttpOnly cookie for up to 30 days. If that value is still valid when a new seller completes signup, it can be used to attach the referral relationship. An existing relationship is not arbitrarily overwritten, and self-referral is not eligible. When the signup flow consumes the attribution value, the Affiliate attribution cookie is cleared.
Post-level Referral works differently and does not use a persistent Referral tracking cookie. Attribution is limited to an eligible public listing with Referral enabled, a valid Referral URL, and server-side validation when the order is created. The order can snapshot the Referral ID, referrer, settlement wallet and reward amount and record the reward in a separate Referral ledger. A manually constructed URL is still invalid for self-referral, and when Affiliate and Referral are both independently valid their records remain separate.
09
Detailed cookie, localStorage and sessionStorage inventory
The table below describes the principal browser storage items currently used by the service. HttpOnly cookies are configured so ordinary page JavaScript cannot read them and use Secure and SameSite=Lax attributes. localStorage and sessionStorage are client-side browser storage and are affected by the user’s browser or site-data clearing controls.
The purchase-list localStorage can contain listing identifiers, title, type, price, payment time and, when available, order number, receipt number and transaction references needed to rebuild the local purchases interface. Clearing it does not itself erase blockchain transactions or server-side order and settlement records that must remain, but it can limit automatic restoration of the purchase list or browser-linked access on that browser.
STORAGE INVENTORY
Current browser storage inventory
Durations reflect current Max-Age values or browser-storage behavior and can end earlier if the user clears data or the relevant flow explicitly removes an item.
| Item | Storage | Purpose | Current duration / behavior | Effect of deletion or expiry |
|---|---|---|---|---|
| Seller login session | Cookie · __Host-msp_seller_session | Maintain authenticated seller session | Up to 30 days · cleared immediately on logout | The seller must sign in again. |
| Anonymous buyer identity | Cookie · __Host-msp_buyer | Associate account-free purchase access, buyer-scoped access grants and reviews | Up to 365 days | Automatic purchase access or restoration can be limited. |
| Affiliate signup attribution | Cookie · __Host-msp_ref | Connect a valid Affiliate link with an eligible new seller signup | Up to 30 days · cleared after the signup flow consumes it | A later signup may no longer be automatically attributed to that Affiliate. |
| Post-level Referral | No persistent cookie | Attribute a qualifying Referral URL to that specific order | URL + server validation when the order is created | Later purchases without the Referral ID are not automatically attributed. |
| Purchase list | localStorage · msp_purchases_v1 | Display the purchases list and receipt/access shortcuts on that browser | No automatic expiry · stores up to the most recent 500 entries | The local list is removed and browser-linked automatic access can be limited. |
| NSFW display preference | localStorage · msp_nsfw_enabled | Remember whether the user chose to display NSFW content | Until changed or site data is cleared | The display preference returns to its default state. |
| NSFW age confirmation | sessionStorage · msp_nsfw_age_ok | Reduce repeated age confirmation during the current browser session | Current session | A later session can require age confirmation again. |
| Payment confirmation UI timer | sessionStorage · msp_payment_confirm_deadline_<orderId> | Manage the roughly 10-minute confirmation timer shown in payment UI | Session-scoped · stored deadline is roughly 10 minutes | The UI timer can reset, but the order and on-chain transaction state are not changed. |
| Analytics consent choice | localStorage · msp_analytics_consent_v1 | Remember an explicit Google Analytics allow or reject choice when the visitor makes one | Until changed by the user or site data is cleared | If the preference is cleared, the site applies the regional analytics rule again: consent is requested where required, while analytics may load automatically elsewhere. |
| Google Analytics measurement cookies | Cookie · _ga, _ga_* | Distinguish visits, sessions and page usage after analytics consent | Up to about 2 years under current Google Analytics defaults · may refresh with use or configuration | Analytics measurement can stop or later visits may be counted as new visits. |
10
Third-party service providers and infrastructure
MySecretPass may use external infrastructure for specific service functions. The current architecture can include Cloudflare for web execution, D1 database, R2 storage, Queues and Access/security controls; Resend for email sending and receiving; NOWPayments for certain crypto payment routes; Helius for Solana payment webhooks and on-chain event verification; Solana networks and RPC providers; and Jupiter for certain asset conversions, settlement operations and Buyback-related swaps. Not every provider receives data about every user, and information is shared only as needed for the relevant function.
The infrastructure table below describes the principal data flows reflected in the current code and operating architecture. Wallet applications, public blockchain networks, and external websites, messengers or communities linked by sellers can operate independently from MySecretPass and may process information under their own privacy policies.
INFRASTRUCTURE & RECIPIENTS
Principal external infrastructure and data flows
Actual use depends on the feature and payment route selected. The list below reflects the principal services identifiable in the current code and deployment architecture.
| Service / category | Purpose | Information that may be processed | Role / note |
|---|---|---|---|
| Cloudflare | Web execution, D1, R2, Queues and administrator Access/security | Request metadata and account, order, support, uploaded-media or evidence data needed by the feature | Core hosting, data and security infrastructure |
| Resend | Login, operational and support email sending/receiving | Sender/recipient email address, email content, attachments and relevant account, order or support context | Only when an email sending/receiving feature is used |
| NOWPayments | Creation and status handling for certain crypto payment routes | Order/payment IDs, amounts, currencies, payment addresses, payment status and transaction hashes | Only for orders using that payment route |
| Helius | Solana payment webhooks and on-chain event verification | Public transaction signatures and on-chain transaction data plus webhook delivery metadata | Direct Solana payment detection and recovery flows |
| Solana network / RPC providers | Payment, balance, transaction and settlement verification or submission | Public wallet addresses, transaction signatures, token/account and block information | Public-network data can be visible on-chain |
| Jupiter | Certain asset conversions, operational SOL replenishment and Buyback-related swaps | Public wallet/token addresses, amounts, swap request and transaction information | Only when the relevant conversion or swap is needed |
| External wallets / seller destinations | Wallet signing or external links, messengers and communities selected by a seller | Information independently requested or collected by those services | Can be independent services governed by their own privacy practices |
| Google Analytics 4 (Google) | Measure consented visits, page flows and key product events | Page path and title, language, device/browser information, approximate region, feature events, and non-identifying transaction ID/value for purchase events | Optional analytics only. Email addresses, wallet addresses, search queries and Affiliate codes are intentionally not sent as analytics event data, and advertising features are disabled. |
ANALYTICS
Optional Google Analytics
For visitors in regions where consent is required for this analytics setup, including the EEA, United Kingdom and Switzerland, Google Analytics 4 is loaded only after you choose “Allow analytics.” In other regions, analytics may load automatically unless you previously rejected it or opt out through “Analytics settings.” Query strings are not sent as the page URL, and Admin pages, APIs, webhooks and static assets are excluded from analytics.
Advertising storage, advertising user data and ad personalization remain denied in every region. Google Signals and ad-personalization signals are disabled. You can change your analytics choice at any time from “Analytics settings” in the footer; choosing Reject denies analytics storage and clears first-party Google Analytics cookies used by this site.
11
Legal bases for processing
Where applicable privacy law requires a legal basis, MySecretPass may process information because it is necessary to provide the service or perform a contract with the user; for legitimate interests such as fraud and abuse prevention, security and reliable operation; to comply with accounting, tax, dispute or other legal obligations; and, where required, based on consent.
The applicable basis can vary with the type of information, the feature used, the user’s location and the governing law. Where consent is the basis, it may be withdrawn to the extent permitted by law without affecting processing that was lawful before withdrawal. If information is necessary to provide a requested feature, declining that processing can mean the feature cannot be provided.
12
When information may be shared or disclosed
Information may be shared with the service providers described above to the extent necessary to operate the service. Profile, storefront or listing information that a seller chooses to make public can be visible to general visitors. We may also disclose information when reasonably necessary to respond to law, court orders or valid government requests, or to protect the rights, safety or property of users, sellers, MySecretPass or others and to investigate fraud, security incidents or unlawful conduct.
If a merger, acquisition, restructuring or transfer of business assets actually occurs, relevant information may be disclosed or transferred as reasonably necessary for due diligence or continued operation, subject to safeguards and notices required by applicable law. MySecretPass does not need a private key, seed phrase or recovery phrase to process privacy requests or provide support, and users should never send those secrets to the service. Under the current service model, MySecretPass does not sell personal information or share it for cross-context behavioral advertising, as those terms may be defined by applicable privacy law, and does not use third-party advertising pixels. If that practice changes, this policy and any legally required choice mechanisms must be updated when required by applicable law.
13
Retention and deletion
Account, listing, support and security records may be retained for as long as reasonably necessary to provide the feature, operate the account and investigate issues. Order, payment, refund, settlement, Affiliate or Referral reward, and related financial or audit records may be retained longer than ordinary service data when needed for accounting, tax, disputes, fraud prevention, settlement reconciliation or legal obligations. We do not invent a fixed multi-year retention promise for server records where the implementation does not currently enforce one.
Browser-stored information can end earlier according to the inventory above or the user’s own clearing controls. Information that is no longer needed and is not required for legal or security reasons may be deleted or anonymized. Backup, log or abuse-prevention records can remain for a limited additional period, and transactions already recorded on a public blockchain cannot be erased by MySecretPass.
14
Your privacy rights and choices
Depending on applicable law, users may have rights to access or obtain a copy of personal information, correct inaccurate information, request deletion, restrict or object to processing, receive portable data, or withdraw consent. Sellers can manage certain account, profile, storefront and listing information directly through the dashboard, and users can use browser controls to delete or restrict cookies, localStorage and sessionStorage.
Privacy rights are not absolute and lawful exceptions can apply. For example, server records needed for settlement, accounting, fraud prevention, disputes or security may not be deletable immediately, and MySecretPass cannot modify or erase transactions recorded on a public blockchain such as Solana.
15
Privacy requests, verification and limitations
Privacy requests can be submitted through the official Contact page. For account-related requests we may ask for reasonable account verification such as the seller email; for order-related requests we may ask for an order number, receipt number, transaction signature or other information needed to locate the relevant record. If we cannot reasonably verify the requester, we may limit the response to protect other users’ information.
We will never ask for a private key, seed phrase or recovery phrase to verify a privacy request. To the extent permitted by applicable law, a request may be declined or limited when necessary to protect another person’s rights, comply with legal duties, preserve security or fraud-prevention records, resolve disputes or maintain record integrity. Where required by law, we will explain the basis and available appeal or complaint options.
16
International processing and transfers
MySecretPass is an internet-based service, and external infrastructure and public blockchain networks may process, transmit or store information in countries other than the user’s country of residence. Processing locations for Cloudflare, email, payment, blockchain and other infrastructure can vary according to each provider’s network and service configuration.
Where applicable law requires safeguards for cross-border transfers, we seek to use reasonable contractual, technical or other lawful measures appropriate to the processing. This policy does not promise an unverified single data-center country or identical storage location across all providers.
17
Security safeguards
MySecretPass uses technical and operational safeguards aligned with the current architecture, including transport security, Secure and HttpOnly cookies, server-side secret management, role-based administrator access, a Cloudflare Access boundary, audit records, server-side verification of payment and settlement state, and separation between the public web Worker and payout signing infrastructure. Certain protected content and sensitive operational information can receive additional access-control or encryption treatment depending on the feature.
No internet or blockchain system can guarantee absolute security. Users are responsible for protecting their email accounts, login credentials, wallets and devices and must never send private keys, seed phrases or recovery phrases to MySecretPass or a seller. Suspected unauthorized access or security issues should be reported through Contact as soon as reasonably possible.
18
Children and age-restricted content
The service is not directed to children under 13 in the United States and is not intended for anyone below the minimum age, digital-consent age or legal capacity required by applicable law to use the relevant features. NSFW, adult or otherwise age-restricted material may be accessed only by users legally permitted to do so where they are located, and sellers must not target minors with adult content.
A parent or guardian who believes a child under 13 or a person below the applicable minimum age has improperly provided personal information may contact us. If we obtain actual knowledge of a situation subject to special child-privacy requirements, we can review service-controlled records and take action required by applicable law where the record can reasonably be identified, but information already recorded on a public blockchain cannot be deleted by MySecretPass.
19
Changes to this Privacy Policy
We may update this policy when service features, external infrastructure, legal requirements or data-handling practices change. When we revise it, we update the “Last updated” date and, where required by applicable law or appropriate for a material change, may provide additional notice through the service or another reasonable channel.
As a general rule, the revised policy applies to processing from its stated effective date. Unless law requires otherwise, changing policy text does not retroactively rewrite finalized order financial snapshots or public blockchain records. Users should review this page periodically for material changes.
20
Contact and privacy operations
Questions about privacy, rights requests, account or purchase data, or security concerns can be sent to the MySecretPass.link operator through the official Contact page. For order-specific matters, including an order or receipt number when available can help locate the record, but never send a private key, seed phrase, recovery phrase or unrelated sensitive information.
If applicable privacy law gives a user the right to complain to a supervisory authority, that right remains available. While this policy does not currently display a separately verified legal-entity name, registered address or named data-protection officer, the official Contact channel is the operational point of contact for privacy matters; if verified legal-operator details are added, this policy should be updated accordingly.
MYSECRETPASS.LINK
Contact about privacy →Questions about privacy?
Use the Contact page for questions about privacy, purchase access or account data. For an order-specific request, include an order number or receipt information when available, but never send a private key or recovery phrase.