Privacy Policy

Last updated: 4 November 2026

This policy describes how SpotMyPixel (SM SEAMLESS DIGITAL LTD) processes personal data when you use the website and related services. For cookies and similar storage, see the Cookie Policy.

We minimise personal data. We do not use advertising analytics pixels, session replay, or third-party marketing trackers on the SpotMyPixel site.

Who we are

The intended controller is the SpotMyPixel operator identified in the Terms. Privacy requests: Contact.

Data we process

  • Payments and billing location (Stripe). Checkout, billing details, and payment method data are collected and processed by Stripe. We require collection of a billing address at Checkout. After payment we may store billing country, region/state, city, postal code, and street address together with the country determined from your network connection (via Cloudflare), the state/province you selected (United States and Canada only), and the geographic eligibility decision. We store Stripe Checkout session and payment-intent identifiers, amounts, currency, and payment status. We do not store card numbers or CVV on our servers. Access to these records is limited to payment fulfilment, refunds, geographic eligibility review, and operators with admin access. Stripe creates and keeps your payment receipt and, for business purchases, your invoice (including the business name you enter at Stripe Checkout); we do not keep copies of these documents. See Retention below.
  • Tax and location evidence. To work out and document the VAT, GST or sales tax that applies, we record whether you bought as a consumer or business, the tax treatment and rate applied, and location evidence: the country determined from your network connection, the state/province you selected (United States and Canada), billing address details from Stripe, and the country of your card issuer where Stripe provides it. If you buy as an EU business we record the VAT number you give us and the European Commission VIES validation result (including any registered name returned by VIES). Where you are a consumer in the EU or UK we record your acknowledgement that the display starts immediately. Legal basis: legal obligation (tax law, including the evidence and record-keeping rules for electronically supplied services) and contract performance.
  • Withdrawal requests. If you use the withdrawal form we record the email address, order reference and optional name you submit, and whether it matched an order, and we send a confirmation email.
  • Affiliate accounts. Email address for magic-link login, referral code, session token hashes, login-token hashes, commission and payout records; your country (EU, Norway, Liechtenstein, United Kingdom or Switzerland); whether you joined as an individual or a company; the company name and VAT/tax number if you gave one; for EU VAT numbers the European Commission VIES result (outcome, date, and the registered name and address VIES returns), re-checked periodically; timestamps of your age confirmation (18+) and of accepting the Affiliate Terms and this Privacy Policy; daily counts of visits through your referral link (no IP address, cookie or visitor identifier is stored with them); records of payout-setup emails we sent you; and, once you set up payouts, your Stripe connected-account id, country, account type and status flags; and any invoice or earnings statement we attach to a payout. SMTP delivers login and payout-setup emails. A VIES outage is not treated as a successful check. Stripe processes affiliate identity, KYC, and payout details on Stripe-hosted onboarding. SpotMyPixel does not store affiliate bank account numbers, IBANs, card numbers, or identity documents. VAT and eligibility records are available to operators for approval, suspension, and accounting export. They are retained while the affiliate account and related commission/payout records are needed for accounting.
  • Administrators. Admin email in server-side sessions; password hash is stored in server environment, not in the buyer database.
  • Advertising images. Uploaded files are validated, re-encoded, stored on our hosting disk, and displayed on the canvas if published.
  • Destination URLs and scan metadata. Optional links, normalised and final URLs, redirect counts, page title, a short extract of visible text, and a content fingerprint may be processed to detect prohibited advertising. Full destination HTML is not stored as a page archive. Scan metadata may be retained with the placement or moderation attempt.
  • Automated content moderation (OpenRouter / Google Vertex). Advertising images and bounded destination-page fields may be sent to OpenRouter, which is configured to route classification to Google Vertex with zero-data-retention and no Google AI Studio fallback. We do not send buyer email, affiliate identity, Stripe customer IDs, IP addresses, or unrelated account information to that classifier. OpenRouter’s and Google’s processing is still a third-party processing activity. We do not claim that zero retention is guaranteed beyond that provider configuration and their terms.
  • Cloudflare Turnstile. Bot/abuse protection on the pre-payment content-check, purchaser image replacement, public placement-report form, affiliate sign-in and admin login. Cloudflare may process a token and related technical data. See also the Cookie Policy for third-party cookies that Cloudflare may set.
  • Purchaser management. After verified Stripe payment we store the Checkout customer email on the order so we can send a one-time magic link for image-only replacement. A hashed session token is stored server-side; the raw token is kept only in an HttpOnly cookie. We do not expose Stripe customer IDs or card details in that flow.
  • Referral attribution. If you consent to optional affiliate attribution, we may store a referral code in a first-party cookie. You may also type a referral code at checkout. Affiliates see aggregated purchase amounts and commission status, not purchaser payment identity.
  • Public reports. A category and optional message submitted with “Report this placement”, stored internally and grouped by placement and image revision for operator review. An anonymous first-party reporter cookie may be stored as a hash for duplicate-report prevention. Reports do not require an account or email address.
  • Admin moderation logs. Status changes, reason codes, and internal notes associated with the acting admin email.
  • Security / rate-limit keys. Client IP addresses may be hashed (HMAC) and used as short-lived rate-limit keys. Raw IP addresses are not stored on moderation or report rows. Rate-limit rows are deleted automatically after about 2 days.
  • Operational logs. Error tags and safe messages. We aim not to log raw tokens, session cookies, Stripe secrets, passwords, or full webhook bodies with unnecessary personal data. Intended log rotation is an infrastructure setting (about 90 days in operator docs), not a guarantee of deletion on a fixed public schedule.

