The small print, in plain words
Privacy Policy
On this page
Marktmorgen (“Marktmorgen,” “we,” “us,” or “our”) is operated by Solrenning, an independent software studio. This Privacy Policy explains how we collect, use, share, and protect personal information when you use our websites and products — the Marktmorgen creator store at marktmorgen.com (the “Services”).
If you have questions about this policy or about your personal data, contact us at support@marktmorgen.com.
1. Information we collect
We collect the following categories of information:
Account information. When you create an account or subscribe, we collect your email address and any other information you choose to provide (such as your name, if requested at checkout).
Payment information. Payments are processed by Stripe, our payment processor. We do not store your full credit or debit card number, CVC, or equivalent payment credentials. Stripe may collect billing name, address, and payment method details as needed to complete the transaction. We may receive limited payment metadata, such as the last four digits of a card, payment status, and subscription period.
What a creator puts in a store. If you run a Marktmorgen store, we host what you put in it: your store name and description, your photo if you add one, the theme and color you choose, your product titles, prices and descriptions, the links you put on the page, and the files you upload for delivery to your buyers. Your photo is shrunk on your own device before it is sent, is shown publicly on your store page and in previews of links to it, and is deleted from our storage when you remove or replace it. The postal address you type for the bottom of your emails goes in those emails only; it is shown on your store's public policies page too only if you check the box for that where you type it, and comes off the page as soon as you uncheck it and save.
Buyer information. When someone buys from a creator's store, we handle the buyer's email address and the details of that order — what was bought, when, for how much, and whether the file was delivered — so the sale can be completed and the creator can see it. The card details are handled by Stripe and never reach us. That buyer information belongs to the creator, not to us, and section 4 explains what that means.
A confirmation of each purchase. After a buyer pays, we email them one confirmation on the creator's behalf, under the store's name, with what they bought and how to get back to it; replies go to the creator. What it says is read from the payment on the creator's Stripe account. We keep only a mark that it was sent, tied to that checkout, for 40 days, so it is never sent twice. If a creator asks buyers questions at checkout, or asks for a phone number in Stripe's own phone box, the answers are kept with the payment on the creator's own Stripe account, shown to the creator, and for a booked call included in the creator's booking email. For a physical product the creator ships, the address you type on Stripe's page is kept the same way and shown to the creator so they can send it; we keep only when they marked it as shipped and the tracking link they gave, for 400 days, to email you once that it is on its way.
An update to something you bought. A creator on Pro can tell the buyers of one of their products, at most once a week, that it was updated and where to get the new version. The addresses are read from the creator's own Stripe account when they press send, kept with us only until the email has gone out, and not shown to the creator or added to any list. Nobody who left that creator's list is written to. Each email has a link that stops these emails from that store; it is kept, tied to the address and the store, for 400 days, and pressing it keeps a one-way hash of the address for that store for good.
A reminder after an unpaid checkout. Only on stores whose creator switched it on, and only for a buyer who agreed on Stripe's own checkout page to hear from that creator, or who, on the page the way back from that checkout leads to, typed their address and asked for the reminder themselves: if they leave without paying, we email them once, on the creator's behalf, with a link back to the product. For the first, Stripe keeps the address and the answer on the creator's account. For the second, the address waits with us for about an hour, until the reminder is sent or dropped; it is not shown to the creator and is not added to any list. We keep a mark that the reminder for that checkout was handled, for two weeks; a one-way hash of the address and the product for a week, so nobody gets two reminders about the same thing; and the link in the reminder that stops them, tied to the address and the store, for 400 days. Pressing it keeps a one-way hash of the address for that store for good, so that store never sends them a reminder again.
A come-back offer. Only on stores whose creator switched it on, and only to somebody who agreed to hear from that creator and has not left their list: some days after a membership ends, we read from the creator's Stripe account when it ended, which product it was and the address it was paid from, and email that address once, on the creator's behalf, with a discount to come back. We keep a mark that the email for that membership was handled, for 90 days; a one-way hash of the address and the product for 180 days, so nobody gets two such emails about the same thing; and the link in the email, tied to the address, the product and the offer, for 14 days. It carries the creator's list's own one-click unsubscribe.
Managing a membership. When a member asks for a link to manage or cancel their membership, we use the email address they type to look for their membership on the creator's own Stripe account and, if there is one, to email them the link. We keep a record that ties that link to their Stripe customer for one hour and, to limit abuse, one-way hashes of the address and of the network address that asked, also for one hour, and nothing else; the page says the same thing whether or not a membership was found. When a member switches their membership to another of the store's plans, the change is made on the creator's Stripe account, which keeps the record of it, and we email the member a receipt and the creator a note with the member's email address and the two plans. The same goes for a switch to yearly payments. Each asks the box about starting before the 14 days end again, and keeps its answer on the membership (see Starting before the 14 days end). We keep nothing more about it.
Getting a purchase again. When a buyer asks a store for what they bought, we use the email address they type to look for their paid purchases on the creator's own Stripe account and, if there are any, to email them a link to a page that lists them. We keep a record that ties that link to the address for 24 hours and, to limit abuse, one-way hashes of the address and of the network address that asked, for one hour, and nothing else; the list itself is read from Stripe each time the page opens, and the page says the same thing whether or not a purchase was found.
Counting visits to a store. When a creator's store page is opened, the page tells us so, with the site that sent the visitor or the campaign word in the link. To count people rather than page loads we make a one-way fingerprint of the day, the store, the visitor's network address and browser, and add it to a counter that keeps only an estimate of how many different fingerprints it has seen. The fingerprint and the address are not stored, no cookie is set, and the daily counts are kept for about thirteen months, with a running all-time total of the same counts for as long as the store exists. The creator sees totals, never a person.
So a creator can see how many people are on their store page right now, the first ten characters of that day's fingerprint are kept for up to half an hour, beside the site the visitor came from, and then deleted; they cannot be turned back into an address, and the creator sees only a count.
A creator's plan covers a number of visits a month, so visits are also counted for that, on any page of a store that is opened: one for each visitor each day. For this we make a second one-way fingerprint, of the day, the store and the visitor's network address (for the newer kind of address, the network it belongs to), made with a secret key of our own, and keep its first sixteen characters in a list for that store and that day, so that the same visitor is not counted twice. The list cannot be turned back into addresses, holds nothing else, and is deleted two days later; what remains is the store's count for the month. The address itself is not stored, and no cookie is set.
Funnels of pages. When a creator puts pages in order as a funnel, each step that is opened tells us so, and so does a sign-up or a payment made on a step. To count each person once a step we make a one-way fingerprint of the funnel, the store, the visitor's network address and browser, and add it to a counter that keeps only an estimate of how many different fingerprints it has seen. The fingerprint and the address are not stored, and no cookie is set. The counts begin again whenever the funnel's steps change, and each is deleted 400 days after the last person counted in it. The creator sees totals, never a person.
Copying a store into another of your stores. When a creator copies one of their stores into another store they own, only what they made comes across: products, pages, forms with their questions, funnels and, if they ask, the store page's setup. No personal data of anyone comes across: no customer, order, contact, email address on a list, answer to a form, review, payment, payout detail or file. Social profiles that reach the creator in person (an email address, WhatsApp or Telegram) stay on the store they were set on. To let a copy go on after an interruption without making anything twice, we keep a record of its progress for seven days, holding the two stores, the products' ids and what is done, and nothing about a person.
A store's own people are not counted. Visits by the store's owner or a member of its team while signed in are left out of its counts. A creator can also mark a browser they use, signed in or not, so its visits are left out: that browser keeps a cookie named nl_nc for 400 days, holding for each store marked only twelve characters of a one-way hash of the store, and nothing about the person.
Google searches that found a store. For stores at marktmorgen.com, we read from Google Search Console, for our own site, which searches showed each store's pages, how many times, how often they were clicked and where the store stood, and show these totals to that store's creator. They are Google's figures about searches, added up by Google and with rare searches left out by it; they say nothing about who searched, and nothing about a store's visitors is sent to Google for them. We keep each store's latest reading for a day, and the access to our Search Console sealed.
Ad measurement a creator switches on. A creator can add their own Meta, Google, TikTok, Pinterest, X or Reddit pixel to their store. When they do, and only once it is allowed, that store's pages load that platform's script, which sets its own cookies and tells the platform about page views, checkouts started, requests for free products and purchases with their amount, on the creator's behalf and under that platform's own privacy policy. Visitors in the European Economic Area, the United Kingdom, Switzerland or Brazil, or whose country we cannot tell, are asked first and nothing loads unless they agree; everywhere else the pixels load unless the browser sends Global Privacy Control. The choice is kept on the visitor's device for that store, and a link at the bottom of its pages changes it. While ad measurement is allowed, that store also keeps a cookie of its own saying so, with the ad click id the visitor last arrived with (Meta's fbclid, TikTok's ttclid or Pinterest's epik), for 30 days; it is deleted the moment the choice is no. X is told about purchases and requests for free products only when the creator set up those events with X, and never about checkouts started; where a visitor has not said yes (because their country does not ask first), X is told to limit how it uses the data, with X's own setting for that. Reddit is told about page visits, purchases and requests for free products, never about checkouts started and never an email address; where a visitor has not said yes, it is marked Limited Data Use with the visitor's country and, when known, region, and the creator has to switch off Reddit's automatic matching of email addresses before the pixel can be added.
Conversions sent from our server, when a creator sets it up. A creator who has a Meta, TikTok, Google Analytics or Pinterest pixel can also give us an access token from their own account with that platform. Then, for a visitor who allowed ad measurement on that store, as above, we send the platform from our server: each purchase once Stripe confirms the payment, each later payment of a membership bought that way, and each sign-up for something free, a waitlist or the creator's list (sign-ups are not sent to Google). With each we send its id, time, amount, currency and products, whether the buyer had paid that creator before, the page, the email address hashed with SHA-256 (a sign-up for something free or a waitlist is sent without it, because the address is not confirmed yet), the network address and browser of the request that opened the checkout or sent the sign-up (not with a later membership payment), and the platform's own cookies and ad click id from that browser. It goes to that platform on the creator's behalf and under its own privacy policy. A visitor who did not allow ad measurement is never sent. We keep the token sealed; for four days, the request that opened a checkout; for 400 days, the cookies and ad click id a membership's later payments are sent with, never an address or browser; for three days (40 for a membership payment) that each was sent; and the platform's last answer for the creator to see.
Buyers' addresses for an ad audience, when a creator downloads them. A creator can download a file of the email addresses of their buyers who agreed to hear from them and have not left their list, to upload to Meta or TikTok themselves: to stop showing ads to people who already bought, or to find people like them. It holds the address and nothing else. We make the file when it is asked for and send it nowhere; the creator decides whether to upload it, and the platform then handles it under its own terms.
A checkout that did not open. When Stripe refuses to open a store's payment page, we count it by the day and keep Stripe's reason, for 35 days, so the creator can see it and is emailed once that day. Nothing about the buyer who pressed buy is kept.
Why a member cancels. When a member cancels on the page a store's emails link to, Stripe asks why, and keeps their answer and any words they add on the creator's own Stripe account. We read them from there to show the creator the reasons added up and the latest words, without the member's name or address beside them, and keep that reading for ten minutes. When the creator asks for the month's summary of what customers say, those words, with any email address, phone number or web address in them taken out, go to Anthropic's model to be sorted into themes, and the summary is kept for about two months.
Paying with PayPal. Where a store takes PayPal, the buyer pays the creator's own PayPal account, under PayPal's privacy policy. We keep, for up to about 400 days, the order and payment numbers, the email address of the buyer's PayPal account (to hand over what they bought and send it again on request), what was bought, the amount, and the same notes a card checkout carries: the channel the visit came from and, where an affiliate sent the buyer, that affiliate and their share. The creator sees the sale in their numbers and orders like a card sale, and their affiliates and webhooks are told of it.
Numbers a creator shares. A creator can show, on their media kit, the visitors and sales of the last 30 days and the countries their buyers are in, as shares; and can give somebody a read-only link, with a password and an end date, to their store's visits, sales, channels, products sold and buyers' countries. Both are read once a day and kept for three days. Neither ever holds a buyer's name or address. The password is kept only as a salted hash; whoever opens the link with it is remembered in that browser for at most twelve hours by a cookie that opens only that link, and the network address it is opened from is used, for ten minutes, only to limit wrong passwords.
Numbers to Slack or Discord, a goal, and the month's email. A creator can give us a Slack or Discord webhook address; we keep it sealed and post there the week's and the month's totals, channels and notes — counts and amounts, never a buyer's name or address. If the creator asks, each sale is posted there too, as its amount, what was bought and the channel it came from, and so is each alert on the store's numbers; never who bought it. A goal the creator sets for the month is kept as one figure. On the 1st of each month the store's creator is emailed the month's numbers, with the same link to stop it as the weekly email.
Booking a call. When someone books a paid call, we use the time they picked, their time zone and the email address on their Stripe receipt to hold that time while they pay, to write the booking down, and to send one confirmation to them and one to the creator. So that each can answer the other, the buyer's confirmation has the creator's email address as the address replies go to, and the creator's has the buyer's. While they pay, a cookie in the buyer's browser names the checkout they opened, for 32 minutes, so that going back to pick another time releases the first one. The buyer and the creator are each reminded of the booking a day and an hour before, from a queue that names the booking and its time, and we keep a mark that each reminder was sent for 14 days. If the buyer moves the booking to another time from the link in their email, we keep the new time and how many times it was moved, tied to that checkout, until 200 days after the call it was moved to, and never longer than two years. The line in the creator's diary that keeps the time taken is let go 90 days after the call ends; the booking itself stays on the creator's Stripe account. The same kind of cookie, for the same 32 minutes, is set when someone starts to buy a product sold in a limited number, so that pressing buy again hands back the one they were holding.
Payment plans and sales tax. When a buyer chooses a payment plan, Stripe keeps their card on the creator's account for the remaining payments, and we keep the checkout on a list until the plan has been given its end date, so it stops after the last payment. When a creator switches on sales tax, Stripe asks the buyer for the address it needs to work the tax out, under Stripe's own privacy policy; we do not keep it.
Private podcasts. When you get the feed of a private podcast you bought, we keep your email address with a private feed address made for you, so your podcast app can read it. Each time the app reads the feed or fetches an episode, we check that your address still holds the podcast, and we count those reads to stop a feed from being shared; we do not keep which episodes you play. The creator sees neither your feed nor what you listen to.
Packages of sessions. When you buy a package of calls, we keep your email address, which payment it was, how many sessions it holds, its last day to book, and which bookings were made from it, so you can book the rest from the link we email you and see how many are left. A package with a last day to book is kept until a year after that day; one with no time limit is kept for as long as it can be used. Each session is a booking like any other and is kept the same way.
Payment requests. When a store sends you a payment request, we keep the email address and the name the creator typed, what it asks you to pay for, its due date if it has one, when it and any reminders were emailed to you (at most four emails in all, never two within a day, and none once it is paid, withdrawn or expired), and what became of it: the checkout opened for it, whether it was paid, the payment's reference and any refund Stripe reports, or, when the creator marks it as paid outside Stripe, how (cash, bank transfer or another way), the day and a short note of theirs. It is kept for 400 days from the day it was made and then deleted by itself; the creator can delete it sooner. Deleting yourself from that store (the privacy link at the foot of its pages) deletes every request of yours there and withdraws any still open. You are not added to the creator's list by a request. The payment itself is made on the creator's own Stripe account and kept there, under Stripe's privacy policy.
Proposals and agreements. When a store sends you a proposal or an agreement to sign, we keep the email address and the name the creator typed, each version of its text exactly as it was sent, with its SHA-256 fingerprint, and when it was emailed to you. If you sign it, we also keep the name you typed, the time, the sentence you checked, the version you signed, and a one-way code made from your internet address with a key of ours: never the address itself, and it cannot be turned back into it. The address you type when signing is compared with the one it was sent to and not kept beside it. It is kept for 400 days from the day the agreement was made and then deleted by itself; the creator can delete it sooner. Deleting yourself from that store (the privacy link at the foot of its pages) deletes every agreement of yours there, signed or not. The signed copy emailed to you and to the creator stays with each of you. You are not added to the creator's list by an agreement.
Gifts. When you buy something as a gift, we keep the recipient's email address, the name and the message you typed, and which payment it was, for about 13 months, so the gift can be handed over, shown on their list of purchases and taken back if the payment is refunded. We email the recipient once, with your name, your message and a link to open it; they are not added to the creator's list and receive nothing else from it unless they ask. You get the receipt. What was given is kept under the recipient's address, like a purchase of their own.
Starting before the 14 days end. Before you pay for something you can open right away, such as a download, a course or a membership, the checkout asks you to check a box about starting before a 14-day right to cancel ends. When you check it, we write “yes”, the version and kind of that sentence and the time on the order, and the confirmation email quotes it back to you. Switching a membership to another plan or to yearly payments asks the same box again, and the receipt quotes it. For a card payment it is kept on the order itself (on a switch, on the membership), in the creator's own Stripe account, for as long as the creator keeps their Stripe records. For a PayPal payment it is kept with our own record of that PayPal order, which we keep for 400 days for refunds, disputes and the creator's books, and then delete. Nothing else is kept for it: no new detail about you, no cookie and no tracking.
Pre-orders. When you pre-order something, we keep the email address you paid with, when you paid and which payment it was, for about 13 months after it last changed, so it can be handed over the day it comes out, shown on your list of purchases and taken back if the payment is refunded. We email you a receipt with the day it is expected, and once more when it comes out, with the way to open it.
When a store you bought from closes. From the day the store’s plan ends until it closes or stays open, we keep, for that store only: the email address of each buyer we email that it closes, so nobody is emailed twice and each can be told if it stays open; and, for each member, their last payment (the amount, the period it paid for and the address on the creator’s Stripe account), to refund the time paid for after the closing day from the creator’s account and to tell them if that could not be done. These are read from the creator’s own Stripe account and the store’s records, used for nothing else, and deleted the day the store closes or the day it stays open. The emails come from Marktmorgen, with our postal address.
Questions on a product's page. Some stores answer questions on their product pages. If you type one, your question and what that page already says in public are sent to a model run by Anthropic, which writes the answer; nothing about you goes with it, and the box says the answer is automatic. We keep the answer for a day, so the same question about the same page is not asked twice. When the page could not answer, we keep the question, the product and the day for up to about four months and show them to the store's creator, so they can see what their page is missing; we do not keep who asked. The network address your browser connects from is used, for up to a day, only to limit how many questions come from one place. Leave personal details out of a question: it is read by the model and may be read by the creator.
A store's AI assistant. Some stores have the Store assistant, a chat that answers questions on every page of the store, labeled as AI on every reply. If you write to it, what you write, the replies and the conversation so far are sent, with any email address, phone number or link you typed taken out first, to a model run by Anthropic, which writes the reply from what the store has published. Nothing else about you goes with it: not your name, not your address, not your network address. We keep the conversation for 24 hours after its last message, under a random code kept in your browser and nothing that names you, so the chat can carry on while you shop; then it is deleted by itself, and you can delete it at any time with “Delete this chat”. When it could not answer, the question and the day are kept for up to about four months and shown to the store's creator, without who asked. The network address your browser connects from is used, for up to a day, only to limit how many questions come from one place. If you ask for your question to go to the creator, you type your email address for their answer, and the question, the conversation and that address go into the store's inbox, where they are kept and deleted as described under a store's chat and inbox. Leave personal details out of a question: it is read by the model, and the creator may read it.
One next product after you buy. Where a store with the Store assistant has switched it on, the page after paying may show one more of that store's own products, at its published price, with “No thanks” to dismiss it. To leave out what you already have, the store's own Stripe account is asked, by the email address you paid with, which of its products that address bought there, and the store's own record of purchases it brought over is read; the answer is used for that and not kept. When the creator has set no product to follow the one you bought, an AI model run by Anthropic may choose among the store's products and is then labeled “AI suggestion”; it is sent only the products' titles, prices and descriptions, nothing about you. The product chosen for your order, and whether you dismissed it, are kept for three days under your order's reference, with no name or address, so the page shows the same one if you open it again. If you checked the box to hear from the store at checkout, and the store allows it, the same product is also mentioned in your order's confirmation email; no separate email is sent for it.
A reminder you ask for at checkout. Where a store with the Store assistant has switched it on, its checkout shows an unchecked box, “Email me a reminder if I don't finish this order” (in the store's language). Only if you check it and type your email address beside it do we keep that address, the sentence you checked, its version and the time, with the reference of that checkout, and send you one email from the store about an hour after that checkout closes unpaid. We rely on your consent for it, and typing an address without checking the box is never taken as one. To make sure you are not reminded of something you paid for, the store's own Stripe account is asked whether that checkout was paid and whether that address paid for the same products since; the answer is used for that and not kept. An AI model run by Anthropic may write one short line of that email from the products' titles and descriptions, labeled as written by AI; it is sent nothing about you. The email has a link that stops that store's reminders to you at once, and a one-click unsubscribe your mail app can use; pressing either withdraws your consent and keeps a one-way hash of your address for that store, as described under a reminder after an unpaid checkout above, so it never sends you one again. What you typed is deleted by itself three days after the checkout opened, sent or not, and at once if the store deletes you or you ask it to delete you. It is not shown to the creator and does not add you to any list.
Prices for your country. Some stores lower their prices for buyers in certain countries. To show you the right one, the country your internet connection is in, as our host reads it from your network address, is used while the page is drawn and when you start paying. It is not stored. When a lower price was given, the country and the percentage are written on that order on the creator's own Stripe account, so they can see why it cost what it did. On an order paid with PayPal, only the percentage is kept, with that order's record, never the country.
Bought for several people. When somebody buys a product for several people, they get a link to pass on. If you type your email address on the page it opens, we email that address one link, and the address is kept for 24 hours with it. If you open the link, we keep your address and when you took your place, with the purchase, for about 13 months, so the product can be opened on your address, shown on your list of purchases and taken back if the payment is refunded. Nobody who holds the link is shown who else took a place, only how many are left; you are not added to the creator's list and receive nothing else from it unless you ask. What you were given is kept under your address, like a purchase of your own.
Waitlists. When you join the waitlist for something a creator has not put on sale yet, we keep your email address, when you joined and whether you checked the box to hear from the creator otherwise, and we email you a button to confirm it. Once it is confirmed, you get one email when the product goes on sale; then the waitlist's addresses are deleted. Only if you checked the box is your address added to the creator's list, once confirmed. The creator sees how many people are waiting, not who. Unconfirmed sign-ups are kept until the product goes on sale, and a link in every waitlist email removes your address at any time.
Courses. When someone buys a course, we note the email address they paid with and when, so the course opens for them and modules that open over time open on the right day. The browser that paid keeps a cookie for a day so the course can open right away, and any browser let into a course keeps a cookie for 90 days so the student does not have to ask again. For each student we keep when they joined, when they last opened the course and which lessons they marked done; the creator sees this in their studio, and we email the student when a module opens for them. A student taken off a course by its creator is kept on a list so the course stays closed to them. To check who bought a course, we ask the creator's own Stripe account by email address.
Where you stopped in a lesson video. When a student watches a lesson video a store hosts with us, their own browser keeps where they stopped, so the lesson can offer to continue from there: in its storage, under mm:lp: followed by the course, the lesson and a code made on our server that cannot be worked out from their email address. It holds the second they reached and when, and is never sent to us. The speed they chose is kept the same way, under mm:lp-speed. A place is removed when the video is watched to its end and when they press Start over. One older than 90 days is never used, and is removed the next time that lesson is opened in that browser. Whenever the course page opens in that browser without confirming their access (because it ended, or because it could not be checked at that moment), all their places in that course are removed. The same browser also keeps the last lesson they opened, so their library on this site can offer "Continue where you left off": under mm:ll: followed by another code made on our server from their email address alone, it holds that lesson's address, its name, the course's and the store's names and when, and is never sent to us. It is never used after 90 days, and it is also removed with their places when the course page opens without confirming their access to that course. Clearing the browser's site data removes all of it at any time.
Comments under lessons. A student who comments under a lesson chooses a name, and we keep that name, what they wrote and when, until they or the creator delete it or the course is deleted. The creator and the other students of that course see the name and the words; nobody sees the student's email address. When the creator answers a comment, we email the student who wrote it, at most once an hour for each lesson. A creator who asked for it gets a notification on their phone with the lesson and the start of the comment, without the name.
Private notes on lessons. A student can write notes on each lesson of a course they are taking. We keep what they wrote and when, for that student alone: the creator, the creator's team and the other students never see them. A note holds at most 4,000 characters, and a student keeps at most 300 notes in one store, together at most 256 KB. All the students' notes in one store together take at most a tenth of the store's data room, so at least nine tenths of it always stay the creator's: past that, a new or longer note is refused and the notes already saved stay. The creator can neither see nor delete them. While signed in with the address they took the course with, the student can download its notes as a text file: from each lesson while the course is open to them, and from the course's own page also after the course is no longer open to them (after a refund, for example, or when a membership ends). The notes stay kept until the student empties them on the lesson or, after their access to the course ends, deletes them on the course's page, asks to be deleted from the store, or the store is closed.
A one-click offer after paying. When a product is followed by a one-click offer, Stripe keeps the buyer's card on the creator's account for payments the buyer makes while present, and a cookie in the buyer's browser, for two hours, lets only that browser take the offer. We keep a record of whether the offer was taken, tied to that order, for eight days.
Your library. So that you can find everything you bought from creators here in one place (marktmorgen.com/library), we keep, for each email address that bought something, which stores it bought from: the store's id only, under a one-way hash of the address. Not what you bought, when or for how much; each store's list is read from that creator's own payment records when you open it. It is kept for three years after your last purchase. When you ask for your library, we email a link that opens it for 24 hours, only if that address bought something, and the page says the same either way. The creators do not see it.
Your affiliate programs. So that an affiliate can see every store they promote in one place (marktmorgen.com/affiliate), we keep, for each email address that joined a store's affiliate program, which stores it joined: the store's id only, under a one-way hash of the address. Your link, where your application stands and your numbers are each store's own, read from that store when you open the page. It is kept for three years after you last joined or signed in. When you ask for the page, we email a link that opens it for 24 hours, only if that address is an affiliate somewhere here, and the page says the same either way.
Free copies, and a creator's list. When you ask a creator's store for something they give away for free, we collect your email address, what you asked for, when, and whether you checked the box saying you want to hear from that creator. The box starts empty. We send you one email, with the link to what you asked for, and nothing else. When you use that link, your address is added to that creator's list, marked with your choice, and the creator can download the list. If you never use the link, the request is deleted after 7 days and your address is not added to anything. To limit abuse, we also keep a one-way hash of your email address, and of your IP address, for one hour.
Emails from a creator. A creator on the Pro plan can email the people on their list who agreed to hear from them: those who checked the box when they got something free or bought, and those the creator imports after confirming that each of them agreed. We send those emails on the creator's behalf, under the creator's name, through our email provider. For each one we use your address, the email the creator wrote and a random code for your unsubscribe link. We do not put tracking pixels in them, and their links are not tracked person by person unless you allow it, as set out below. A link to the creator's own store carries a tag naming the email it is in, or one of two subject lines when the creator is trying two, each sent to a part of the list chosen at random. The tag is the same for everyone who got that email or that subject line: it lets the store count visits and sales by email, and says nothing about who you are. In a one-off email sent since November 6, 2026, each link first opens an address of ours, the same for everyone who got the email, so the creator can change where a wrong link leads after sending. Opening it counts as one request of the store, as a page of the store does. Nothing about who opened it, or when, is kept for that email or shown to the creator. As on every page of the store, to limit abuse, a one-way hash of the network address it is opened from is counted with that day's requests from the same address, never with the email. Which of a creator's automatic emails reach you is decided by what their list already holds about you — what you got or bought from them, and any labels their import brought or their automatic emails gave you (a step can give a label, take one off, or start another of their automatic emails) — and never by whether you open an email. When a creator narrows an email to some of their buyers, opens their task agenda or looks a buyer up, we read their sales once and keep that copy of who bought what for one hour, so the count they see says when it was read; it is then deleted, and deleted at once if you ask us to delete your data.
Which links you use, only if you allow it. Where you join a creator's list, a second box, empty and separate from the first, asks whether the creator may see which links in their emails you use, so their automatic emails can send you what fits. If you check it, we record when. Then, in those automatic emails only, each link to the creator's own store carries one more code made from your unsubscribe code, which cannot be turned back into it. When such a link opens a page of the store, that page tells us which email the link was in, and the code is taken out of the address bar. We keep which of those emails you used a link in, for 90 days after the last one, and the creator's automatic emails use it to decide whether you get a particular email: for example, one sent only to those who used the link in the email before, or only to those who did not. The creator does not get a list of what you did. Nothing is recorded for a link to anywhere else, for a one-off email, or for opening an email. Every email that carries the code has a line at its foot to stop it: one press, and nothing more is recorded, what was recorded is deleted at once, and you stay on the list. Unsubscribing stops it too. If you do not check the box, nothing about which links you use is recorded, ever. In the European Economic Area and the United Kingdom, the legal basis is your consent. Our email provider tells us when one of these emails could not be delivered to your address for good, or when you report one as spam: we record that, and when, for your address on that creator's list, you are not written to by that creator again, and for ten days we keep a one-way hash of your address so that it is counted once. When you unsubscribe — one press, from the link or your mail app's own button — we record it and when, and you are not written to by that creator again unless you check their box again yourself.
A creator's community. When a creator opens a community on their store, we decide who may come in by looking up the email address a person types on the creator's own Stripe account, on that creator's list for something free, or among the buyers the creator brought over from another platform, and we email that address a link that works for one hour. Using it sets a cookie for that store in their browser for 90 days, the same one a course uses. For each member we keep their email address, the name they choose to be seen by, whether they chose to be listed in the member directory and to be emailed announcements, when they joined and were last there, and whether the creator muted or removed them. We keep what members write: posts, comments, the pictures they add, likes, and reports of a post or comment. Posts, comments, pictures and likes are seen by the other members and by the creator. The directory shows only the chosen name, and only of those who asked to be listed. A member's email address is seen by the creator and never by other members. What is written is kept while the community exists, until its author or the creator deletes it; deleting a post deletes its comments, likes, reports and picture. A creator may choose to approve posts or comments before they are published. Until then, what is waiting for approval is seen only by its author and the creator; if the creator does not publish it, the author is told, and if nobody answers within 30 days it is not published. A short note about what was not published is kept for its author for at most another 30 days. Deleting a member deletes what they had waiting too. Who reported something is kept for 90 days, so each member's report counts once. The answer about whether someone may come in is kept for up to five minutes, a record of each announcement emailed and who it went to for up to 60 days, the code in a member's unsubscribe link with their member record, and, to limit abuse, one-way hashes of the address and network address that asked for a link for one hour.
An email kept for members. When a creator publishes an email on their store for the buyers of some products only, we decide who may read it by looking up the email address a person types on the creator's own Stripe account, on that creator's list for something free, or among the buyers the creator brought over from another platform, and we email that address a link that works for one hour. The link and the address it was sent to are kept for that hour. Using it sets the same cookie for that store a course and a community use, for 90 days. The answer about whether an address may read it is kept for up to five minutes, and, to limit abuse, one-way hashes of the address and network address that asked for a link for one hour.
Live events in a community. When a member says they are coming to a creator's live event (an RSVP), we keep that they are coming and when they said so, under a one-way key made from their email address, with the event; giving the place back removes it. The creator and the people on their team see who is coming, with the name and email address the community keeps for each member. Reminders a day and an hour before go only to members who asked for the community's emails; a move or a cancellation is emailed once to everyone coming. For each of those emails we keep a record of it and of who it went to for 30 days, so it is never sent twice. For an event kept for the buyers of some products, the answer to whether a member holds one is looked up on the creator's Stripe account and kept for up to five minutes. An event, with the list of who is coming, is kept until the creator deletes it once it is over or canceled, or until it makes room for a newer one after 500 are kept. When a member presses Join here, the event's video room loads from Jitsi Meet inside the page, with the name they chose in the community filled in as their name in the room, where the others in it see it. A replay is a YouTube, Vimeo or Loom video that loads from that service only when a member presses play, and so does a video on a creator's sales page, when a visitor presses play or the button that opens it in a window, where it then starts playing.
Moving a store from another platform. A creator can bring spreadsheets from another platform. The file is read in their own browser, and we receive only the columns they match: for a list, email address, name, labels and consent; for products, title, price, description and link; for past buyers, email address and product. We keep the rows as they came, which rows were already seen, the report of rows not brought in (each with its row number, column, reason and value), the buyers still to be emailed, and the import's own record (the file's name, who started it and its counts) for 14 days after the import began, and then delete them. Contacts are added to the creator's list only when the creator confirms that the people in the file agreed to hear from them; each is marked as imported, with when, and keeps the name and labels from the file. An address that unsubscribed from that creator is never added back. For each past buyer we keep which products they were given, when and by which import, stored against a one-way hash of their email address, for as long as the store exists; nothing is charged, no receipt is made, and these are never counted as sales. When that person opens the store's list of purchases or its community with that address, we use it to look up what they were given. If the creator checks it, each past buyer gets one email from the store's name, through our email provider, saying what moved and how to open it. We send it on the creator's instruction and on their word that these people bought from them and may be told so, which we cannot check against the other platform. A store may send up to 20,000 of these in 30 days, and for that we keep only a count.
Members moved from another platform. A creator can also bring the members of a membership they ran elsewhere: for each, we receive the email address, the membership, the date it would next renew there and, for a membership with several prices, which one. Nobody is given a membership because of it. For each member we keep that address, membership, price and date, the import that brought them, a random link of their own, and whether they kept the membership here, until the store is deleted; the link stops working 30 days after the renewal date. Each member gets one email from the store's name, through our email provider, with that link, and one reminder a few days before the date if they have not kept it by then. Before the reminder we ask the creator's Stripe account whether that address already holds the membership, so somebody who kept it is not written to. We send these on the creator's instruction and on their word that these people are their members, which we cannot check against the other platform; they count within the same 20,000 in 30 days. Keeping the membership is a checkout on the creator's own Stripe account, like any purchase in their store.
A creator's own tools, through the API. A creator can give their own tools a key that may also write. With it, a tool can put somebody on the creator's list, on the creator's word in that request that the person agreed to hear from them, kept as an imported contact is; change that person's labels; and give or take back a product, kept as a past buyer's is, marked as given through the API. Nobody who unsubscribed is added back. When the tool asks, the person gets one email from the store's name, through our email provider, saying what they were given, within the same 20,000 in 30 days as the emails above. We keep how many of these a store made each day, for a day, to hold them to their limits. Any key of a store, one that only reads included, can also list the store's sales with each buyer's email address and name, read from the creator's own Stripe account when the tool asks; we do not keep that list.
Discount codes in a link. When someone opens a store's page through a link carrying a discount code, a cookie named nl_code_ followed by the store's address holds that code for seven days, so it applies at that store's checkout without being typed. It holds the code and nothing else, and is sent to no other store.
A store's cart. What someone adds to a store's cart is kept in their own browser's storage, under mm-cart: followed by the store's address: the products' ids and nothing else. Those ids are sent to us only to show the products' prices when the cart is opened and to check out, and are not kept. Nothing in it is sent to another store, and it is emptied once they have paid.
Tests on product pages. A visitor to a product's page gets a cookie named nl_ab holding one random number from 0 to 999, for 90 days, so that when the creator tests two headlines, or two versions of the whole page, the same visitor keeps seeing the same one. For each test we count how many times each version was seen and how many checkouts were opened from it, and nothing about who. Visitors in the European Economic Area, the United Kingdom, Switzerland or Brazil, or whose country we cannot tell, get no such cookie: they see the first version and are not counted.
Where a store's buyers came from. When someone reaches a store's page from somewhere we can name — a link the creator tagged, another site, or the Instagram or TikTok app — a cookie named nl_ch_ followed by the store's address keeps, for 90 days, the name of that place and of the first such place in the last 90 days, with the two dates. If they then buy within the window the creator chose (7, 30, 60 or 90 days after that visit; 30 unless they change it), those names are written on the payment in the creator's own Stripe account, so the creator can see which of their channels brought the sale; renewals of a membership carry them too. It holds nothing else, identifies nobody, is sent to no other store, and we keep no copy. Visitors in the European Economic Area, the United Kingdom, Switzerland or Brazil, or whose country we cannot tell, and anyone whose browser sends Global Privacy Control, get no such cookie: their purchase is credited only by the tags on the page they bought from.
How far a sales page is read. When a visitor leaves a product's sales page, the page sends the id of the furthest of its sections they saw, and we add one to that section's count. On a store's own page it sends the furthest item they saw — a product, a link or a part of the page — where it stood, and the item they clicked, if any, and we add one to that day's count of it. Each page decides at random to send this for one visitor in eight, and for nobody else. On a sales page it can also say how far into the page's video they got, and, where the creator turned the question on, which of five answers they tapped when asked what was stopping them from buying. No cookie is set and nothing about the visitor is sent or kept; the device remembers only that the question was asked, so it is not asked again.
Searching a store. When a search of a store finds nothing, we count the words searched for on that day, so the creator sees what visitors looked for and could not find. Only the words are kept, not who searched.
Where a buyer heard of a store. After paying, a buyer may be asked one question, which they can skip: where they heard of the store. If they answer, we check that the order is a paid order of that store, add one to that day's count of the answer and the order's amount to its total (and, when the order had no channel, to a second count and total of the same answer, so the creator can see what such sales were put down to), and mark the order as answered for 30 days so it is counted once. The answer is not kept with the order, the buyer or the time, and the creator sees only the counts.
A store's latest purchases. Where a creator switches it on, their store's pages show a card with a recent purchase: which product, how long ago, and the country the card was billed in, as Stripe gives it. For that, we keep the product, the time, the country and the payment's reference of the store's 20 latest purchases for up to 8 days, and use the reference only to leave out a refunded one. Nothing about who bought is kept for it or shown: no name, address, email, city or picture.
A creator's affiliate program. When someone follows an affiliate's link to a store, a cookie named nl_via_ followed by the store's address holds the affiliate's code and the time of the click, and the earliest click that visitor still carries, for up to 400 days, subject to the browser's own limits; it may expire sooner. A purchase counts for the affiliate only within the window the creator set, measured from whichever of those two clicks that creator credits. Visitors in the European Economic Area, the United Kingdom, Switzerland or Brazil, or whose country we cannot tell, are asked first, because the rules there require consent: the cookie is set only if they allow it, and their answer is kept in their browser for that store. To count a click once per visitor per day we keep a one-way hash of the visitor's network address and browser for two days. When a purchase counts, we note which product, when, what was paid before tax and in all, the share it earns, and whether it was credited by a click, by a discount code, by the buyer already belonging to that affiliate or by the buyer having been that affiliate's confirmed lead — and never the buyer's name or email address. Where a creator credits memberships and payment plans, the affiliate, the share and the terms ride on the subscription in the creator's own Stripe account, and each payment is read from there when the program's records are opened, not kept by us. When a click on an affiliate's link came from a paid search ad (the address carries Google's or Microsoft's ad click id, or is tagged as paid search), we add one to that affiliate's count of such clicks, and nothing about the visitor. A creator may give one of their own discount codes to one affiliate, and then a purchase that used that code counts for them with no cookie involved; what we keep for that is which code belongs to which affiliate, and nothing about whoever typed it. A creator who pays affiliates per lead may also credit a one-off purchase to the affiliate who brought the buyer as a confirmed lead before they bought. This applies only when no link, code or earlier purchase already credits it. To find it, we compare the email address the order was paid with against that program's leads. Nothing is kept for it beyond what any credited purchase keeps. A creator may also ask that a buyer credited to an affiliate stays credited to them for every later purchase. Where they have, we keep a one-way hash of the buyer's email address together with the store's own id, and the affiliate it belongs to — no address, no name and nothing about what was bought. The hash cannot be turned back into an address or lined up against another store's, it is never shown to the affiliate, and a buyer who asks the creator to be forgotten is removed from it. Where a creator lets buyers join without applying, a buyer who presses “Get my link” joins with the email address their order was paid with, which we read from the creator's Stripe account for that order. When someone applies to be an affiliate, we keep their email address, the note they wrote, their code, when they applied and what the creator decided, the PayPal address they choose to be paid at, if they give one (we email the address they joined with whenever it changes), their clicks and sales, and the payments the creator records to them with the date and reference the creator types. An affiliate who signs in to their page keeps a cookie named nl_aff_ followed by the store's address, for 30 days. Where a creator chooses to take out affiliates with no sale and no lead for a time they set, we keep the date each affiliate was last warned. Before an affiliate is taken out, we email them at the address they joined with, at least 14 days ahead. An affiliate taken out keeps their records, as when a creator removes them by hand. Where a creator pays affiliates per lead (since October 18, 2026) — an email sign-up to their list the person confirmed, a free product claimed from its emailed link, or a booked call that took place — the affiliate the visit came through travels in the emailed confirmation link, or on the booking in the creator's own Stripe account, and once the lead is confirmed we keep, for it: the person's email address; a one-way fingerprint of that address with the store's own id, so one person is one lead in that program; which affiliate it is credited to; the kind of lead and the product or booking it was; when it was confirmed; the amount and the terms then; and what the creator decided, with the reason they gave. The creator sees the address; the affiliate sees only its first letter and its domain. A person deleted from the store has their address removed from the lead; the lead stays, as the affiliate's record, and so does the fingerprint, which cannot be turned back into the address, so they are not counted again. The creator sees all of this; an affiliate sees only their own figures. It is kept with the store's records. We never hold or pay out an affiliate's money: the creator pays them. A creator who pays from their own PayPal through us gives us the Client ID and Secret of an app in their PayPal Business account; we keep the Secret encrypted, never show it again and delete both when they disconnect. Each time they pay, we send PayPal each affiliate's email address, the amount and a note, and PayPal sends the money from the creator's PayPal to the affiliate's, under PayPal's own privacy policy; we keep which PayPal batch and payment paid which affiliate.
Creators inviting creators. A creator's studio gives them an invite link for other creators. Opening it sets nothing. Pressing “Accept the invite” sets a cookie named nl_invite holding the invite's code, for 60 days, and it is removed when a store is made. When the first store of a new account is made with it, we keep which store invited which, and when. To add the credit the invite earns, we read from our own Stripe account the payments the invited account made to us, and keep, for each, the amount credited, its date and whether it is on the plan yet. The inviting creator sees the invited store's public name and address, when it was made, whether it is in its trial, paying or not, and the credit it earned them, and never its email address or what it sells or earns. Kept while either store exists.
Calendars a creator connects. A creator can give us the private iCal address of up to three of their own calendars. We store the address, never show it again once saved, and use it only to read when they are busy; we keep only the busy times, never a title, guest or place, and each reading for up to six hours. The calendar's provider sees our request for it. A creator also gets a private address of their own that lists their upcoming calls and sessions with the name and email address of each buyer, for the calendar app they subscribe with; replacing that address turns the old one off. We keep the last copy of that list made for their calendar app for up to 40 days; once the store is deleted or closed, that copy is never shown again, and it is erased within those 40 days.
Webhooks a creator adds. A creator can give us up to five web addresses of their own, such as a Zapier or Make hook. When a sale, a change to a membership, a confirmed request for something free, a booking, a moved booking or a refund happens in their store, we send that address a message with its details, which can include the buyer's name and email address, the product and the amount. What happens to it there is the creator's choice and responsibility. We keep each address and its signing secret until the creator removes it, a mark of each event sent for 30 days so it is never sent twice, and each delivery, with the answer the address gave, for up to seven days. When a free copy or a list sign-up could not be passed on to those addresses at once, we keep that event, with the same details, for up to seven days to try again, and never send it about someone deleted from the store.
Forms and quizzes on a store's pages. When someone sends a creator's form, we keep their answers, when they sent them, the page they came from and, for a quiz, the result they were shown. For a scored quiz we also keep the total and each category's score, worked out from the points the creator gave each answer; nothing else goes into it. The newest 2,000 responses of each form are kept, for the creator, and are deleted with the form, or when the person is deleted from the store, found by the email address in their answers. The result page's web address names the result and the score, never the person's answers or email address. The creator is the controller of these answers.
License keys. When a creator sells a product with license keys, we keep each key with the sale it went to, when, and the buyer's email address, so the buyer can see it again and the creator can see who has it, and whether the creator revoked it. Anyone can ask whether a key is valid; the answer says nothing about who bought it. When a creator limits a key to a few devices, we keep, for each device their software names, a one-way code made with a key only our server holds, different for every license key and never the identifier the software sent, and when the buyer freed a device. Nobody can turn a code back into the device or match it on another key. These codes are kept with the key and go by themselves 400 days after their last change. Keys are kept with the store's records.
Course quizzes and certificates. For each student and quiz we keep how many tries they used, their last answers, their best mark and whether they passed, with their course progress. A certificate keeps the name exactly as the student typed it, the course title, the creator's name, the student's email address and when it was issued or withdrawn. Its page shows the name, the course, the creator and the date to anyone who has its address, is kept out of search engines, and never shows the email address. Certificates are kept for as long as the store that issued them is open, so the page goes on proving what it says; a withdrawn one says it was withdrawn. When the store closes (section 6), its certificates go with it. A student who wants theirs withdrawn asks the creator.
Course assignments. When a creator gives a lesson an assignment, we keep what each student hands in for it: what they wrote, the file they added with its name and size, when, how many times, and what the creator wrote back and when, with their course progress. The file is kept privately with the creator's store files, where only that student, the creator and the creator's team can download it; a file uploaded and not handed in is deleted within about a day, one replaced by a new one is deleted at once, and everything is deleted when the creator removes the assignment, the lesson or the course. When the creator asks AI to draft a reply, the assignment and what the student wrote are sent to Anthropic to write it, never the file. A student who wants their work deleted asks the creator.
Discord access. When a creator connects their Discord server, a buyer of a product that gives roles there can press “Join the Discord” and agree on Discord's own page. Discord then tells us their Discord account's id and name, and lets us put them in that one server. We keep, with the creator's records, that id and name, the address that bought, which of the creator's products it held and which roles it was given, and check every few hours, against the creator's Stripe account, whether it still holds them. We do not keep the permission Discord gave beyond that moment, never read or send messages there, and never see the buyer's Discord password or email. Once the address holds none of those products, the roles are taken back and the record is deleted; it is all deleted when the creator disconnects the server.
Stamped PDFs and EPUBs. When a creator switches on stamping for a product, every page of the PDF a buyer downloads carries the buyer's email address, the date and the end of the order number, and an EPUB carries the same line hidden inside the book's files, where reading apps do not show it but a copy keeps it. The stamped copy is made by our own code, is kept privately beside the creator's file so a later download gets the same copy, and is deleted with that file; a note of which copy belongs to which sale is kept for about 400 days. Anyone the buyer passes the file to can read that line.
A store's team. A creator can invite up to five people to help run a store. For each invitation we keep the address it went to, the role, when it was made and when it runs out, seven days later; the link in it works once. For each member we keep their sign-in address, their role and when they joined, and, for each person, which stores they are on, so their studio can find them. A store keeps an activity log of its last 500 lines: when, who (their sign-in address), their role and what they did, such as a change they made in the studio, a file they downloaded or a change to the team. The owner sees the team and the log, and is emailed when someone joins or changes role. The team, its invitations and its log are deleted with the store, and a member taken off the team or who leaves is removed from it at once.
Passkeys and new browsers. A creator can add up to ten passkeys to their account. For each we keep only the public half of the key, a counter, the name they gave it, the kinds of connection the device reported, whether it is kept in a synced keychain, and when it was added and last used; the private half never leaves their device. Each is kept until they remove it. Signing in with a passkey sets a cookie named nl_pk for five minutes, for that one sign-in. Every sign-in also sets a cookie named nl_device holding a random code for that browser, for 400 days, and we keep a one-way hash of that code with the account, up to 100 browsers, until 400 days after the account's last sign-in. When an account that has signed in before signs in from a browser it has not used, we email its owner when it happened, how, and the browser and system as the browser names them; we do not keep that description. In the studio, a cookie named nl_store remembers which of an account's stores was last open, for a year. A creator who adds a recovery address has it kept, to email a code to it once and a link when they ask for one from the login page; after a login through it, we keep until when what matters is locked for that login, and for 30 days after. A creator who turns on two-step login has the secret their authenticator app shares with us kept encrypted, a one-way hash of each recovery code not yet used, the recovery address they gave (which we write to only to confirm it and when they ask for a way back in from the login page), the last code used and, after a login let in without its second step, the day two-step login turns off and which sessions are locked until then, until they turn it off. Between the emailed link and the code, a cookie named nl_2fa holds a random code for that one login, for ten minutes.
Email drafts. For each draft of an email to a creator's list we keep its subject, its text, who it is meant for, who last saved it (their sign-in address) and when, until it is sent or deleted, up to 20 per store.
Sending a purchase email again. A creator, an Admin or Support can have a buyer's purchase email sent again; it goes only to the address the buyer paid with, read again from the creator's Stripe account.
An email platform a creator connects. A creator can connect their own Mailchimp, Kit, beehiiv or MailerLite account with an API key. We encrypt the key before it is stored, keep its last four characters to show them, and delete it when they disconnect. When someone who agreed to hear from that creator asks for something free and confirms it, or buys and agreed, we send that platform their email address, their first name when the payment carries a name, and the tags the creator chose, to add them to the audience, form, publication or group the creator picked. Nobody who did not agree is sent, and we then keep no address for them. For each person sent we keep a record of how it went, with their address and first name, for up to a week, the last 50 of them in the creator's studio, and a one-way hash of each person and event for 30 days so nobody is sent twice. What happens on the platform is governed by the creator's own account there and that platform's privacy policy.
Phone notifications. When a creator or someone on their team turns notifications on for a device, we keep what the browser gives us to reach it (its push address and keys), a label such as “iPhone · Safari,” which events it wants, when it was added and whose it is, until it is removed or the browser turns notifications off, with how the last send went. A notification says an amount, a product title or a time, never a buyer's name or email address; it is encrypted for the device and passes through the push service of that browser's maker, such as Apple, Google or Mozilla. We keep a mark of each event sent for 40 days, so it is never sent twice.
Marktmorgen Path. When a store's owner begins Path, we keep their four answers (a monthly goal of their own, what they know how to do and want to make something about, the minutes a day they have and where their audience is), their time zone, the days they opened Path (the latest 60), the best level the store reached and when, and for ten minutes at a time the last reading of the store's own counts and money: visits from social networks, visitors, short links, addresses left on the store, and the paid orders and refunds on the creator's own Stripe account, as counts and amounts, never who bought. The goal is only ever shown to its owner as their goal; nothing in Path predicts what anybody will earn. Missions are read from what the store already records and are never stored as done. Your answers and money remain private. We also keep a private return-step date and a fingerprint of your store introduction. This keeps the same small step in place when you reload; opening it never completes it. These markers go with your Path when you delete it or close or delete your store. Level certificates are generated only when you request a download, from your private saved Path level. They contain no name or contact details. Sales amounts are off by default. No public certificate page, separate stored certificate or automatic message is created; a downloaded copy remains under your control. If you request optional AI wording, only a fixed instruction goes to the writing provider. Your free-text answers, personal goal, money and buyer details are not sent, and the suggestion never changes recorded progress. Only if you explicitly join the mission board do we share a generated pseudonym, a count of verified missions and its reading time with other Path owners. The board never shares your real name, store address, goal, answers, level or sales amounts. Leaving removes the shared entry and keeps your private Path. Deleting Path, or closing or deleting the store, removes its board entry too. Manage Path board participation.
Reviews. A buyer can review what they paid for. We check the order on the creator's own Stripe account, and keep the stars, the words, the photo if the buyer adds one (made smaller on their device before it is sent, and kept as a picture file on our storage provider until the review, the photo or the product is deleted, or the creator takes the photo off), the name the buyer chose to show (or “Verified buyer”), the order reference and the payment it came from, when it was written and changed, whether the creator hid it or answered it, and whether the payment was later refunded. The buyer's email address is not kept with the review and is never shown; the review's code is a one-way hash that includes it, so one buyer has one review per product. The review, with the chosen name, is public on the store; its buyer can change or delete it, and the creator can hide it but not change it. Deleting the product deletes its reviews. If the creator switches on the email that asks for a review, we put each paid order on a list with when it was paid, send its buyer one email on the creator's behalf and, only if the creator chose it and the buyer has not reviewed yet, one reminder 3 to 14 days later, and keep a mark that its buyer was asked (and reminded), for 120 days. The link in that email, tied to the order and the address it went to, works for 60 days; its link to stop being asked works for 400 days, and pressing it keeps a one-way hash of the address for that store for good, so that store never asks again. When the creator asks for an AI summary of a product's reviews, the words of up to 60 of its newest reviews shown on its page are sent to Anthropic, with any email address, phone number or web address taken out and without the name or address of whoever wrote them. A summary is kept at most once a week for each product, but a try that fails or finds no theme can be made again at once, and each try sends those words again. The summary it returns keeps only the themes and how many reviews say each, never a review's words, who wrote it or which reviews were read; it is kept for 8 days, with the time it was made, and is deleted at once when a review it counted is deleted, hidden, refunded or rewritten.
Video rooms. When a creator chooses a video room for their calls, each booking, or each time of a group call or session, gets a Jitsi Meet address with a random name. We keep it for 60 days after the call and put it in the booking emails, reminders, calendar files, the creator's bookings feed and the buyer's list of purchases. Jitsi Meet (meet.jit.si) is run by 8x8, not by us: whoever opens the room uses that service under its own privacy policy, and the first person in may be asked to sign in to it with an account such as Google. We send Jitsi nothing ourselves. A community's live event has a room of its own, made with the event, as the section on live events describes.
Google Calendar or Zoom, if a creator connects it. A creator can connect their own Google Calendar to their store, so that an event with a Google Meet link is made on it for each booked call set to Google Meet and, if they choose it, for a community's live event. A creator can connect a Zoom account in the same way, once Zoom approves our Marketplace listing. This section says what happens then. None of it happens unless a creator connects one. Only the store's owner and its Admins can connect or disconnect it, and the owner is emailed each time.
Google. When a creator connects Google Calendar, we ask Google for their account's identity and email address (openid, email), to show which account is connected, and for one permission, https://www.googleapis.com/auth/calendar.events. We use that permission only to create, change and delete the events of calls booked through their store, and of their community's live events, each with a Google Meet link, on their primary calendar. We do not read, change or delete any other event, and we read nothing else from their calendar or their Google account. What we send Google: for a one-to-one call, a title with the product and the buyer's name (or their email address when there is no name), a description with the store's address and the buyer's email address, the time, and the buyer's email address on the event's guest list; for a group call or a session on dates, the product's title, the time and each buyer's email address on the guest list, up to 200, set so that guests do not see one another; for a live event, only its title, its time and the address of its page, and no member's name or email address. Google is told not to email anyone about these events: the booking emails come from us. When a booking is moved the event moves with it, and when it is refunded in full the event is deleted or the buyer taken off the guest list.
Marktmorgen's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use that information only to make and keep these meetings, never for advertising; we do not sell it, transfer it to anyone else except as needed to provide this feature or as the law requires, or use it to train any artificial intelligence model; and no person reads it unless the creator asks us to for support, it is needed for security, or the law requires it.
Zoom. When a creator connects Zoom, we ask for permission to create, read, change and delete the meetings of the Zoom user who connects, and to read that user's own profile for the name and email address shown in the studio. We only change or delete meetings we made, and we do not read the user's other meetings, recordings, chats or participant lists. What we send Zoom: for a one-to-one call, a topic with the product and the buyer's name (or their email address when there is no name), an agenda with the store's address and the buyer's email address, and the time; for a group call or a session on dates, the product's title and the time; for a live event, only its title, its time and the address of its page. The link that starts a meeting as its host is asked of Zoom when the creator presses Start, shown to them, and never stored.
What we keep, and how it ends. For each connection we keep the account's ID, email address and name, when and by whom it was connected, and the access and refresh tokens the provider gives us, encrypted at rest; the tokens never leave our servers. For each meeting we keep which account made it, its ID, link, title and time and, on Google, its guest list, until 60 days after the meeting. We keep a short log of problems with a connection for 30 days, and each consent in progress for ten minutes. When a creator disconnects from the studio, we ask Google or Zoom to cancel the token, so that access ends on their side too, and delete the connection and its tokens. If Google or Zoom does not confirm that our access ended, we say so on the screen and tell the creator how to remove our app in their Google or Zoom account themselves. Meetings already made stay on the creator's calendar or Zoom account. If the creator removes our app from their Zoom account, Zoom tells us and we delete every connection that user made, with its tokens, at once. We then keep, for one day, a scrambled form of that Zoom user ID and the time Zoom told us, only so that a connection being finished at that very moment is not kept either. If the creator withdraws our access in their Google account, we stop using the connection and tell them, and disconnecting deletes it.
Meta ads. A creator can connect their own Meta ad account, so their numbers read what their ads cost. We ask Meta only for permission to read their ads (ads_read), and we read only, once a day, what each campaign spent on each day and on each platform (Facebook, Instagram, Threads, Messenger, the Audience Network), for the last 30 days. We never ask for, and never receive, anything about the people who saw or clicked an ad, and we never change or create ads. We keep the Meta user ID of whoever connected it, the ad accounts' IDs, names and currencies, the access token Meta gives us, encrypted at rest and sent to nobody but Meta, and what was spent, kept a week to a line after 30 days and for 400 days at most. When the creator disconnects from the studio, we give the permission back to Meta and delete the connection, its token and every figure read from it. If they remove our app in their Facebook settings, or ask Meta for their data to be deleted, Meta tells us and we do the same at once, and tell the store's owner. We then keep, for one day, a scrambled form of that Meta user ID and the time Meta told us, only so that a connection being finished at that very moment is not kept either.
Comparisons between stores. To show a creator how their store's rates sit beside stores of its size, we keep, for each store whose numbers are read in the studio or for the weekly email, four rates over the last 90 days (visits that became a sale, checkouts that were paid, sales refunded, buyers who had bought before) and the size band of its visitors, for three weeks. Nothing about any buyer is in it. From them we work out, once a day, each band's middle half and median, and only from at least 10 stores; that is all any creator is shown, and no store is named or can be picked out. The demo store and suspended stores are left out.
A store's chat and inbox. When a visitor writes to a store through its chat or its contact form, we keep the address they give, the name if they give one, and the messages, for that store's team to answer, and for 180 days after the last message. The store's answers go only to that address. A code kept in the visitor's browser, and in the link of each answer's email, opens the conversation again; nothing else does. Where the creator asks for a suggested answer, the messages are sent to Anthropic to write it, with addresses, phone numbers and links taken out first, and the visitor's name and address are never sent.
Usage and technical data. We may collect information such as IP address, browser type, device type, pages visited, referring URL, and approximate location derived from IP address. This helps us operate, secure, and improve the Services.
Communications. If you email us, we keep the content of that correspondence and your contact details so we can respond.
Creator research answers. If you fill in the form at marktmorgen.com/creators, we collect your name, email address, country, the platform where you sell, the store or profile link you choose to share, your answers, the date you sent them, and the consent choices you checked. To limit abuse, we also keep a one-way hash of your IP address for one hour; we do not store the IP address itself with your answers.
Research outreach. If we contacted you first to ask about your experience as a creator, we used business contact details you had made public: your name, your business email address or social media profile, your store or profile link and, for UK companies, details from the public Companies House register. We use them only to send that research message and to continue the conversation if you reply. Our legal basis is our legitimate interest in understanding what creators need before we build a product. You can object at any time by replying “stop” or by emailing us, and we will not contact you again.
Outreach by creators. A creator can use their studio to prepare one email to a business they name: a proposal to sponsor them, to sell their product for a share, or to buy from them. For that, a reader that identifies itself as MarktmorgenOutreach opens up to four pages of that business's own website, once, and we keep, for that creator's store only: the address the business printed there, the page it was printed on, the words around it, the date, the draft, and what became of it (sent, answered, or asked to stop). Addresses are taken only from the business's own website and only at its own domain; in the United Kingdom, Ireland, France and Sweden only an address that names a desk, not a person, can be used. We send none of these emails: the creator sends each one from their own mailbox and is its sender. Our legal basis is the legitimate interest of that creator, and ours, in one relevant business proposal reaching the address a business published for being written to. Every such email ends with a link that closes your business to that store, or to every store here, in one press and for good; and a robots.txt rule for MarktmorgenOutreach keeps the reader off your site entirely.
2. How we use information
We use personal information to:
- create and manage your account;
- process subscriptions, renewals, cancellations, and refunds, and email you before a charge you might not expect: the first one after your free trial, and each renewal of a yearly subscription;
- provide the Services: host your store page, keep the files you sell where only you can reach them, and hand a file to a buyer who paid you for it;
- send you a free copy you asked a creator's store for and, once you use the link we sent, add your address to that creator's list with the choice you made;
- communicate with you about your account, billing, and service updates;
- detect, prevent, and investigate fraud, abuse, and security incidents;
- comply with legal obligations;
- improve the reliability and quality of the Services; and
- if you answered our creator research, read your answers to decide what to build next and, only if you checked the matching optional box, email you follow-up questions about your answers or tell you when we launch a product for creators. Each of these is a separate choice, and we contact you only by email.
Where the GDPR or similar laws apply, we process personal data on the following legal bases: performance of a contract (providing the subscription), legitimate interests (security, service improvement, and necessary communications), consent (where we ask for it, such as the creator research form), and legal obligation. You can withdraw consent at any time by emailing us; this does not affect processing that happened before you withdrew it.
4. If you buy from a creator’s store
The store belongs to the creator, not to us. For the personal data of that store's buyers, and of the people who ask it for something free, the creator is the controller and Marktmorgen is their processor: we handle that data to run the store on their behalf and on their instructions, and we do not use it for our own purposes, do not sell it, and do not email a creator's buyers or list to market anything of ours.
The same is true for the members of a creator's community, the people who apply to their affiliate program, their students' quiz answers, handed-in work and certificates, and their buyers' reviews: the creator is the controller, and we handle that data on their behalf. When a creator connects an email platform, Google Calendar, Zoom or a Discord server, or chooses Jitsi Meet for their calls and events, that is the creator's choice, and the data sent or used there is governed by the creator's account and that service's own terms. The same is true when a creator adds an ad pixel or asks us to send conversions to an ad platform from our server: the creator decides it, the platform receives it under its own terms, and the rules for when anything is sent at all are the ones in section 1, under ad measurement. So too when a creator downloads their buyers' addresses for an ad audience and uploads them: that use is the creator's, under their own privacy notice.
In practice this means a request about your data as a buyer — a copy of it or a correction — is answered by the creator you bought from. Write to them first. If you write to us instead, we will pass it on and tell you we did. Deleting it you can do yourself, at once, as section 8 says; the creator is told it was done.
When a creator's store closes, what it kept about you as its buyer is deleted with it, and so is your access to what you bought there (section 6, when a store closes). The payment itself stays on the creator's own Stripe account; we keep no copy of it.
Two things stay ours in that situation: the security of the systems the data sits in, and the legal obligations we have to keep records of our own, such as fraud prevention and anything the law requires us to retain.
6. Data retention
Account and billing records are kept for as long as your account is active and as needed for tax, accounting, and legal purposes. Support emails are retained as long as needed to resolve your request and maintain a reasonable business record.
The files a creator sells, their lessons' videos and their podcast's episodes, the files their students hand in and the pictures in their community's posts are kept until they are removed with what they belong to. Where a store's plan has ended, they are deleted 30 days after the plan ended, after three emails to the store's owner; for a plan that ended before October 18, 2026, only where the store keeps more than a store with no plan may (Terms of Service, section 8).
When a store closes. A store whose plan ended on or after October 18, 2026 closes 30 days after its plan ended, after the three emails above (Terms of Service, section 8). Its files go that day, and within 14 days, usually the same day, everything else it kept with us is deleted: its page, products, pages, posts, courses, community, contacts and their lists, forms and their answers, numbers, settings, its courses' certificates, and its buyers' access and every other record of theirs that belonged to it. Records a person has across stores lose only that store, and their sign-in is not touched: a buyer's library, the lists a person joined and an affiliate's page of the stores they promote stop showing the store at once, because it no longer exists; its id stays in them, pointing at nothing, until the quarter it was written in has run out, three years and a quarter at the most, and is then deleted by itself. Links and marks that store already sent out, and what one of its sales left under the sale's own reference rather than the store's (a gift's or a group purchase's record, a pre-order's payment, a shipment's or a call's marks), cannot be found once the store is gone and are deleted by themselves within the days each is kept for: 430 at the most. We keep no copy of the store's sales: every sale, refund and payout is on the creator's own Stripe account. What we keep, as our own record under our legal obligations (GDPR article 6(1)(c)), is our invoices for the store's plan and any fee we charged, in our billing records and on our own Stripe account, and a note of the dates the store ended and closed, kept for about a year. The store's address is held back from anybody else for 30 days.
A creator's list is kept for as long as their store exists, or until the creator deletes a person from it, or the person deletes themselves (section 8). A request for a free copy whose link is never used is deleted after 7 days. An address that unsubscribed from a creator stays on that list, marked as unsubscribed, so it is never written to again; to have it deleted entirely instead, delete it yourself at marktmorgen.com/privacy/delete.
A creator's automatic emails and workflows keep a record of each person's way through each of them: your address, which steps were attempted, done, skipped or could not be confirmed, and when. It is kept for up to 400 days after it starts, and deleted earlier when you ask to be deleted, when the creator erases you from their workflows, removes the workflow, or deletes the store. Deleting it also deletes any of its emails or steps still waiting to reach you. A workflow may start when a creator's team moves a deal that names your address into a stage they chose; it starts only while you are on their list and agreed to hear from them, and nothing new is kept about you for it beyond the deal and the workflow's record. An automatic email sequence may start when you sign a creator's proposal or agreement, or pay a payment request they sent you, for the address it was sent to. It starts only while you are on their list and agreed to hear from them. Signing or paying never adds you to the list. The only new things kept for it are the sequence's own record, described above, and its emails waiting to be sent.
A community's posts, comments, pictures and member records are kept while the community exists, until the author or the creator deletes them. An affiliate program's records, license keys and the list of who holds them are kept with the store's records. Certificates are kept while the store that issued them is open, so their pages keep proving what they say. Webhook deliveries are kept for up to seven days, and the mark that an event was sent for 30 days. A calendar reading is kept for up to six hours, and the calendar address until the creator removes it.
A store's team, invitations and activity log are kept until the store is deleted, and invitations run out after seven days. Passkeys are kept until removed, and the record of the browsers an account signed in from until 400 days after its last sign-in. Email drafts are kept until sent or deleted. An email platform's key is kept until the creator disconnects it, each record of a person sent there for up to a week, and the mark that they were sent for 30 days. A device's notification address is kept until it is removed or turned off. Reviews are kept until their buyer deletes them or the creator deletes the product. A video room's address is kept for 60 days after its call.
A live event and its list of who is coming are kept until the creator deletes the event once it is over or canceled, or until it makes room after 500 are kept; the record of each event email, for 30 days. What an import from another platform sends us is deleted 14 days after it began, except the contacts it added to a list, kept as the list is, what past buyers were given and the members invited to move, kept for as long as the store exists. A Google Calendar or Zoom connection is kept until the creator disconnects it or removes our app, each meeting's record until 60 days after the meeting, and a connection's problem log for 30 days.
Creator research answers are kept for up to 24 months from the date you sent them, or until you ask us to delete them, whichever comes first. They are stored with our database provider (Upstash) on infrastructure used by our hosting provider (Vercel).
Research outreach records (who we contacted, when, and any reply) are kept for up to 24 months from the last contact. If you ask us to stop, we keep only your name and contact detail on a do-not-contact list, so that we can respect your request.
A creator's Outreach records are kept while their store exists, up to 400 at a time, the oldest unanswered ones making room for new ones. When a business asks a store, or every store, to stop, we keep its domain on that list for good, so that the request holds.
7. International transfers
Marktmorgen serves customers internationally. Your information may be processed in the countries where we and our service providers operate, which include the United States and may include the European Union. Where required, we use appropriate safeguards for cross-border transfers. Our database provider, Upstash, stores the records this policy describes under its Data Processing Addendum, which includes the EU Standard Contractual Clauses, the UK Addendum and the EU-U.S. Data Privacy Framework.
8. Your rights, including under the GDPR
Depending on your location, you may have the right to access the personal data we hold about you; correct inaccurate data; delete your data; restrict or object to certain processing; receive a copy of your data in a portable format; and withdraw consent where processing is based on consent.
Deleting what a store keeps about you. You do not have to ask anybody. At marktmorgen.com/privacy/delete, or from the link at the foot of any store's page, type your address. If a store knows it, we email it a link that works for an hour; the page it opens says what will be deleted and what is kept, and pressing its button deletes it, from that store or from every store you bought from (since October 11, 2026) or signed up with yourself (since October 17, 2026). The page says the same whether or not a store knows the address, and a few requests an hour are taken from one address. A creator, or an admin of their store, can do the same from the studio, and the store's owner is told when you do it, with your address, so they can delete you from their own tools too.
What is deleted: your place on the store's list and every link in its emails to you; what its team noted about you (its fields, notes, deals and tasks); your form answers with their quiz results and scores, inbox conversations, reviews and their photos, and waitlist places; your way through its sequences and workflows, and any email still waiting to reach you; your progress, quiz results, handed-in work and its files, lesson comments, private lesson notes and certificates in its courses, and your private podcast feeds; your community profile, points, notifications, private conversations and what you said in its room; your Discord account's link to the store, whose roles are taken back; the record of sending you to the creator's email platform; what an import from another platform gave you there with no payment here, which you then lose; and the marks that you were sent a reminder or an offer. When the creator deletes you rather than you, two of these stay: your reviews, without your address, because a store may not take a review down by deleting its writer, and what an import gave you, which is how you keep what you bought elsewhere. You can still delete both yourself.
What is kept, and why: a one-way fingerprint of your address, under that store, so it never emails you again and no import brings you back, which only you can lift by joining its list again yourself; any stop you pressed on one kind of its emails, also a one-way hash; your payments, which are on the creator's own Stripe account as their sales and tax records and are not stored by us; and the few order records a purchase still needs for a refund or for delivery, each with only what it needs and for the time section 1 gives it: PayPal orders, license keys you bought and the codes of the devices they run on, gifts and group places, pre-orders, packages of calls, your place on a booked group call's guest list until 60 days after it, and when a physical order shipped. The links emailed to you before stop working. A few records are not kept by your address and run out by themselves: a link that opens a page for a day or less; the list of addresses an email already going out is sent down, which passes a deleted address over (until it finishes, at most 60 days); a reminder waiting for its hour, which is then not sent (at most a week); an event for the creator's webhooks still waiting to be sent, which is then not sent (at most a week); an import's file (14 days after it began); the events a store's webhooks already sent to the creator (7 days); and one-way marks that limit how often something is sent or asked (at most 32 days).
Not deleted by this yet: posts and comments you wrote in a store's community, and your likes and poll votes there, stay, shown without your name. Delete them in the community first if you want them gone, or ask the creator. What a creator copied elsewhere (their email platform, their own files) is theirs to delete there. If a creator removed a course before we began keeping a record of removed courses, the records you left in that course (lessons done, quiz answers, work you handed in, a certificate) are not reached when you ask us to delete your data from that store.
If you are in the European Economic Area or the United Kingdom, where the General Data Protection Regulation (GDPR) or the UK GDPR applies, or in another jurisdiction with similar laws, you may exercise your other rights by emailing support@marktmorgen.com. We will respond within the time required by applicable law, typically one month under the GDPR. You also have the right to lodge a complaint with your local data protection authority.
You may cancel your account and subscription at any time. Cancellation and refunds are described in our Refund Policy.
9. Children’s privacy
The Services are not directed to children under 18. We do not knowingly collect personal information from children. If you believe a child has provided us with personal data, contact us and we will delete it.
10. Security
We use reasonable technical and organizational measures to protect personal information. No method of transmission or storage is completely secure. You are responsible for keeping your email inbox and any passkeys you add secure, since they are how you sign in.
11. Changes
We may update this Privacy Policy from time to time. The “Last updated” date at the top of this page will change when we do. We encourage you to review this page periodically.
12. Contact
Marktmorgen
Email: support@marktmorgen.com
Website: marktmorgen.com