SMART COD AI · Last updated · 23 October 2026

Privacy notice

How account, store, support and measurement data are used.

Who is responsible

The provider trading as Excellum, identified above, is responsible for account administration, billing, support, security and website measurement, and for the purposes and means of its shared-network processing. Each merchant is responsible for its store transactions, the data it supplies and its checkout policy. Where we process data solely on a merchant’s documented instructions, the processor requirements and the relevant processing arrangements apply. Responsibilities are determined by the particular activity, not a blanket label. Contact info@woosmartcod.com about data held by Smart COD AI.

Account and payment information

We process email, password hash, account and store identifiers, billing contact/address, tax details, subscriptions, payment references and correspondence to provide the account and service. Passwords are not stored as plain text. Stripe handles card details; we do not receive the full card number or security code. Contract necessity applies where appropriate, legal obligations to required tax records, and assessed legitimate interests to security and abuse prevention. Marketing measurement uses separate consent.

Shopper and tracking data

Connected stores send the checkout attributes needed by enabled rules, pseudonymised identifiers, order references, status/lifecycle events and available courier/tracking references. Rule context may include shipping selections, cart and product attributes, coupon matches and payment-attempt information. Certain private rule values use store-specific digests. Pseudonymisation is not anonymisation: matching data can remain personal data. Tracking numbers remain usable for courier queries. Legitimate interests support the delivery-history protection described in the network notice; merchants provide the corresponding shopper information. Shared history and courier findings remain distinct sources. Missing tracking, courier loss or an inconclusive response is not evidence of customer refusal.

Support and attachments

Support messages and optional files are available only to the ticket owner and authorised staff. Up to four PNG, JPEG, WebP, PDF or text/log files are accepted per message, with size/type checks and downloads rather than public publication. Files are not attached to notification emails. Redact unnecessary shopper details and never send credentials or card details. Support data is used to respond to requests and maintain a record of service communications. Cloudflare Turnstile protects supported forms against abuse using verification tokens and related technical information; it is a security control, separate from optional analytics consent.

Indicative country and display currency

When the plugin or session does not provide a store country, we estimate a country from the connection IP using a local DB-IP Lite database on our server. We do not send the IP to an external geolocation service, and this lookup does not retain it in an additional access log. We use only a country hint for currency and network information, without precise location or changes to billing country and tax. Country and currency preferences stay in the browser session. If unavailable, we use limited browser language or time-zone hints for India, or display EUR and the global network. An IP may indicate a VPN or proxy country. Country data: DB-IP Lite, Creative Commons Attribution 4.0, https://db-ip.com.

Analytics and advertising choices

Essential storage supports login, security, checkout and cookie choices. We use advanced Google Consent Mode: site pages send limited page/plan events and consent signals without analytics or advertising cookies before a choice or after rejection. These signals support aggregate measurement and modeling, not a complete visitor count. Analytics cookies and client identifiers require analytics consent; advertising cookies, retained click identifiers and a SHA-256 hash of a normalised checkout email require marketing consent. Hashing does not make an email anonymous. Email hashes go only to Google Ads, not GA4; fresh marketing consent under the email-use notice is required. Account, checkout and other private pages send only their fixed page type, without account details, form contents or URL tokens. Trial start and the first confirmed positive payment are separate Stripe-verified events; a trial is not a purchase. Both are reported only from our server, including the first charge after a trial; no browser return is required. With valid analytics consent, we use the permitted client identifier captured at checkout. Otherwise, limited trial-start and first-payment reporting continues using new random identifiers for each upload only. We do not retain or reuse these random identifiers. Reports include event time, public plan, currency, net amount and tax; trials have zero value. They exclude customer IP, contact details, email hashes, account or Stripe identifiers, session identifiers and advertising click IDs. The random identifiers cannot link an event to a previous visit or campaign, or a trial to its later payment, and may affect GA4 visitor counts. Rejecting or withdrawing optional analytics stops the use of optional identifiers; this limited trial-start and first-payment reporting continues. Uncertain deliveries are held for review rather than automatically repeated. Your billing records remain complete. Manage optional categories through Cookie settings in the footer.

Recipients and international processing

Data is accessible to authorised staff and providers needed to operate the service: DigitalOcean for hosting, Resend for transactional email, Stripe for billing, Cloudflare for form security and Google for website measurement as described above. Supported couriers receive the tracking requests needed for shipment checks. Other merchants do not receive source-store identities or raw shopper contact details through network results. Providers may process data outside the EEA. Such transfers are subject to the applicable data-protection requirements, including adequacy decisions or appropriate safeguards such as standard contractual clauses where required. Contact us for information about the recipients and transfer safeguards relevant to your data.

How long information is kept

Support attachments expire after 90 days and are removed by scheduled cleanup. Measurement contexts expire after 180 days; advertising click identifiers have a 90-day use limit. These periods do not apply to every record. Account information, support messages, billing records, decision records and shared history are retained according to the service purpose, continuing relevance, relationship with the account holder and applicable legal or dispute-related needs. Account closure or disconnection does not automatically erase all past records. Requests for erasure or restriction are assessed for the relevant dataset, including any legal preservation obligation. Contact us for the period or criteria applicable to a particular record.

Your rights and complaints

Depending on the processing and applicable law, you can request access, correction, erasure, restriction or portability, object to legitimate-interest processing and withdraw consent without affecting earlier lawful use. Contact info@woosmartcod.com; we may need proportionate verification and help from the relevant merchant to identify pseudonymised records. GDPR requests normally receive a response within one month, with lawful extensions where applicable. You can complain to the Hellenic Data Protection Authority or another competent supervisory authority. Rights can be limited by applicable legal obligations; an automated adverse outcome should have an appropriate challenge route.