privacy

Privacy policy

The short version: we collect what the product needs to research, draft and publish your content. Nothing gets sold or published without you, and our ad pixel runs only if you accept it.

last updated · November 1, 2026

What we collect

Account details. Your email address, display name and a password (stored only as a secure hash). We use your email to sign you in and to send messages about your account — never marketing you didn't ask for.

Your sites and content. The site URLs you register, the publicly available pages the agent reads from them to build a brand profile, and everything the agent produces for you — research notes, drafts, images and social posts. This content exists so you can review and publish it; it stays yours.

Billing. Payments are processed by Stripe. Your card number never touches our servers — we keep only your subscription status, plan and invoice references.

Support requests. When you contact support from the app, we store your message with your account and email it to our support inbox through our email delivery provider, Resend, so we can reply.

Usage and errors. We use cookieless page analytics (below) and error monitoring (Sentry) to keep the service working. Error reports leave out your account details and cookies. We use one advertising tool, the Meta Pixel, and only if you accept it (see cookies). We don't sell or rent any of your data to anyone.

Visits to magicshare.io

We count visits with Vercel Web Analytics, which sets no cookies. It records the page you viewed, the site that referred you, your country, and your browser and device type. Before anything is sent, we strip the page address of everything but its utm_ campaign tags, and replace anything in the page's path or those tags that looks like an email address, an ID or a token with a placeholder (other than the post IDs our own published links carry), so links with tokens in them (like a confirmation link) never leave our site. Pages inside the app are not counted.

On top of page views we count a few events, none of which names you: that a blog post was read (you stayed a minute or scrolled most of the way), a click on a sign-up, log-in, pricing or get-started link and where on the page it sat, the domain a link took you to when you left our site, and, when an account is created, the channel it came from and the page the visit started on.

Where new accounts come from

To learn which posts and campaigns bring people to Magic Share, we note how your visit began: the page you arrived on, the website that referred you (its name only, never the full address), the utm_ campaign tags on the link you followed, and whether that link carried an ad-click marker from Google, Microsoft, Meta, TikTok, X or LinkedIn (only that it was there, never its value). This is kept in your browser tab's session storage, not a cookie. No other site can read it, and it disappears when you close the tab.

It reaches us only in the link to our sign-up page, and it is saved only if you create an account (if you accepted the Meta Pixel, Meta also receives that link as a page address): then it is stored with your account, together with the page and button you signed up from. Page addresses are saved without their query strings, and anything in a page address or a campaign tag that looks like an email address, an ID or a token is replaced with a placeholder first (other than the post IDs our own published links carry). Only our team sees what we store, and it is kept and deleted with your account.

Publishing connections you choose to add

Connecting X (Twitter), GitHub, or a Facebook Page and Instagram account is optional. If you connect them, we store the access tokens encrypted at rest and use them for what you set up: publishing the content you approved — a tweet thread, a pull request with one markdown file per post, a Facebook or Instagram post — and, for Meta ads, creating ads that stay paused until you activate them. Disconnect at any time from your site's settings and we delete the tokens.

When we publish a link to your site on X or Facebook, we add utm_ campaign tags to it: the network, the word “social”, the blog post's web address name (or “daily”) and our internal id for the post. Meta ads carry similar tags naming the campaign, the ad and where it was shown. They tell your own analytics which post or ad a click came from; they describe the post, not the people who click it. Links you wrote into the post text yourself, and links you already tagged, are left as they are.

Search data for your site

If you connect a Google Search Console property, we read its search performance — which of your pages appeared for which search terms, with clicks, impressions and average position per day — and the index status of your published posts. Google reports these as totals; they don't identify the people searching. We keep about 14 months of daily figures. Access is read-only and works by adding our service account to your property, so we never hold your Google password or tokens.

To judge which topics your site can rank for, topic research may look up search terms with DataForSEO, a keyword-data provider. We send it only the search terms and website domains being compared (yours and the sites ranking for those terms) — no names, emails or other personal data. Results are cached for 30 days so the same lookup isn't repeated.

The blog digest

You don't need an account to get new blog posts by email. If you subscribe at the end of a post, we store your email address and, once you click the confirmation link, the date you confirmed. Until you confirm, the only email we send you is the request to confirm.

To stop the form being used to flood someone else's inbox, we count how often it is used in each hour from each network, under a one-way, keyed hash of the network address (never the address itself) and kept apart from your email address. Each hour's count is deleted after that hour, the next time anyone uses the form. An unconfirmed sign-up is deleted once its seven-day confirmation link has expired, also the next time anyone uses the form.

The confirmation email and the digests go out through our email delivery provider, Resend. Digests are sent by hand when there are new posts. Every digest carries an unsubscribe link; unsubscribing deletes your address from the list, and so does Resend rejecting it as an invalid address. We never use the list for anything else or share it with anyone.

AI processing

Drafting a post means sending prompts built from your site's public content and your settings to AI model providers (via OpenRouter). We send what the run needs to write your content — never your password, billing details or tokens.

Cookies and browser storage

We set the cookies needed to keep you signed in, and one that remembers your cookie-banner choice. Those are essential. Your browser tab's session storage holds how your visit began until you close the tab (see where new accounts come from).

Ad measurement, only with your consent. If you click Accept in the cookie banner, the Meta (Facebook) Pixel records the public pages you view (the full page address, including any campaign tags in it), the referring page, your IP address and browser details, a click toward signing up, and that a signup finished. It sets Meta's advertising cookies, such as _fbp and, if you arrived from a Meta ad, _fbc. Meta may link this to your Facebook or Instagram account, so we can measure and improve our ads. The pixel never loads unless you accept, and it never runs inside the app or on links that carry a token. These are the only non-essential cookies, and declining changes nothing about the service.

You can withdraw or change your choice at any time. The pixel stops, _fbp and _fbc are removed from your browser, and the banner reappears:

Retention and deletion

We keep your data while your account is active. Ask us to delete your account and we remove your personal data, registered sites and generated content, keeping only what payment and tax law requires us to retain about past invoices.

Your rights

You can ask for a copy of your data, ask us to correct it, or ask us to delete it — email sales@magicshare.io and we'll handle it. If we ever change this policy in a way that matters, we'll note the change here with a new date.