Skip to the page content

Marktmorgen is still being built. You can open a store and set it up today; its paid plans are not on sale yet. See what is built

Marktmorgen

Security

How your store and your buyers are protected

What we do, written so you can check it: payments on your own Stripe account, sign-in without passwords, strict rules on what your pages may run, a refund that closes what it paid for, your data yours to take or delete, and how the code is checked. And, at the end, what none of it does.

Working todayAll plans; limits apply

Passkeys and two-step login in the studio's account card. The device, the dates and the recovery address are made up as an example.

Your money and your account

  • Sales on your own StripeThe buyer pays on Stripe's own checkout, on your account. We never see a card number and never hold a balance of yours.
  • Prices worked out on our sideWhat a buyer is charged is read on our server from what you saved, never from anything the page sends.
  • No password to stealYou sign in with a link sent to your email. It works once and stops working after 15 minutes. We keep only a hash of the link, not the link itself, and there is a limit on how often a link can be requested.
  • Passkeys, if you want themOptional: sign in with the face, fingerprint or PIN that unlocks your phone or laptop. We keep only the public half of the key, and the emailed link keeps working.
  • Two-step loginTurn it on and the emailed link also asks for the six-digit code in your authenticator app, so somebody who gets into your email still cannot open your studio. Ten recovery codes for when your phone is not at hand, each good once; a passkey needs no code. A code is never taken twice, five wrong ones end the login, and turning it on or off emails you. Turning it on asks for a recovery address, a second inbox: lose your phone and your codes, and a link sent there lets you straight back in.
  • Lost your email? Still yoursAdd a recovery address, a second inbox you confirm with a code, and a passkey. If you can no longer open the inbox you log in with, a passkey logs you in with everything open, and a link to your recovery address lets you in at once, with payments, exports, settings, sending and your sign-in address opening a week later, unless your old inbox answers first. Then move your sign-in address to one you have. Nobody here has to open anything for you.
  • Team roles checked on our serverWhat an Admin, an Editor or Support may do is checked on the server for every request, not only hidden on the screen.
  • A fresh session every timeEach sign-in starts a new session, and a session the browser held before is closed.
  • A session cookie scripts cannot readAfter you sign in, your browser keeps a cookie that says it is you. Scripts on a page cannot read it, because it is HttpOnly, and on the live site it is sent only over an encrypted connection. We keep only a hash of it. It ends after 30 days, or when you log out.
  • Log out of all devicesOne button at the bottom of your studio closes every session you have open, everywhere.
  • An email when something important changesWhenever your Stripe account, your domain or your webhooks change, we write to your sign-in address saying what changed and when.

Your pages

  • A strict policy on what runsStore pages, on marktmorgen.com and on your own domain, the studio and signing in carry a Content-Security-Policy with a new nonce on every response, so text somebody typed cannot run as a script.
  • Pixels only where allowedYour Meta, Google, TikTok and Pinterest pixels load only after the visitor agrees, where the law says they must be asked.
  • Forged requests refusedEvery request that changes something must come from this site, and our cookies are HttpOnly and SameSite.
  • The usual browser protectionsHSTS, nosniff, a referrer policy, Cross-Origin-Opener-Policy, a Permissions-Policy that switches off camera, microphone and location, and no framing by other sites.
  • Emailed links go to us or to youEvery link we email points at marktmorgen.com or at your store's own domain, never at an address a request made up.

