Privacy

Who we are

Channekt is a multi-channel commerce back office operated by AXICOM. Anything on this page, including a request about your own data, goes to support@channekt.com.

Controller and processor

Two different relationships, worth separating because different rules apply to each.

The account with us. Names, email addresses and the record of a subscription belong to the people who work at the merchant. For that we are the controller.

The merchant's customers. Everything arriving with an order from a shop or a marketplace belongs to the merchant. They decide what is done with it; we hold it to do the things they ask. For that we are a processor and act on their instructions.

What we hold

About the merchant

• the name and email address of each person given access
• a password, stored only as an argon2id hash, never in a readable form
• sessions, roles, and the record of what each person changed
• a subscription: the plan, its state, and Stripe's identifier for it

About the merchant's customers

Only what an order carries and a parcel needs:

• name, email address, telephone number
• billing and delivery address
• the channel's own identifier for that person
• what they bought, and for how much

Where it lives

Application and database	Google Cloud, europe-west2 (London, United Kingdom)
Database	PostgreSQL 17, reachable on a private network address only
Files and documents	Google Cloud Storage, same region
Transport	HTTPS only, everywhere

Data is encrypted in transit and at rest. Channel credentials get a second layer of their own: each is sealed with a key held outside the database, so a copy of the database alone yields no working token.

Who else is involved

Who	For what	Sees customer data?
Google Cloud	Hosting, database, file storage, TLS	Yes, it runs the database
Stripe	Subscription billing	No, merchant billing only
Email provider	Invitations, password resets, alerts	No, staff addresses only
AI provider	The in-product assistant	No, it is never sent an order

The connected shops and marketplaces are not sub-processors. They are the merchant's own accounts, and data moves between them and Channekt because the merchant asked for it to.

Who can see it, and who has looked

Access is by role. Every screen and every endpoint checks a permission, and a role without the right to read orders does not see an order: not in the interface, not in the API, not in the service beneath both.

Every read of a customer's personal data is recorded - who, when, from which address, and which records. Opening one order records that order; listing orders records the ones the list returned. So "did this member of staff look up this customer" has an answer rather than a count.

What is recorded is a pointer, never a second copy: an order id, not a name. A log holding the data itself would give an erasure request a second place to reach, and the newer one would be the one nobody remembered. A search term is never recorded either, because that is the one field which is itself often personal data.

The record is kept for twelve months and then deleted.

How long it is kept

For as long as the merchant's account is active. An order is a financial record, and a merchant has to be able to look up what they sold years later.

When an account is closed the data goes with it, save for what bookkeeping law requires be kept without it.

Erasure

When a marketplace tells us somebody has asked to be forgotten, the request is written down before it is attempted. A process that dies halfway leaves a record saying the erasure is still owed, and a sweep picks it up. Recording afterwards would lose the obligation on exactly that failure, and the channel, already told we heard, would never mention it again.

Identifying fields are tombstoned: the person disappears, the financial and stock records still add up. Nothing in that path writes the person into a log, because logs are the one store with no erasure path of their own.

Your rights

Under the UK GDPR and the GDPR a person may ask for a copy of their data, ask for it to be corrected or erased, object to how it is used, or ask for it to be handed to somebody else.

If you bought from a merchant who uses Channekt, that merchant is the controller: ask them, and we act on their instruction. A request made through a marketplace's own privacy tools reaches us automatically and is handled as described above.

If you work at a merchant, write to support@channekt.com. You may also complain to a supervisory authority.

Cookies

This website sets no cookies at all. No analytics, no tag manager, no third-party script. Its content security policy refuses them outright, so it is the browser enforcing it rather than a paragraph promising it.

The application at app.channekt.com sets what a signed-in session needs and nothing more: one cookie carrying the session, secure and http-only. There is no advertising cookie anywhere in the product.

Security

• passwords hashed with argon2id and checked against known breach corpora
• one organisation's rows are unreachable from another's session, enforced in the database rather than only in the code above it
• channel credentials sealed with a key the database does not hold
• every change recorded in an audit trail, with the person and the time
• a written incident procedure: the clock, containment, the queries that establish who saw what, and who is told

Security reports are welcome at support@channekt.com and acknowledged within one working day.

Changes to this page

When this page changes in a way that affects what happens to data, the merchants using Channekt are told before it takes effect rather than after. The date at the top is the date of the last change.