What Rekhu keeps, and why

Charisma Design is the controller for the data about our customers, their users, sellers and visitors of rekhu.com. For the data of your own sites, your clients and their visitors that the Services handle on your instructions, you are the controller and we are your processor; the Terms and this policy together form the processing agreement.

• Account and users: company name and legal details (address, Chamber of Commerce and VAT number), your name, e-mail address, country, language, a hashed password, sign-in codes, and, if you switch it on, the secret of your authenticator app. Needed to run the account, sign you in and invoice correctly.
• Team: the e-mail addresses of the people you invite, their roles and the projects they may work on.
• Billing: top-ups, plans, usage per product, site and user, receipts, invoices and statements. Card details never reach us: payments run through Stripe.
• Sellers: the public name and link you choose, the roles you sell in, your Stripe Connect account id, and a record of accepting the seller agreement: the exact text, its fingerprint, your name and e-mail, the time, your IP address and browser. Stripe collects your identity and bank details on its own pages; we never see them.

• Projects: the site address, the hashed Key that links the Plugin to the account, conversations with the agent, files you upload (templates, notes, pictures), the knowledge, skills and facts kept per project, schedules, and the activity log of every change.
• Site data the agent reads while it works: pages, posts, menus, forms, plugins, themes, media and settings, as far as a request needs them.
• Who did it: the Plugin sends the name of the site and the e-mail address of the WordPress user who started a request, so usage can be shown per user.
• Usage: per request the model used, the tokens, the cost and the time, to bill it and show it to you.
• Model calls: what you ask, the instructions and site knowledge the agent needs, tool results and attached pictures are sent to the AI model provider (Anthropic) to produce the answer.

Each service is connected by the person who holds the account there, on that service's own screen. We never see the password, store the access encrypted (AES-256-GCM), and delete it the moment you disconnect.

• Google Search Console: through Google's sign-in, with read-only access (webmasters.readonly) to the property you pick: queries, clicks, impressions, positions and indexing state. We also receive the e-mail address of the Google account, to show who connected it. We use the data only to answer requests in that project, never write to Search Console, never share it, and never use it for learning or to train any model. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can withdraw access at any time at myaccount.google.com/permissions.
• Semrush and Ahrefs: your own API key, stored encrypted and used only for requests in that project.
• Slack and Discord: the webhook you add, used only to send the notifications you set up.

Rekhu gets better at a trade by learning from the work done in it. After a request is done, the Platform keeps an example of it: the request, the answer, the tools used and their outcome, and for designs the page and a picture of it, with signals of what worked (a thumbs-up, a publish, a report, a copy).

• Stripped before it is kept: e-mail addresses, phone numbers, web addresses and identifiers are removed, and your account is replaced by a pseudonym. Other personal details you type into a conversation can remain in the text, so keep personal data out of the chat where the work does not need it.
• What we make of it: knowledge, rankings and models of our own. To condense examples into knowledge, batches are processed by our model provider (Anthropic) under its commercial terms, which do not let it train on them.
• Never used: data from connected Google services, and designs offered in the gallery unless the designer chose to allow it.
• Switch it off: under Preferences → Learning in your account. From then on new work in the account is not kept for learning. Knowledge already condensed stays, because it no longer contains your content as such.
• We never sell examples, never publish them, and never show your content to another customer.

We announce a new sub-processor in the news before it starts.

• Account and project data: as long as the account is open.
• Conversations: until you delete them, and at most a year after their last activity.
• Working copies of a site's files: seven days, unless you keep them in the library.
• Connected-service access: deleted when you disconnect.
• Invoices, receipts and statements: seven years, as Dutch tax law requires.
• Seller acceptance records: as long as the seller agreement applies, and seven years after.
• Learning examples: as long as they are useful for training, under a pseudonym and without the identifiers listed in section 5.
• A closed account: deleted within thirty days of closing, except invoices and what the law requires us to keep.

You can see and correct most of your data in the account. You may also ask us for access, a copy in a common format, correction, deletion, restriction, or object to processing, including the learning in section 5. Write to hello@rekhu.com; we answer within a month. You can complain to the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens.

Everything travels over TLS. Passwords and Keys are stored as hashes, connected-service access encrypted, files privately. Sign-in uses a code by e-mail or an authenticator. Platform-to-site calls are signed. Access within our team is limited to those who need it.

rekhu.com sets only the cookies signing in needs: the session cookie, a protection against forged requests (XSRF-TOKEN), and, when you tick "remember me", a remember cookie. The account keeps some interface choices, such as an open panel, in your browser's own storage. No tracking, analytics or advertising cookies, and no third-party cookies.

The Plugin itself sets no cookies for your visitors. Forms you build may use Cloudflare Turnstile or Google reCAPTCHA when you switch them on; you are the controller for your visitors' data and for mentioning those services in your own privacy statement.

When this policy changes in a way that matters, we say so in the news and by e-mail to account owners before it applies.