After payment, the Stripe Checkout email may be used for a purchaser management session so you can replace artwork on placements you paid for. That session is scoped to paid orders for that email. Status is also shown via the Stripe checkout success flow using the Checkout session identifier.

Why we process data

To provide the canvas and checkout, take payment, moderate advertising content, operate affiliate commissions, secure the Service, and meet legal accounting and dispute needs.

Processors and hosting

Typical processors / subprocessors in the current architecture:

  • Hosting VPS (OVHcloud; data centre in Warsaw, Poland, EU) running the app, PostgreSQL, and upload disk
  • Stripe — customer Checkout, Connect onboarding/transfers, and webhooks
  • Configured SMTP provider (Purelymail) — magic-link, withdrawal-acknowledgement and affiliate payout-setup emails
  • Cloudflare — reverse proxy/CDN for all site traffic (including IP-based country detection) and Turnstile bot protection
  • OpenRouter — automated image and page classification, routed to Google Vertex as configured
  • Isolated URL-scanner service (our infrastructure) — fetches public destination pages

International transfers may occur where a processor is outside your country (for example Stripe, OpenRouter, Google Vertex, or Cloudflare).

Retention

  • Payment documents held by Stripe. Card details, payment receipts and business invoices are created and kept by Stripe under its own terms. We do not store card numbers, CVV or copies of Stripe receipts or invoices; we store only Stripe identifiers, amounts, currency and payment status.
  • Orders, tax and accounting records. Order and payment records, the purchaser email on the order, the tax treatment, VAT numbers and location evidence (including billing address details) are kept for as long as tax and accounting law requires: for sales declared under the EU One Stop Shop, 10 years from the end of the year of the sale; otherwise the period required by Cyprus tax and accounting law (generally six years from the end of the relevant tax year). When these periods end, the records are deleted or anonymised.
  • Affiliate commissions and payouts. Commission, payout and Stripe transfer records, and any invoice or earnings statement attached to a payout, are accounting records and are kept for the same periods. Other affiliate account details are kept while the account is open and afterwards only as long as those records need them.
  • Advertising images. Published images are kept while the advertisement is displayed. Images of advertisements that have been removed, and images replaced by a new upload, are no longer shown and are ordinarily deleted within 90 days, unless we need to keep them longer for a payment dispute, a legal claim or a report to the authorities. Images uploaded but never taken to payment are deleted automatically after about 90 minutes. Images from checkouts that were started but not paid are currently kept with the checkout record.
  • Sessions, tokens and security data. Affiliate sessions expire after about 14 days; purchaser management sessions and admin sessions after about 7 days; unused magic-link tokens after about 30 minutes; used login-token hashes are kept for about 7 days; rate-limit rows are deleted after about 2 days. Expired sessions and tokens are deleted automatically.
  • Other records. Withdrawal requests and placement reports are kept while needed to handle them and any related dispute; withdrawal requests that relate to a purchase are kept with that purchase's records. Records of expired unpaid checkouts are currently kept with the order records. Compliance monitoring alerts sent to our administrators do not contain customer personal data.

We do not claim universal zero retention. Provider zero-data-retention settings, where used, apply only to that provider’s described configuration.

Your rights

Depending on applicable law (including the GDPR where it applies), you may have rights to access, rectify, erase, restrict, object, or port personal data, and to withdraw consent for optional storage. Use Contact. You may also complain to a supervisory authority in your country of residence.

Children

The Service is not directed at children. Eligibility is described in the Terms.