Cartdini privacy notice

Who is responsible?

This notice covers the Cartdini website, staff workspace and requested Pro licence service. The legal seller and website operator is A.M.E.X. Internet Marketing ltd.

Makariou III, No.9, Larnaca, 7530, Cyprus

Privacy and support contact: Show email Email us for setup, billing or privacy questions.

If a shop uses Cartdini checkout fields, that shop controls the customer information collected through those fields. Contact that shop about its checkout data.

Optional visitor analytics

Analytics is off until the site operator enables it and you choose Accept analytics. Rejecting has no effect on access to the website or purchases. Use Privacy choices in the footer at any time to reject analytics or withdraw consent. We also treat Global Privacy Control and Do Not Track signals as a request to keep optional analytics off.

With consent, we count visits to public pages, daily unique browsers and approximate countries supplied by our hosting network. A country estimate can be affected by VPNs or network routing; it is not GPS or a precise address. Daily browser counts are estimates, not counts of identified people.

Our analytics database does not store your full IP address, email, browser user-agent, query strings, full referral URLs, form contents, payment information or license key. We do not join these counts to staff accounts, purchases or licenses. We do not run advertising pixels, sell analytics profiles, track across websites or automatically subscribe visitors to marketing. Administration, payment confirmation and customer download pages are excluded from optional analytics.

Cookies and browser storage

Stripe and the hosting platform may use their own necessary technologies when you use their hosted services, including a private-site access gate. Their notices apply to those services. Clearing necessary cookies may sign you out or interrupt payment confirmation. Optional analytics stays off if preferences cannot be loaded reliably.

Purchases, billing and downloads

Stripe processes card payments and subscription billing. Card numbers and security codes do not enter this website’s database. We retain purchase, customer, subscription and invoice identifiers, the selected plan/site allowance, amount, currency, paid period, access status and a hashed download-key reference. Authorized support staff can request the customer name and email from Stripe when handling a purchase. Download access is verified with Stripe; owners can record support notes or suspend access and replace compromised keys.

Accounts, service emails and support

Authorized staff use a protected workspace. It retains staff account and role details, password hashes, sign-in and session records, and administrative audit records used to control access and protect the service.

Requested customer-account emails and newsletter messages use our GoDaddy VPS mail service and its outbound relay. Account access and support do not subscribe you to marketing. Newsletter signup requires separate confirmation; see the newsletter privacy notice.

Support stores the subject, messages, contact details, staff replies and conversation history. OpenAI assists staff with spam assessment, summaries and reply drafts. A staff member must approve a reply before it is sent. The workflow omits structured contact fields, private staff notes and ticket-access tokens from prompts, and applies redaction to recognized credentials and contact details in message text. API responses are requested without storage; this does not establish a zero-retention policy for all provider processing. Read the support privacy notice before submitting a request.

Cartdini on a WordPress shop

Checkout field values and settings stay in the shop’s WordPress database. Cartdini Free sends no usage telemetry to us. Cartdini Pro needs one successful, explicit licence activation before editing and tools unlock on a new site. Saved checkout rules do not depend on a live licence connection. Once earned, the local unlock survives expiry and outages; disconnecting locally locks editing again without deleting rules or order answers.

Inside the plugin, Pro preview navigation preferences and an explicitly chosen task are stored locally in WordPress user metadata for each administrator and store. A chosen task expires after seven days. Existing browser draft recovery and contextual suggestion preferences remain local. Optional usage counts are off by default; if enabled, preview opens, pricing-link clicks and matching workflow saves are counted locally and expire after 90 days. Expired tasks and counts are scheduled for removal through WordPress cron while the plugin is active and are covered by personal-data export and erasure. Turning counting off clears those counts. No shopper answers, checkout content or licence keys are recorded for this purpose, and no guidance preferences or counts are sent to Cartdini. These are plugin action counts, not purchases or a paid upgrade rate.

The Pro licence connection starts only when a WordPress administrator enters a purchase key and authorizes the disclosed communication. Connection, manual checks, daily scheduled checks and an authenticated Pro update download send the shop URL, a random installation identifier and Cartdini Pro, WordPress, WooCommerce and PHP versions. We retain connection status and successful check-in times to enforce the purchased update/support site allowance and help diagnose service problems. No checkout fields, orders or shop customer data are sent. Update downloads also send the requested release version. The updater verifies the downloaded package locally; Cartdini does not enable automatic installation.

The purchase key is exchanged for a restricted installation token. The token is encrypted locally using the shop’s WordPress security salts; its hash is stored by the license service. Successful Disconnect releases the site seat and locks Pro editing. Removing the local connection locks editing and stops future checks, but the owner must separately free the seat on the server. A site-bound local record preserves an earned unlock across subscription expiry, service outages and WordPress salt changes; it is removed when the local connection is removed. Deactivating Pro stops its scheduled checks. Uninstalling removes local connection credentials; checkout configuration and order values are retained.

Why we process information

Optional analytics relies on your consent, which you can withdraw through Privacy choices. Account access, payment fulfillment, downloads, requested communications and license support are used to provide the service you or your organization requests. Security and access records support our legitimate interests in preventing abuse and operating the service. Financial records may also be retained to meet applicable legal obligations. Annual Pro plans are available through the pricing page; this notice does not enable payments or change accepted purchase terms. Contact our support team for information about the processing of your data.

Retention

Analytics event-deduplication records expire after 24 hours, daily pseudonymous browser records after 31 days and aggregate page/country counts after 395 days. Expired records are removed in bounded cleanup batches during use of the service; expired aggregates are excluded from reporting. Withdrawal stops future analytics and removes the browser identifier; prior aggregate counts are not reversed.

