Privacy Policy

Effective and last updated: 7 November 2026

1. Who we are

Amadalis Capital LLC, a Wyoming limited liability company ("Amadalis", "we"), runs amadalis.ai and Praxis, our platform.

This policy says what personal data we handle, why we handle it, and what you can do about it.

Write to us about your data at support@amadalis.ai.

Amadalis will appoint an EU and UK representative before offering paid plans in those regions; until then, write to support@amadalis.ai.

2. Three groups of people

  1. Visitors to amadalis.ai, our own website. We decide what is collected, so we are the controller.
  2. People who hold a Praxis account, and the members of their teams. We are the controller of account data.
  3. Visitors to our customers' sites. Each customer decides what its site collects. The customer is the controller. We process that data for the customer, on its instructions. Section 7 explains what that means for you.

3. Visitors to amadalis.ai

Our website is built and hosted on Praxis, in our own CMS, and follows the same consent rules as every Praxis site. Until it moves to amadalis.ai, it is served at amadalis-hq.sites.amadalis.ai, and amadalis.ai shows a short holding page that sets no cookie and runs no analytics. The holding page loads its fonts from Google Fonts, so your browser asks Google for them.

amadalis.ai sells and shares no visitor data. Its analytics are first-party only.

Consent by where you are

  • You meet the consent rules of where you are. The server applies them before a page is sent.
  • In 32 countries, opt-in applies: the 27 countries of the European Union, with the United Kingdom, Switzerland, Iceland, Liechtenstein and Norway. No identifying cookie is written before you say yes.
  • In the United States, opt-out applies. You see a short notice at the moment of collection, and you can say no.
  • Everywhere else, and whenever your location is unknown, opt-in applies.
  • "Accept all" turns on analytics and personalization. Marketing stays off until you choose it.
  • "Privacy choices" reopens "Choose what you allow on this site." at any time. A new choice replaces the old one.

Global Privacy Control and Do Not Track

  • If your browser sends Global Privacy Control, the server refuses all three purposes: analytics, personalization and marketing. The signal outranks any click.
  • If your browser sends Do Not Track, the page's analytics script stays off until you make an analytics choice.

What we record, within your choice

  • Analytics: the pages you visit, and how you found the site: the page you land on, the site that referred you, and any campaign tag or ad-click ID (such as gclid or fbclid) in the link you arrived on. With each of these we also record your country, your kind of device, your browser and operating system with their main version, and your preferred language. We never store your browser's full identification string.
  • Personalization and A/B tests: the pages you read, used to tailor and test what the site shows you, and a record of which version you were shown and why.
  • These records are first-party. They live in our site's own database, with no third-party tag.

What you send us

  • The contact form: your name, your email, your company, the topic, your website and your message. We use it only to reply to you.
  • The Lighthouse application: your name, your work email, your company or agency, your website, which describes you best, what you would like to run on Praxis, what your current site is built with, roughly how many visitors it has a month, and anything else you tell us. We use it only to review your application and to reply to you.
  • Email you send to support@amadalis.ai.
  • A person on our team reads every message and every application.
  • We keep these messages until we delete them. Messages our spam protection marks as spam are deleted automatically after 30 days.

Fonts

Our website serves its fonts from its own address. Your browser makes no request to a third party for fonts on it.

4. Account holders and their teams

What we hold

  • Sign-up: your organization, your site's name, your name, your email address and your password. You can name an existing WordPress site for us to look at. Nothing imports until you authorize it.
  • Your team: each invitation names an email address and a role. We record each member's role on each site.
  • Billing: Stripe takes payment. We never see or hold your card. We hold your plan and the state of your subscription.
  • The Security log: every governed action on your account: when, what, who, from which network, and the browser it came from. By default the log keeps only the network part of an address (such as 203.0.113.x). Your account can choose to keep the full address.
  • Sign-in security: your two-factor settings, your sessions, and your SCIM settings if your identity provider manages your team. SCIM tokens are kept only as a hash.
  • AI use: copilot calls are written to a cost ledger and checked against your account's monthly allowance. At Cloudflare AI Gateway, payload logging is switched off, so only each call's metadata is logged.
  • Copilot conversations: your conversations with the copilot are kept so you can return to them.
  • Support: the messages you send us, and the record of every time our support reaches your site.

