Privacy Policy

1. Who we are

Cremedyx is operated by CREMEDYX LTD, a company registered in Israel under number 517292207, at Hai El-Madares 141, Jerusalem 9709201, Israel. Contact: admin@cremedyx.com.

Cremedyx is a tool for merchants. It reads a merchant's own business data and helps them publish, reply to their customers, and understand what worked.

2. Two kinds of people, two different roles

This distinction decides everything else in this policy, so we state it first.

• Merchants — the businesses who sign up for Cremedyx. For their data we are the controller: we decide what we collect and why.
• A merchant's customers — the people who message that merchant or buy from them. For their data we are a processor: the merchant decides what is collected, and we hold and process it on their instructions. If you are one of these people, the merchant you contacted is your first point of contact, and we will support any request they pass to us.

3. What we store about merchants

• Account — email address, phone number, name, avatar, business name, business type, subscription plan.
• Business profile — business category, declared country and currency, goals, monthly budget, team size, language preference, notification preference.
• Business description for the AI — what you sell, to whom, and in what tone, as you entered it during onboarding.
• Connected channels — for each platform you connect: the access token, its expiry, and the page or account identifier. Tokens are held server-side only and are never sent to your device.
• Devices — push token, app version, OS version, device model, locale and time zone, so notifications reach the right device in the right language.
• Usage metering — model name, token counts and cost per AI request. This carries no message content and no personal data; it exists so billing can be explained.
• Billing records — invoice status, amount, currency, dates.
• Diagnostics and product analytics — when a crash or error occurs we record the error type, the app version and the device model. We also record which screens are opened and which features are used, so we can find what breaks and what confuses people. This is governed by consent switches in the app, carries no message content, and is never used for advertising.

4. What we store about a merchant's customers

Only what the merchant's own channels give us, and only so the merchant can serve them.

• Contact and order details — name, email, phone, address, city, country, any notes the merchant writes, order totals and history.
• Conversations — message content, message type, media links, timestamps, read state, and the platform's own message identifier.
• Conversation summaries — a short summary of a thread so the assistant can remember context between turns rather than restart every time.
• Engagement metrics — aggregate performance figures for the merchant's own public posts: reach, impressions, interactions and follower counts, as provided by the platform. These are aggregate figures about content, not profiles of individual viewers. We neither receive nor store data identifying who viewed a post.

We do not sell this data. We do not use it to build advertising profiles. We do not use one merchant's data to answer another merchant's customers.

5. Artificial intelligence, stated plainly

Some replies to customers are generated by AI, and some analysis shown to merchants is AI-produced.

When a customer is answered by AI, we tell them so. The first automated reply in a conversation identifies itself as an assistant and states that a person will follow up when needed.

When a reply is generated, the message text, recent thread history, and a bounded snapshot of the merchant's own catalogue and business description are sent to our AI provider for the sole purpose of producing that reply. When the assistant is not confident it does not guess: it stops, hands the thread to the merchant, and sends nothing.

We do not use customers' messages to train any model. Our AI provider is Anthropic. Under their commercial terms, data submitted through the API is not used to train their models, and we have additionally disabled model-improvement and feedback sharing at the organisation level. We do not send customer messages to any other AI provider.

Inputs and outputs may be retained by our AI provider for up to 30 days for safety and abuse monitoring, after which they are deleted. They are not used for training.

6. Improving our own models

We may use merchants' own business data — business descriptions, product catalogues, and a merchant's own conversations with the in-app assistant — to develop and improve Cremedyx's own models and features.

We never use a merchant's customers' messages for this. Customer conversations are processed only to produce a reply for that merchant.

Before any such use, data is stripped of direct identifiers. Merchants can opt out at any time in Settings; opting out applies going forward.

7. Where the data lives, and who else processes it

Our database and server functions run on Supabase infrastructure in the Singapore (ap-southeast-1) region. We say this plainly because it matters: for users in the European Economic Area this is a transfer to a third country, made under the European Commission's Standard Contractual Clauses as incorporated in our providers' data processing terms.

Data in transit is encrypted with TLS. Data at rest is encrypted by the hosting provider. Provider access tokens are further restricted so that only server-side functions can reach them: no client application can read a token, and no client application can write one.

Our processors:

Each is used for the stated purpose only.

We do not embed advertising SDKs, we do not sell or share data for advertising, and we do not collect an advertising identifier. We use Firebase for crash reporting, performance monitoring and product analytics on both iOS and Android, governed by the consent switches in the app. Firebase receives technical and usage signals only — never message content, never customer contact details, and never catalogue data.

8. How long we keep it

Account and business data are kept while the account is open. Conversations and orders are kept while the account is open, because the merchant needs their own history.

When an account is deleted, deletion is immediate and cascading, not a flag. What survives is narrow and named: invoice and subscription records required for accounting are retained under a one-way cryptographic digest, so the figures remain auditable while the person is no longer identifiable from them. Uploaded files are queued and removed through the storage provider's API.

9. Your rights, and how to actually use them

Under Israeli privacy law and, where it applies to you, the GDPR, you may request access, correction, deletion, restriction and portability, and you may object to processing.

• Deletion — a merchant can delete their entire account inside the app, in Settings. It takes effect immediately and needs no email to us. Instructions are also published at https://cremedyx.com/delete-account.
• Everything else — write to admin@cremedyx.com. We answer within 30 days.
• If you are a customer of a merchant — contact that merchant. They control the data. Pass us their request and we will carry it out.

10. Children

Cremedyx is a business tool and is not directed at children. Accounts require the user to be at least 18, or the age of majority where they live.

11. Security incidents

If a breach affects your data and creates a real risk to you, we will notify you and the competent authority within the time limits the applicable law sets, and we will tell you what happened rather than what is comfortable.

12. Changes

If we change this policy materially we will notify merchants by email or in the app at least 30 days before it takes effect, and the date at the top of this page will change.

13. Contact

CREMEDYX LTD
Hai El-Madares 141, Jerusalem 9709201, Israel
admin@cremedyx.com
+972 52-220-5143