What we do with your data

01 What we read from your store

We read the parts of your store that are already public. Specifically, the product and collection files a storefront publishes for anyone to fetch, and your sitemap.

• We never ask for admin access. No staff account, no app install with write permissions, no password to your store.
• We never ask for an API key to your store platform.
• We never see customer data. No orders, no names, no email addresses, no payment details. That data is not in the files we read, and we do not ask for it.

If a scan or a plan is ever wrong about what you sell, it is because the public catalogue said so. That is why the first step of every engagement is showing you what we read and asking you to correct it.

02 What we store

For a store we are working on, we keep the working set the platform needs to be useful the next time you log in:

• Your catalogue structure: collections, sub-collections and product counts.
• The keywords and topics we generated for you, and which ones your team marked as covered or done.
• Records of the posts and pages we audited, and the links you supplied for published work.
• Your account: an email address and a hashed password. We cannot read your password.

If you inquire through the site but never become a client, what we keep is what you typed into the form: your name, your email, your store URL, an optional phone or WhatsApp number, and your answers to the questions we asked.

03 Who else touches it

We use other companies to run the service. These are the only ones that any of your data reaches, and this list is the whole list:

We do not sell your data. We do not share it with advertisers. We do not pool one client's catalogue with another's, and nothing we learn from your store is used to build a plan for anyone else.

05 Training

We do not train any model on your data. We do not build models, and we do not contribute your catalogue, your keywords or your content to anyone else's training set.

We use our AI provider through its paid developer interface rather than a consumer chat product, because the terms are different and the developer terms are the ones written for handling someone else's business data.

Being confirmed. We are documenting our AI provider’s current developer terms on training and retention, and will state them here in full rather than summarizing them from memory. Ask us and we will send what we have today.

06 How long we keep it, and how to get rid of it

While you are a client, we keep your working set so the platform is useful. When an engagement ends, you can ask us to delete it and we will, along with the account.

Inquiries that never become engagements are kept while they are still live, and cleared out after that. You can ask us to delete yours at any point.

Email contact@citelx.com and say what you want removed. We will confirm when it is done. There is no form to fill in and no retention team to argue with.

07 What we never do

• We do not sell your data, to anyone, for any purpose.
• We do not use one client's data to serve another.
• We do not put advertising pixels or advertising trackers on this website. We use Google Analytics to count visits and see which pages are read, and it is not linked to any advertising account.
• We do not invent a statistic for your content. Where a real figure belongs, the brief leaves a gap and asks you for it.