Why we use it

  • To create and run your account and your sites.
  • To bill you, through Stripe.
  • To send the emails the service needs, such as your invitation, the link that verifies your email, and the email that says your plan is active.
  • To keep Praxis and your account secure, and to keep the audit record.
  • To answer you when you ask for help.

Where EU or UK law applies, we rely on our contract with you, on our legitimate interest in running and securing Praxis, on legal obligations, and, for analytics and personalization on amadalis.ai, on your consent.

5. Who receives personal data

  • Our subprocessors. They are named on our public register at https://account.amadalis.ai/subprocessors: Cloudflare, GitHub, Neon, Resend and Stripe. The register says what each one does and where it runs.
  • Our AI providers, for copilot requests. The copilot uses two: Anthropic, for the copilot model itself, and OpenAI, to give each conversation its title. Every call goes through Cloudflare AI Gateway, with payload logging switched off on every request, so the gateway keeps only metadata. We treat what you send the copilot as your data. On request, you may add your own key for Anthropic or OpenAI. That provider is your choice, and the relationship with it is yours. With your keys on, the copilot's calls go to that provider on your key, or are refused.
  • Training. Praxis opts into no model training with its AI providers. Whether a provider trains on data sent through its API is that provider's own commitment, in its own words:
    • Anthropic's Commercial Terms of Service, effective 17 June 2025 (https://www.anthropic.com/legal/commercial-terms, read 3 November 2026): "Anthropic may not train models on Customer Content from Services."
    • OpenAI's page "Data controls in the OpenAI platform" (https://developers.openai.com/api/docs/guides/your-data, read 3 November 2026): "As of March 1, 2023, data sent to the OpenAI API is not used to train or improve OpenAI models (unless you explicitly opt in to share data with us)."
  • An agency, if an agency manages your account. Its owners and admins reach your sites and account through access that is recorded and can be withdrawn.
  • Authorities, when the law requires it.
  • A successor, if our business is sold or merged. This policy keeps applying to your data.

6. Where data is processed

  • Every request arrives on Cloudflare's network. The network that serves pages, its caches and AI features run worldwide.
  • Each site's content and events live in a database of its own, with Neon. Our register lists Neon's region as the United States. Your account's Overview names the region your site's database runs in, recorded when the site was created.
  • Uploaded files are kept in Cloudflare's object storage, R2.
  • Transfers of personal data from the EU, the UK and Switzerland use the EU Standard Contractual Clauses, the UK Addendum and the Swiss amendments.

7. Visitors to our customers' sites

The site you visited decides what it collects. Its own privacy notice tells you. Ask the site's owner first. If you write to us, we pass your request to the site's owner.

On every Praxis site:

  • Consent by jurisdiction. The rules of where you are apply on the server, before the page is built. Each site sets its own map of rules.
  • Global Privacy Control is honoured on the server. A visitor who sends it is never placed in an experiment, never shown targeted content, and never scored for interests. A shopper who sends it keeps everything they paid for.
  • First-party analytics. Events, visitor facts and traits live in that site's own database. A site can add its own tags, and Praxis can hold each one until the visitor allows its purpose.
  • Only the site's Admins can open visitor data.
  • Erasure. A site's Admins can find a visitor by email, user id or visitor id, export that visitor's record, and erase it permanently. Erasure works on one browser's record at a time, so a person who used several browsers is erased browser by browser. Erasure deletes identity links, profile, traits, audience memberships, consent records, interest scores, raw events, experiment assignments and conversions. What remains in the event history is anonymised. The site's export archive marks the visitor as erased and is rewritten within seven days. Export files already downloaded cannot be recalled.
  • What erasure keeps. Orders and shopper accounts are kept, without the link to the visitor. Orders keep the name and email given at checkout. Form submissions are deleted on their own, from the form's inbox. An evidence record of the erasure is kept, and it never names the visitor.
  • Retention. Each site sets how many days each kind of captured event is kept, from 1 to 3,650. Unless the site sets a period, everything is kept. A day's raw events are deleted only after a completed archive export covers that day.