For customer accounts, cleanup rules remove expired access tokens seven days after expiry, sent or cancelled account-email records 30 days after creation, and customer security-event records after 180 days. Session validity and cleanup are separate: expired or idle customer sessions are no longer accepted even before their stored records are removed. These rules do not set a retention period for purchases, licences, support conversations or recovery backups.

Newsletter confirmations expire after 48 hours. Confirmed subscriptions expire after 730 days; withdrawal removes the usable email address and retains a suppression record for up to 180 days. These are the newsletter service’s configured lifetimes and cleanup rules, not a claim that every copy is deleted at the same instant. Read Newsletter choices, browser storage and retention for the separate service details.

We keep information needed for an active account, purchase, licence or support entitlement. Closed or no-longer-needed account details are reviewed monthly and removed or anonymised when no continuing purpose applies. Not signing in does not cancel a valid licence. Minimal licence, withdrawal, revocation and legal records are considered separately. A scheduled review is not a promise that every category is deleted automatically.

Ordinary support conversations and attachments are scheduled for deletion 12 calendar months after both resolution and the last meaningful contact, using the later date. Open cases, privacy requests, disputes and documented legal holds are excluded while needed. Older cases without a reliable closure date receive a conservative review date; they are not treated as already expired. Direct mailbox copies linked to a resolved case follow that case. Standalone correspondence is reviewed and recorded before deletion, rather than guessed to be resolved from its age.

Necessary invoices and accounting/payment records follow our six-year company schedule, starting from the relevant tax-return filing deadline or actual filing date, whichever is later. Amended returns, applicable extensions, audits, disputes and documented legal holds can extend this period. Filing dates and exceptions are reviewed; this is not automatic deletion six years after purchase and does not apply to every account or support field.

Routine recovery copies managed by our VPS cleanup are subject to a rolling 35-day retention target, with protected recovery and deletion/revocation records and documented holds handled separately. Failed jobs, outages or locks can delay expiry and require follow-up. Accepted deletions and withdrawals must be reapplied before restored data returns to service. Encrypted archives held on the operator’s protected computer are reviewed separately; no verified fixed expiry is claimed for those copies. This VPS schedule does not cover the hosting provider’s own snapshots, provider logs, a merchant’s WordPress backups or independently retained provider records.

Service providers and international handling

We use a shared platform for our plugin businesses. Access and purposes remain separated by brand; contacting one brand does not subscribe you to another. Our company is based in Cyprus, and our VPS is in the United States. Providers can process information internationally. The list below distinguishes our own retention rules from provider-managed copies. Contact our support team for the safeguards applicable to your request.

GoDaddy — VPS hosting and mail

Hosts the website, application databases and our mailboxes; its outbound relay carries requested customer-account, newsletter and support emails.

Information: Website requests, stored account and support records, correspondence and delivery details needed for these services.

Location: Our VPS is in the United States (US West in the retained hosting account record). Provider administration, support access and onward processing can occur in other locations; no EEA-only restriction is claimed.

Terms and transfers: The GoDaddy DPA takes effect with its applicable service agreement and includes terms for restricted international transfers. The linked terms explain the available safeguards; a service location is not a complete transfer assessment.

Retention: Our application/mail and managed-backup rules are described in the privacy notice. GoDaddy-managed snapshots, delivery/security logs and account records have separate provider rules; we have not verified a fixed expiry for every provider copy.

Provider processing terms

OpenAI — support assistance

Assesses spam, summarises support issues and prepares draft replies for staff review. A member of staff approves a reply before sending. It does not receive a shop’s WordPress customer database through normal plugin operation.

Information: Limited support subject and message text after configured redaction; structured contact fields, private staff notes and ticket-access tokens are excluded from prompts. Unnecessary shopper data and secrets should not be supplied.

Location: International processing may include the United States. We do not claim EU-only processing or a special zero-retention account arrangement.

Terms and transfers: OpenAI’s Services Agreement incorporates its DPA; that DPA provides EEA/Swiss transfer safeguards using contractual clauses or an applicable adequacy decision. The applicable contracting entity follows those terms.

Retention: We request API responses without application storage. This is not zero retention: default abuse-monitoring records may be held for up to 30 days, with stated legal/security exceptions. Our own ticket summaries and drafts follow the support-case rule.

Provider processing terms

Stripe — payment and billing services

Hosted payment and billing processing where an existing purchase or service uses Stripe. Cartdini Pro plans use Stripe-hosted checkout. We do not receive card numbers or security codes.

Information: Customer billing/contact information, payment details and provider purchase/subscription references as needed.

Location: International processing under Stripe’s applicable service and privacy terms; no EU-only processing claim.

Terms and transfers: Stripe’s DPA is incorporated in its service terms and includes transfer provisions. Stripe acts as processor for some services and as an independent controller for its own fraud, security and legal purposes.

Retention: Our necessary accounting records follow the company schedule above. Stripe separately retains information required for its own services and legal duties; closing our account does not automatically erase Stripe’s independent records.

Provider processing terms

OpenAI API data controls · Stripe privacy · Newsletter privacy · Support privacy

Your rights and requests

Depending on your location, you may be entitled to access, correct, delete, restrict or obtain a portable copy of your personal information, object to certain processing, withdraw consent or complain to a data-protection authority. Contact the published privacy/support address. We may need to verify your identity and explain records that must be retained. Do not email passwords, recovery codes, full card details or license keys. A request concerning a shop’s checkout data should go to that shop.

We will update this notice when practices change. Changes to this notice will explain new collection before it begins. This notice describes the implemented service; it is not a certification of legal compliance.