Files, refunds and bots

  • Downloads that expireThe download on the thank-you page works for 3 days; after that the buyer gets it again by email. Where a file is stored is never shown, and large files go through signed links that expire in minutes.
  • Files that cannot runEvery file is handed over as a download, with headers that stop a browser running anything inside it.
  • Pictures checked, files size-limitedA product or page picture you upload is checked by its first bytes, not by its name. It must really be a JPEG or a WebP, at most 1 MB, or it is refused. A file you sell can be at most 5 GB.
  • A full refund closes the doorRefund a payment in full on your Stripe account and its download stops at once, its course closes within 10 minutes, the community within 5 minutes, and its license key is revoked within about 5 minutes. A partial refund keeps access.
  • Limits that stop botsCheckouts are limited to 20 per 10 minutes per connection per store, and bookings and every form that sends an email have limits of their own, so a script cannot sit on your limited stock or your call times.
  • Hidden traps for botsThe sign-in form and your store's contact and free-product forms have a hidden box that people never see. A request that fills it in is dropped. Sign-in also asks our hosting provider whether the request came from a program.
  • Signed webhooks, guarded addressesWebhooks are signed with HMAC-SHA256. When our server fetches an address someone typed, such as a webhook or a calendar feed, it first looks up where the address leads and refuses one inside a private network.
  • Ceilings on paid workWork that costs us money, such as AI writing and uploads, is counted against a monthly ceiling for your store, and one for the whole site, before it starts. If a ceiling is reached, or cannot be checked, the work is refused instead of run.
  • Email platform keys kept encryptedThe API key of your Mailchimp, Kit, beehiiv or MailerLite is encrypted before it is stored, and never shown again.
  • Reviews only from paying buyersA review can be written only for an order your own Stripe account says was paid and not refunded in full.

Your data, yours to take or delete

  • A copy of your store's main dataYou, or a teammate allowed to export, can download a copy of your store's address, name, bio, links, currency and the date it was created, your products and their pages, thank-you notes, courses with every lesson's text, blog posts, forms and their answers, contacts and a summary of your orders as one file, from your studio. Nothing else is in it. For example, files, videos, community posts, email sequences and broadcasts, reviews, coupons, affiliates, the times of booked calls (their payments are in your orders), funnels and CRM deals and tasks stay in your studio.
  • Buyers can delete their own dataA buyer can delete what a store keeps about them through a link emailed to them. No account is needed, and nobody has to approve it.
  • Delete a person when they askYou, or a teammate allowed to, can delete one person from your store. Before you confirm, the studio says what is deleted, what is kept and why.

How the code is checked

None of these checks proves that there are no faults. Each one finds some kinds of faults early.

  • Tests on every changeEvery proposed change to the code, and the main code once a day, runs our automated tests.
  • Code scanningCodeQL, GitHub's code scanner, looks for known kinds of security faults in the code on every proposed change to the code and once a day.
  • Packages checked for known flawsnpm audit compares the packages the site is built from with public lists of known security flaws, on every proposed change to the code and once a day.
  • A written reviewOn October 18, 2026, the code was reviewed for security faults. Each fault found was tried out on test data, written down with how serious it was, and then fixed or listed as not fixed yet.

What this does not do

Said here so nobody relies on it for more than it does.

  • No system is free of faults, and this one is not either. The checks above find some kinds of faults, not every one. If you find one, please tell us: the question “How do I report a security problem?” below says how.
  • Two-step login is off until you turn it on. Without it, your account is as safe as your email inbox: protect that one.
  • Lose your phone, your recovery codes and every passkey, and a link to your recovery address gets you straight back in. Lose that inbox too, and you still get in at once, with the emailed link alone: you can sell, edit your products and pages and answer buyers, while payments, your plan, your team, exports, imports, settings, sending email to your list or your members, canceling or moving events, sending a purchase email again, deleting anything for good (people, products, lessons, files, forms, posts), putting a new file or picture over an old one, your sign-in address, passkeys and two-step login stay locked for 7 days, until two-step login turns off. That lock is what stops somebody who only has your sign-in inbox, and a login with a code or a passkey, or Cancel in your studio, logs them out.
  • On a payment plan, a refund in full of the first payment closes access like any refund in full; a refund of a later payment is not detected, so take the buyer off the course, or remove their access, yourself. A refunded membership closes when its subscription is canceled in Stripe.
  • A refund cannot take back a file already saved, or a product delivered as a link to somewhere else.
  • The limits on checkouts, bookings and forms are counted in our database. If it cannot be reached, they let requests through rather than stop a buyer from paying.
  • Pages built ahead of time, such as the home page, the help center and the blog, carry a policy without a nonce. Nothing on them comes from a creator or a visitor.

Questions about security

What do I need to do to keep my account safe?

Protect your email inbox first: the link we send there is how you log in. Then, in your studio under “Account”, you can turn on two-step login, which asks for a code from your phone after that link, and add a passkey or a recovery address, which are ways back in if you ever lose that inbox. Each is optional. Pick a recovery address only you can open: a link sent there lets you in too.

