Security

You own the stack

MaShop runs the builder, the workspace where you describe your business and the AI writes your code. The output leaves our platform and lands in accounts that belong to you.

• The code we generate is committed to your own GitHub repository. You can read it, change it, or take it somewhere else at any time.
• Your site deploys to your own Netlify account. We trigger builds on your behalf; the live site runs on infrastructure you own.
• Your storefront data, such as products, orders, and customers, lives primarily in your own Supabase project. Some order and payment records pass through our platform when webhooks are processed, so your workspace can show them.

Your prompts and data

We use your prompts to build and edit your project. Prompts are sent to the inference providers that run our models. They are not sent to OpenAI or Anthropic.

• Connections to MaShop run over HTTPS, and in production we enforce it with HSTS. The providers that host our infrastructure encrypt stored data at rest.
• We are direct about one point: to build and deploy on your behalf, we store the service key of your Supabase project. We encrypt it with AES-256-GCM before it is written to our database, and we use it only to build, provision, and deploy your project.

How we secure the builder

The builder holds your project files, chat history, and settings. We protect it in layers.

• Row-level security in Postgres scopes workspace records to your account and the collaborators you invite, with read or write rights matching their role.
• Privileged keys stay on the server. Your browser never receives them, and sensitive writes check your role server-side first.
• Hardened HTTP headers ship on every page and API response: a Content Security Policy, HSTS, and anti-clickjacking protection.
• Sensitive flows such as sign-in, password reset, and two-factor checks only accept requests from a trusted MaShop origin, and post-login redirects only go to allowlisted MaShop hosts.
• OAuth tokens and connected-service credentials are encrypted at rest with AES-256-GCM.
• Billing webhooks are verified with HMAC signatures where the provider supports it, and events older than five minutes are rejected when the provider includes a timestamp.
• Two-factor authentication is available on every account, backed by single-use backup codes stored as hashes. It can be enforced for admin access.
• Sensitive endpoints are rate limited to slow down brute-force attempts.
• Collaboration invites and project transfers use signed, expiring tokens.

Compliance and honesty

• We operate under the GDPR. You exercise your data rights by writing to contact@edeverse.com, and you can complain to a supervisory authority. In France that is the CNIL.
• We hold no security certifications today. We will not show a badge we have not earned.
• Card data stays outside MaShop. Payments on your site run through the payment providers you connect, so card details go to those providers, never to us.