8. How long we keep data

  • Account data and the Security log are kept while your account is open. When the account is terminated, account data is deleted, and each Security log entry is kept without its details. A deletion certificate lists what was destroyed, when and by whom. We keep a record that the account existed and what happened to it, and the records the law requires us to keep. A final backup is kept for a limited period, then deleted.
  • Backups. Every site's database is backed up twice a day. Backups are kept for a limited period, then deleted.
  • Messages sent through our forms are kept until we delete them. Messages marked as spam are deleted automatically after 30 days.

9. Your rights

  • Depending on where you live, you can ask to see, correct, export or delete your personal data, to object to or limit its use, and to withdraw your consent.
  • On amadalis.ai, "Privacy choices" changes your consent at any time.
  • In the United States, a Praxis site that sells or shares data shows a "Do Not Sell or Share My Personal Information" link.
  • To use a right, write to support@amadalis.ai. We answer within the time the law sets.
  • You can complain to your data protection authority.

10. Cookies and browser storage

This section lists the cookies and browser storage of amadalis.ai and account.amadalis.ai.

What a site needs to work, such as a shopper's cart, sign-in and paid access, is essential and never gated.

On amadalis.ai, cookies are set only as the table below describes. account.amadalis.ai sets cookies only when you sign in, runs no analytics and shows no consent notice.

Until our website moves to amadalis.ai, the rows marked amadalis.ai apply to amadalis-hq.sites.amadalis.ai.

NameWhereKindWhat it doesHow long
__em_vidamadalis.aiCookieRecognizes a returning browser for analytics and personalization. It is Secure and HttpOnly, so the page's own scripts cannot read it. Under opt-in, it is created only after you allow analytics or personalization. Under opt-out, it can be created when a page is served, when you make a choice or on the first recorded page view, unless your browser sends Global Privacy Control or you have refused both analytics and personalization.One year
__em_consentamadalis.aiCookieHolds your consent choice, so a refusal is remembered even without a visitor id.One year
praxis_consent_noticeamadalis.aiLocal storageRemembers that you chose "OK" on the notice, so it is not shown again.Until you clear it
praxis_pending_arrivalamadalis.aiSession storageUnder opt-in, holds your landing page in your own browser until you decide. It is sent only if you accept.Until the tab closes
praxis_pending_consentamadalis.aiSession storageKeeps a choice you just made until the server has recorded it.Until the tab closes
praxis_order_attributionamadalis.aiSession storageOn every page load, campaign source, landing page, referrer and device type are kept in your browser session to attribute an order, on sites that run a shop. It also holds your browser's identification string, the current page address, when the session started and how many pages you have opened in this tab. Our website runs no shop, so nothing reads it here, and it never leaves your browser.Until the tab closes
Sign-in cookiesaccount.amadalis.aiCookieKeep you signed in. They are essential, and set only when you sign in.Until you sign out or your session ends
Scroll positionaccount.amadalis.aiSession storageInside the signed-in account, keeps your place on a page as you move between pages.Until the tab closes

When your browser has a visitor id, each new or changed consent choice is also kept on the server, with the regime, the version of the policy in force, and where the choice came from. A refusal from a browser with no visitor id is kept only in its __em_consent cookie.

11. Security

  • Each site has its own database.
  • Stripe keys and identity provider secrets are stored encrypted. SCIM tokens are kept only as a hash. No copilot tool takes a secret.
  • Every operator signs in with two-factor authentication, and each operator holds a scope: read, support or admin.
  • Each new entry in our operators' audit log is linked by a SHA-256 checksum to the entry before it.
  • Our support reaches a customer's site only in four ways, and each one is recorded.
  • No system is perfectly secure. If a breach affects your data, we tell you as the law requires.

12. Children

Praxis and amadalis.ai are for businesses. Account holders must be 18 or older.

13. Changes to this policy

We post changes here and update the date at the top. We tell account holders by email 30 days before a material change applies.

14. Contact

Your data, and help with Praxis: support@amadalis.ai.