How do I turn on two-step login?

In your studio, open “Account” and find “Two-step login”. If it first asks you to log in again, do that and come back. Type a recovery address if you have none yet, and press “Turn on two-step login”. Scan the square code, or type the key shown beside it, into your authenticator app. Type the six digits it shows and, if you typed the recovery address here, the code we email to it, then press “Turn it on”. Save the recovery codes it shows you: they are shown only once. If it says the code could not be emailed, check the address and try again. If it says two-step login is not available yet, it cannot be turned on for now.

Do these need a plan or a payment?

No. Adding a passkey, a recovery address or two-step login asks for no plan and no payment, and none of them is charged. They are under “Account” in your studio once you have taken your store's address.

What if I lose my phone?

With two-step login off, nothing changes: the emailed link logs you in. With it on, type one of your saved recovery codes at the code step, or log in with a passkey kept on another device. If you kept a recovery address, the code page offers “Email my recovery address”. If none of these works, the same page says what opens at once and what waits. Then, under “Account”, remove the lost phone's passkey with “Remove”.

What if I get an email about a change I did not make?

Log in, choose “Log out of all devices” at the bottom of your studio, put the setting back, and reply to that email so we can help.

Who handles a refund?

You do, in your own Stripe dashboard. What a full refund closes here happens by itself, read from Stripe.

Can I sign in with a password?

No. There is no password to set, and none kept here to be stolen. Each link we email works once, for 15 minutes.

How do I report a security problem?

Email support@marktmorgen.com with what you found and how to see it, and a person answers by email. Please test only your own store and your own data. The same address is in our security.txt file, at marktmorgen.com/.well-known/security.txt, the standard place security researchers look.

Words on this page

Passkey
A way to sign in with the face, fingerprint or PIN that unlocks your phone or computer. Your device keeps the private part of the key; we keep only the public part.
Two-step login
Signing in with two things instead of one: the link sent to your email, and a six-digit code from an authenticator app on your phone.
Recovery code
A code you save when you turn on two-step login. Each one works once, for when your phone is not at hand.
Hash
A scrambled stand-in for a piece of text. The same text always gives the same hash, but there is no practical way to turn the hash back into the text. So a stolen hash does not give anyone the link or the session it came from.
Cookie, HttpOnly
A cookie is a small note a website asks your browser to keep. HttpOnly means scripts on the page cannot read it; only the browser sends it back to us.
Content-Security-Policy
A rule a page sends to the browser saying which scripts may run on it. Anything else is blocked.
HSTS
HTTP Strict Transport Security: a rule that tells the browser to use only the encrypted connection to this site.
Webhook
A message our server sends to an address you choose when something happens in your store.
HMAC-SHA256
A way to sign a message with a secret key, so the receiver can check that it came from us and was not changed on the way.
Private network
Addresses inside a company's or a cloud's own network, which the open internet cannot reach.
Code scanning
A program that reads the code and points out patterns that often lead to security faults.

A practical way to use it

  1. 1

    Check the record before opening access

    Use the store's existing payment and permission checks to decide what a visitor can open. A guessed link is not a purchase record; these checks are not a claim that every possible attack is prevented.

Check the terms before you commit

Your work stays yours. Read how payments, data and leaving the platform work, then decide whether the fit is right.

  • Your own Stripe account

    Direct charges use the creator’s Stripe account. Stripe processing, payout timing, refunds and disputes still apply.

    Follow the payment path
  • Your records can leave with you

    Export the contact and order records your role can access. Keep a copy before closing a store; export does not move subscriptions to another provider.

    Read the data policy
  • Cancellation from your studio

    Manage an existing platform subscription through Account. Review its end date and what closing a store changes for buyers.

    Review cancellation terms
  • A clear platform refund policy

    The first platform payment can be requested back in full within 30 days, under the Terms. A buyer’s refund for a creator’s product follows that offer and applicable rights.

    Read the refund terms

Paid plans and paid selling remain subject to all opening gates. These terms do not mean sales are open or that earnings are guaranteed.

Prepare your own store

Take your address and put your first product up today. The plan is $69 a month and 0% of your sales, and it is not on sale yet.