What Marsell stores
- Your account: your name and email address. Sign-in is handled by Clerk, whose screen you see when you sign in.
- Your projects: what Marsell read on your site and public profiles, your answers, the facts you confirmed and your brand.
- Your files: the logos, pictures, fonts, documents and series material you upload.
- Your own voice, if you clone it: Marsell sends your recordings to ElevenLabs to make the voice, keeps a note that you confirmed it’s your voice or that you have the speaker’s permission, and never lets another business use it. Removing the voice removes it from ElevenLabs too.
- Who applies for your grants and programs, if you tell MarPly: who applies, the registered name, when the business started, money raised, the team, the country and what money won would be spent on. These are kept apart from your business’s facts: no post, page or chat answer reads them, a program’s card says only whether they are on file, and only the brief for your own AI writes them out, which needs a role that can approve. See Apply for grants, credits and programs.
- The work: plans, drafts, pictures, films and pages, with your approvals and edits.
- Connected accounts: the access Marsell needs to post, send or read results on the accounts you connect.
- Linked chats: for a Telegram or Slack chat you link in Settings › Notifications, the chat or Slack user it is, its name, and the project it talks about. A Slack bot’s key is encrypted. See Telegram and Slack.
- People Marsell finds for outreach: with your yes to finding and emailing people who could buy, the person’s name, their work address, their business and where it is based, and where the name and address came from. See Finding work addresses.
- Usage: what ran and how many tokens it used.
Where it’s kept and how it’s protected
- Marsell hosts the service, its database and your files in the European Union (Frankfurt, Germany). Cloudflare serves the domain and delivers the site. Its providers process information in the United States and other countries.
- Everything between your browser and Marsell travels over HTTPS.
- Every request to your account is checked against your sign-in and, in an organisation, against your current membership and role. Each press asks for the permission it needs: one that spends tokens needs a role that may make things, one that puts something out, such as posting from the canvas or putting a page live, needs a role that may publish, and one that can take a scheduled post back, such as deleting it, needs a role that may stop work. See Team.
- Files you upload are private: they open only for people signed in to your account.
- Pictures and films Marsell makes are shown and published through long, random links that work without signing in, so the platforms you publish to can fetch them. Anyone who has one of these links can open that file.
- The tokens and keys for your connected accounts are encrypted (AES-256-GCM) and tied to your account, so they can’t be read under another one.
- If you join the partner programme, how you’re paid (the email of your PayPal or Wise account, or your bank details) is encrypted the same way. Only Marsell’s team can open it in full, in its own private tools and never in the app, to pay you; your own screen shows only the end of it. Each time it changes, Marsell emails the address you sign in with to say so, without the details. A partner sees the customers they brought by number only, never a name, an email or an account.
- A key for your own AI shows once and is stored only as a fingerprint (SHA-256), so a copy of the database never holds a working key. When you connect Claude or ChatGPT by signing in instead, its sign-in tokens are stored the same way; each works for an hour and is renewed while the app stays connected.
Who at Marsell can see it
Marsell’s team runs the service and has an operations view of every account: the business name, the Marsell plan, tokens used, when it was last active and how far the work has got, such as how many pieces were made or published. The team uses it to keep Marsell running and to fix problems. People Marsell authorises to handle customer data are bound by confidentiality.AI providers
To do the work, Marsell sends the content each task needs to AI model providers: text models for research, planning and writing, and image, video, voice and music models for media. They process it and send back the result. Marsell doesn’t use your content to train AI models. Section 6.1 of the Privacy Policy lists the providers.Delete your data
To delete a project, open Settings in that project, go to Connections, press Delete this project at the bottom, type the project’s name to confirm, and press the button that names it, such as Delete Softwear. Everything made for it goes for good: its files, setup, plans, posts, pages, films, rivals and communities. Your Marsell plan and your tokens stay with your account. If the project has social accounts, the dialog lists them. They’re disconnected and their slots on your plan free up, or, if you have another project, you can move them there instead. Posts that already went out stay on the platforms. Keys and apps connected for your own AI stay connected. To close your account and have your data deleted, email privacy@getmarsell.com from the address on your account. After an account is closed, Marsell deletes or de-identifies your personal information, normally within 90 days, and copies in backups expire, normally within 30 days. Billing and tax records are kept for as long as the law requires.Export your data
You can download your work where it’s shown: open a picture or film in Made for you in Create, or download a file under Your files on Brand. For a copy of everything, email privacy@getmarsell.com.Revoke a connected account
- To stop Marsell posting to a social account, press Stop posting here on its card under Where you post, on Market’s Posts tab, then Stop posting to confirm. Drafts stay and nothing is deleted. Resume posting turns it back on. See Connect your accounts.
- To remove an account from Marsell, press Disconnect on its card and confirm. Marsell stops posting to it and stops reading its comments and numbers, posts planned for it go back to waiting for an account, and its slot on your plan frees up (or, if it was past the accounts your plan includes, it stops costing tokens). Connected to the wrong project? The same dialog can move it to another project instead.
- The platform may still list Marsell’s permission after that. To withdraw it completely, remove it in the platform’s own settings. For a Google account, that’s Google’s third-party access page.
- Posts already published stay up, and their records stay in Marsell. Delete them on the platform if you need to.
Your own AI
When you connect your own AI, it sees what you see in Marsell. With Can act on, it can also do what Marsell’s chat can, such as making pictures and spending tokens. It answers what waits for you only when you ask it to. Homework for your AI gives it one list of the jobs that need your own logins, files or inbox, each saying where it is done (your missions profile, your mailbox, your files or your own accounts), so nothing for Reddit, X or LinkedIn is done from a browser that also holds your email; a homework card is answered only by you, in Marsell, never by the AI the job is for. Auto mode lets your AI do planned homework without a card first: use it only with a newer, careful model, because you are responsible for what your AI does in your accounts. Turning homework or auto mode on needs a role that can approve. See Agents. Missions are the messages your AI sends on Reddit, X and LinkedIn from your missions profile, on the accounts you picked. Give that AI a missions key (Make a missions key, under Your own AI): it can only take a mission, report how it went and set its own wake-up timer, so a page your AI reads in that browser can’t reach the rest of your business. It is stored as a fingerprint like any other key and can be revoked the same way. Marsell never gets your passwords or your browser’s sign-ins: your AI sends from the browser, and reports back the link of what it sent. Marsell sets the pace on its own side, so your AI can’t send in a burst, and Pause missions stops them at once. Give it to an AI that works in a separate browser profile, signed in only to Reddit, X and LinkedIn, never to your email or bank.Telegram and Slack
Linking a chat in Settings › Notifications lets Marsell send it your morning report and alerts, and lets you talk to Marsell there.- Connect Telegram uses a link that works once, for 15 minutes. Add to Slack goes through Slack’s own page, and finishes in Marsell with your own sign-in.
- Messages from a linked chat run Marsell’s chat as you. Before anything is sent to a chat or done for it, Marsell checks again that you are still on the team and what your role allows now. Someone who leaves the team is unlinked.
- What spends tokens still waits for a press in Marsell. Files sent to the bot are saved privately with the project and read the same way as files sent in the app’s chat.
- Telegram and Slack carry what Marsell sends there, such as the report’s lines and the pictures you asked for, under their own terms.
- Unlink stops a chat at once. Whoever runs the account can unlink anyone’s.
Finding work addresses
With your yes to finding and emailing people who could buy, Marsell looks for the person who runs each business that fits, then their work address.- It goes only on what was shared: a business on a list, or a business the person named or linked as their own in a public post. It never matches a username to a real name. With no business site, there is no lookup.
- It reads the business’s own pages for who runs it. If they don’t say, a data service (Explee) is asked for the role, such as the founder or owner.
- Explee is sent the person’s name and the business’s web address and returns a work address it has checked. Only a checked address on the business’s own domain is used, never a free email address. Each address found costs 1.5 to 5 cents in tokens, and a role lookup 1 cent for each person it returns; nothing is charged when nothing is found. What was found for a business is kept for 30 days, so it is never bought twice.
- Businesses in Germany, and sole traders in the UK and the EU, are skipped because the law there asks for permission first, and the morning report says who was left out. So are businesses whose country can’t be read, anyone on your do-not-contact list, and anyone written to in the last 30 days.
- An email to a found address never quotes the person’s post.
Your code on GitHub
If your site’s code is on GitHub, Marsell can open fixes as pull requests you merge. You connect it under Your site’s code on the Connections tab of Settings, and How Marsell handles your code on that card has the full detail. Marsell asks GitHub for:- Read and change files in the repo you pick, only to open pull requests
- Open pull requests
- See the repo’s name and basic details, which GitHub requires of every app
package.json lists), package.json, your page template index.html, the files that set your site’s headers (render.yaml, _headers, netlify.toml, vercel.json), and the four files it publishes: robots.txt, sitemap.xml, llms.txt and llms-full.txt. Nothing else: not your app’s source, not the repo as a download, not a clone.
What it changes: only on a branch it makes itself, named marsell/…, and only those four files, your page template’s head, and the Content-Security-Policy value in a header file. Then it opens a pull request against the branch you chose, for you to merge or close.
Marsell never:
- touches a repo other than the one you pick;
- writes to your main branch, or any branch it didn’t make;
- merges anything: you do, or your rules on GitHub do;
- reads your app’s source, or downloads the repo;
- changes workflows, settings, secrets, env files or lockfiles;
- force-pushes, deletes a branch or a file, or touches hooks, collaborators, releases or tags;
- keeps a GitHub token. Each job gets a token that works for one hour, for your one repo, with only the permissions that job needs.
What Analytics reads
- Your own channel and code. A YouTube channel’s subscribers, uploads and each video’s views, and a public GitHub repository’s stars, forks, open issues and release downloads, are read once a day the way anyone can see them, with no sign-in and no key. Analytics never uses the GitHub access above, so a private repository isn’t counted.
- Visits to your site. Marsell’s visit counter counts every visit without cookies. It goes in your site’s head, where Marsell can add it as a pull request, or you can use Copy for your developer.
- Payments from Stripe. The connection only reads: your payments, and where the access allows, your subscriptions, customers, checkouts, products and invoices. So that your own team is never counted as a new customer, Marsell takes the verified email addresses of everyone on your account (in an organisation, each member’s) from Clerk and asks your Stripe, where it can read Customers, for the customers with each of those addresses. It stores only the ids of the customers that match, never the addresses. See Before tax, and your own team.
- Where people press. With heatmaps on, a press line on your site reports which button or link a visitor pressed and where on it, and how wide their window was. Nothing is kept on the visitor’s device, and nothing names who they are. Marsell keeps them only from your site’s own address, added up by day.
- Who signs up on your site. With Catch who signs up on, Marsell’s line on your site sends the email address, name and the few details people give your sign-up, newsletter, enquiry and booking forms, who is signed in through your sign-in service, and where their visit came from. It never sends passwords, card numbers, hidden fields, a message’s words or any sign-in token. Marsell receives this on your behalf, only to show you your own people: it keeps the address sealed, never sells it or uses it for anyone else, and deletes it when you delete the person, the project or your account. Add the sentence the card gives you to your own privacy page.
Visits from Marsell’s own ads
When you arrive on getmarsell.com from one of Marsell’s own ads, or from a link with campaign tags, Marsell’s server logs the visit: which ad or link it was, the page, the time, your country and whether you’re on a phone, a tablet or a computer. It doesn’t log your IP address, your name or your email address. If you then open an account, subscribe or book a call, Marsell counts it toward that ad. A link from one of Marsell’s partners carries that partner’s code: Marsell logs such a visit the same way and keeps the code with it, and when an account is opened from that visit it records that the partner brought it. The code names the partner, never you, and a partner sees counts and amounts only, never who signed up. Booking a call on the Services page opens Calendly’s booking window on the page, and Calendly’s script loads only when you reach for the booking button (point at it, touch it or move to it with the keyboard). Once you’ve booked, the page sends Marsell Calendly’s booking reference. Marsell checks with Calendly that the booking is active and belongs to the Services calendar before counting it once. Calendly’s response includes your name and email address; Marsell discards those fields and keeps the booking reference and time for its count. If the booking cannot be confirmed, it is not counted, but your appointment in Calendly remains. A confirmed booking counts whether you said yes or no to cookies; only with your yes is it sent to Google for a Google ad click, as below. Your name and email address are never sent to Google for this.- With your yes to cookies, Marsell also keeps the click id the ad network added to the link, and its server sets a cookie of its own for 90 days. It then sends the network the click came from (Google, through Zernio) that click id, when it happened and, for a payment, the amount, so the network can measure the ad. No email address or phone number is sent.
- Without it, or when your browser sends a Global Privacy Control signal, Marsell keeps no click id, sets no cookie and sends nothing to the network. Only a reference to the visit stays in the tab until you close it, so an account opened there can still be counted toward the ad inside Marsell.
- Saying no later deletes the click id Marsell kept and the cookie. Click ids are deleted after 90 days anyway.
Labels on AI-made content
Marsell uses a platform’s own AI label in some cases, not all: films with AI-made pictures or clips go to YouTube with YouTube’s altered or synthetic content label switched on. A film never carries a “Made with AI” badge on the picture itself. Other posts aren’t labelled automatically. Under the Terms, you’re responsible for any AI disclosure that the law or a platform’s rules require, whether or not Marsell adds a label.Report a security issue
Email security@getmarsell.com and don’t post the problem publicly. Say what you found, how to reproduce it, and how you’d like to be credited. Marsell acknowledges a report within 3 business days and tells you what it found within 10 business days. There’s no paid bug bounty yet. The Security Policy covers scope, testing rules and safe harbour, and security.txt gives the same contact. If you think someone else got into your Marsell account, email security@getmarsell.com straight away.Related
Connect your accounts
What connecting an account lets Marsell do.
Team
Organisations, roles and seats.