Stack & Sell XBack to site

Updated 6 November 2026

Privacy Policy

1. Who is responsible and how to contact us

Elizabeth Martin trading as Lizize Creates, Bakers Mill, Great Cornard, Sudbury, Suffolk CO10 0GG, England. Contact: lizizemartin@gmail.com.

Not VAT registered. No VAT is charged.

The seller is the data controller for operating Stack & Sell X. This notice describes verified application behaviour, not a completed data-protection assessment. Use the same email for privacy requests. The outstanding provider and retention disclosures below require owner verification.

2. Information processed by the app

Email is needed for purchases and access; relevant project input is needed to prepare a product. If it is not provided, those functions cannot be completed. Do not place other people's private information, children's identifying details or special-category data in prompts or uploads.

3. Purposes and lawful bases requiring confirmation

Account access, verified purchases, allowances, project creation, saved downloads and responding to service requests support the contract you request. Contract necessity is the proposed basis for those necessary activities. Security, fraud prevention and troubleshooting are proposed legitimate interests, subject to the owner's documented assessment. Applicable accounting or legal obligations may require certain transaction records to be retained.

Owner action required: confirm the actual lawful bases, legitimate-interest assessment, legal retention obligations and intended user age/safeguards. No basis for collecting sensitive personal data has been established. These are not blanket consent claims, and accepting terms must not be treated as consent for unrelated marketing.

4. Providers and recipients

The app retains provider references and operational evidence to recover saved work and avoid duplicate submissions. No assurance is made that AI processing is UK-only, never retained by providers or never used for provider training: the applicable accounts, contracts and settings need verification.

5. Cookies, browser storage and WordPress

The customer sign-in cookie is configured for a 12-hour session, HttpOnly, and Secure/SameSite=None on hosted connections to support embedding. Expiry of access is not proof of deletion of the database record. Browser session storage holds drafts, request/retry identities and interrupted purchase-return state; local storage is used for features such as prompt favourites.

No advertising or analytics integration was identified in the application code reviewed for this draft. That is not an audit of the WordPress host, hosting platform or provider checkout. The WordPress page embeds the app; its own cookies, plugins and any analytics require a separate review. Some browsers block embedded sign-in cookies and may need the existing new-tab sign-in fallback.

6. Retention and deletion — what is verified

Customer sessions expire after 12 hours and setup/recovery links after 30 minutes in the relevant code. These validity periods are not general record-deletion schedules.

The app has a seven-day file-expiry mechanism for specifically enrolled customer projects/files, with explicit timestamps and protections for historical, shared, test and completed-journey material. It is not a rule that every project or all personal data is deleted after seven days. Removing a project from the visible library is not necessarily physical erasure of its records or files.

No comprehensive automatic deletion period has been verified for accounts, payment history, project/operation records, logs, backups, support mail or copies retained by providers. The owner must establish and disclose retention periods or clear retention criteria for each. Existing saved work is not being deleted or reclassified by this policy change.

7. Security, locations and outstanding assessments

The code uses account-scoped access checks and private file storage. These measures do not guarantee absolute security. Processing regions, international-transfer destinations and safeguards, provider data-processing agreements/subprocessors, backup retention, any training-related settings and complete field-level sharing have not been verified. The owner must confirm them before treating this notice as complete; no UK-only hosting or specific encryption certification is claimed.

8. Your rights and complaints

Depending on the circumstances, UK data-protection law gives rights of access, correction, erasure, restriction, portability and objection. You may object to processing based on legitimate interests. Where consent is relied upon, you may withdraw it without affecting earlier lawful processing. Rights are subject to applicable exceptions, including lawful retention requirements.

Send requests to lizizemartin@gmail.com. Requests need appropriate identity checks and are handled manually, not through a promised automated deletion tool. Statutory response periods apply, normally one month with lawful extensions where applicable. You may complain to the Information Commissioner's Office (ICO); you do not have to contact us first.

9. Changes

Revisions should be dated and significant processing changes explained before they take effect where the law requires. Outstanding disclosures must be completed against actual business/provider arrangements, not assumed from typical provider practices.