Privacy policy

MagpieFeed reads your website, and any product or content feed you add, and turns what it finds into finished social posts that wait in a queue for you. This page describes the data that involves, in the same detail the software actually works in. If something here is vague, assume the narrow reading and ask us.

1Who we are

MagpieFeed (magpiefeed.com) is run by a private individual based in Croatia, who is the data controller where this policy says "we". Operator details are available on request through the contact form. For anything in this policy — access, deletion, questions, complaints — use the form or the privacy address in section 8. A person reads both.

For the data you put into MagpieFeed, we are the data processor and you are the controller: it is your website, your feed and your customers' shop. For your own account data (your email, your login), we are the controller. We are also the controller for a website address someone pastes on our start page before they have an account, and for what we read from that site to show them a plan (see "Your website" below).

2What we collect

Your account

  • Your email address, and a hashed password if you signed up with one.
  • Your plan, your timezone, when your account was created, when your trial window ends, and when you finished onboarding.
  • If you used the Google button: Google's permanent account identifier for you (the sub claim), your verified email address, and the date you linked it. We ask Google for three scopes only — openid, email, profile. We do not store Google's access token, and we never ask for a refresh token (the request uses access_type=online), so MagpieFeed cannot act on your Google account — the sign-in proves who you are and nothing else.

Your brand settings

  • Brand name, website, tone of voice, language, notes, keywords and topics (your Voice Profile), colour palette, font choice, default hashtags, your affiliate-disclosure text, whether posts are labelled as AI-assisted, any webhook address you set, and any logo you upload.

Your website: Site Analysis and Plan Preview

  • The website address you paste on our start page. You can do that before you have an account.
  • To analyse it, our server fetches a sample of that site's public pages - at most 15 per analysis, found through its RSS/Atom feed, its sitemap or the links on its home page. It identifies itself as MagpieFeed, obeys the site's robots.txt, does not log in, and does not submit forms.
  • What we keep from that read, stored against the site's domain name: the address that was pasted, and for each sampled page its URL, its title and a text excerpt of up to 1,200 characters; the detected language; the proposed keywords, tone, notes and topics; the mix of Post Types the site can support; and the example posts written for the Plan Preview. The same analysis is reused for about 24 hours if the same site is pasted again.
  • An analysis is not tied to you, your IP address or any account until you sign up. When you do, it is copied into your brand and becomes your Content Plan: each Plan Topic keeps the excerpt of your page it was drawn from, so captions can be checked against it.
  • While you edit the proposal on the start page, your changes are kept in your own browser's sessionStorage (cleared when you close the tab) and are sent to us only when you create your account.

Public pages can contain personal data. A team page, a testimonial or a blog byline may name people, and an excerpt of that page is stored as it was read. Paste the address of a website you run or are allowed to use this way.

Feeds, if you add one, and what is in them

Feeds are optional. If you add one — a product feed, or a content feed such as RSS or Atom — we keep:

  • The feed URL, how often it should be polled, your field mapping, and any authentication header you give us so the poller can read a private feed.
  • A record of each poll: HTTP status, bytes read, how long it took, how many items were seen, created, updated or removed, and the error text when a poll fails.
  • For every item in the feed: its id, title, description, price and sale price, currency, image URL, product URL, availability, brand, category, GTIN (a content feed simply has no price) — and the raw source record as we received it, stored as JSON. If your feed carries a field we do not map, it is still in that raw copy.
  • The changes we derive: new item, price up, price down, back in stock, out of stock, removed, with the old and new price.

Do not put personal data in your product feed. MagpieFeed stores the whole raw record of every item. It is built for products — titles, prices, images, links — and a feed that carries customer names, addresses, order details or anything similar will be stored verbatim and is not something this service is designed to handle.

The posts we generate

  • The caption, the rendered image or clip, the link, the schedule, the status, and which template and automation produced it — and, for a post from your Content Plan, its Post Type and Plan Topic.
  • For a Short made from an image post: the video file and the voiceover of the caption. The voiceover is made on our own server by an open-source speech engine (Piper); the caption is not sent to any speech service.
  • A delivery log for every publishing attempt: the endpoint called, the HTTP status, how long it took, the error code and message, and the request and response bodies. Those bodies are scrubbed before they are written — any field whose name looks like a credential is replaced with [redacted], so access tokens do not land in the log.

Channels you connect

  • The platform, the page/account id and name, the avatar URL, the granted scopes, the OAuth access token and refresh token, and when the token expires.
  • For Facebook Pages, Instagram and Threads, connected through MagpieFeed's own Meta and Threads apps: the access token the network issues, and the app-scoped id of the person who connected it, so that a deletion request from Meta finds the right connections.
  • If you connect a channel through a developer app of your own, the client id and client secret of your app.
  • For YouTube, the id, title and picture of the channel you connect (see YouTube below).
  • For Telegram, the bot token you paste and the chat id; for Discord, the webhook address you paste; for Bluesky, your handle and the App password you create for MagpieFeed. These are stored in the same encrypted token field.
  • Tokens, App passwords and own-app secrets are encrypted at rest (Fernet/AES) with a key held in the server's configuration, not in the database. A database dump on its own does not yield a working token.

API keys

  • We never store an API key. We keep a SHA-256 digest of it plus a short non-secret prefix for lookup and display, so a key cannot be recovered from our database — if you lose one, you rotate it. We also record when a key was last used, from which IP address, and how many requests it has made.

Technical data

  • A session cookie when you are signed in, and a CSRF cookie. Both are strictly necessary to run a website with forms and logins: the session cookie is HttpOnly, SameSite=Lax, and lasts 14 days; the CSRF cookie is set on pages that carry a form, including the home page, and lasts one year. Both are sent only over HTTPS.
  • Two things kept in your own browser rather than in a cookie: the start-page draft described above (sessionStorage), and, on the pricing page, whether you last looked at monthly or yearly prices (localStorage). Neither is sent to us on its own.
  • Server logs — the web server's access and error logs and the application's own log — which include IP addresses, requested URLs, the browser's user-agent string and error traces.
  • To stop the start page being abused, the number of analyses and previews requested from one IP address is counted in our in-memory cache for up to an hour. That counter is not written to the database.

Visit measurement, only if you agree. On our public marketing pages (home, pricing, features, tutorials, help, developer docs, the "for" pages and these legal pages) a banner asks whether we may measure visits. Only if you choose "Accept" do we load Google Analytics 4 (Google Ireland Limited) and Microsoft Clarity (Microsoft Ireland Operations Limited). They record which pages you view, clicks and scrolling (Clarity also records a session replay with form text masked), device and browser type, approximate location, and a pseudonymous id kept in cookies (_ga, _ga_<id> up to 2 years; _clck 1 year, _clsk 1 day; Microsoft may also set MUID, 1 year, on its own clarity.ms domain). Advertising features are switched off, and so are the optional Google Analytics data-sharing settings; Google processes this data as our processor under the Google Ads Data Processing Terms. Microsoft acts as our processor for Clarity, and as an independent controller for some of its own purposes, as described in the Microsoft Privacy Statement. If you choose "Reject" or do nothing, neither is loaded. Your choice is kept in your browser's localStorage (mf_consent), and "Cookie settings" in the footer lets you change it at any time; rejecting deletes those cookies. They are never loaded inside the app, on sign-in, sign-up or password pages, on links that carry a token, or for signed-in users. We run no advertising trackers, and our fonts are served from our own server.

To see whether the sign-up path works, our own server keeps aggregate daily counts of a few steps ("home page viewed", "website submitted", "analysis started", "analysis finished", "plan preview shown", "account created", "plan claimed"): one number per step per day, set without cookies or scripts, and stored with no IP address, user id, browser details or any other identifier. So that one analysis is not counted twice, a one-way hash of its analysis token sits in our cache for a day; it never reaches the database.

The demo websites at demo-roastery, demo-kitchen and demo-bikes.magpiefeed.com are fictional shops we host to show our own output. They set no cookies and run no scripts beyond page metadata; visits to them appear only in the server's access log.

3Why, and the lawful basis

WhatWhyLawful basis (GDPR Art. 6)
Account, brand, Content Plan, feeds, items, posts, channelsTo provide the service you signed up forPerformance of a contract, 6(1)(b)
Site Analysis and Plan Preview for an address pasted before sign-upTo show you the plan you asked to see before you decide to sign upSteps taken at your request before a contract, 6(1)(b)
Sending page excerpts, item fields and brand voice to our language-model providerTo write captions and propose your keywords, tone and topicsContract, 6(1)(b)
Uploading your approved Shorts to a YouTube channel you connectTo publish where you asked us toContract, 6(1)(b) — you choose whether to connect it
Delivery logs, poll history, channel healthSo you can see why a post failed, and so we can keep it workingContract, 6(1)(b); legitimate interests, 6(1)(f)
Visit measurement (Google Analytics 4, Microsoft Clarity) on public pagesTo learn which pages help and where the site gets in the wayConsent, 6(1)(a) — only after "Accept", withdraw any time via "Cookie settings"
Server logs, IP addresses, rate limitsSecurity, abuse prevention, debuggingLegitimate interests, 6(1)(f)
Google sign-inTo let you sign in without another passwordContract, 6(1)(b) — you choose whether to use it
Email about your account (a broken feed, a dead token)To tell you the service stopped doing its jobContract, 6(1)(b)

We do not profile you, we do not make automated decisions about you, and we do not sell or rent data to anyone.

4Who we share it with

Only the following, and only for the reasons given.

WhoWhat they getWhy
Hetzner Online GmbHEverything — they host the server the whole application runs on, in FinlandHosting
CloudflareTraffic to magpiefeed.com passes through their network; they also route mail sent to our addressesDNS, proxy, inbound email routing
GoogleOnly if you use the Google button: the sign-in exchange itselfSign-in
Google (Google Analytics 4)Only if you click "Accept" on a public page: the visit data described under Visit measurement; may be transferred to the USA under the EU-U.S. Data Privacy FrameworkVisit measurement
Microsoft (Clarity)Only if you click "Accept" on a public page: the visit data and masked session replay described under Visit measurement; may be transferred to the USA under the EU-U.S. Data Privacy FrameworkVisit measurement
Anomaly Innovations, Inc. (trading as OpenCode, opencode.ai), USA, through its Zen gateway, which runs DeepSeek modelsThe text described under "Caption generation" below: page excerpts, item fields, Plan Topics, captions and your brand voice settingsLanguage model for captions and Site Analysis

That is the complete list of our sub-processors. Card payments are not switched on, so Stripe receives nothing today; it will be added to this list, and account holders emailed, before it does. Mail we send you (account alerts) leaves from our own server in Finland; we do not use an email-sending vendor, nor a third-party error-tracking, email-marketing, CRM or support vendor; the only analytics vendors are the two consent-gated ones above. Our fonts are served from our own server, and the voiceover of a Short is made there too.

Platforms you connect yourself

When you connect a channel and a post for it is approved (by you, by writing and scheduling it yourself, or in advance by an automation set to "Auto-post" or a channel set to auto-approve) we send that post (the caption, the image, clip or Short, and the link) to the platform you chose, directly and through MagpieFeed's own apps; no other service sits in between. LinkedIn, Bluesky, Mastodon, Telegram and Discord can be connected. Each platform receives only the posts you send to it. What happens to it there is governed by that platform's own terms and privacy policy, not ours. You decide which platforms are involved by deciding which ones to connect.

If you let a plan send to a channel, we send its posts on the schedule you set, as each one comes due, without a further action from you. We keep the plan's schedule (days, times and time zone), which channels it sends to and whether it is paused with your account, so that it can keep running. Pausing the plan, detaching the channel or switching auto-approve off stops further sends.

From Facebook and Instagram we read only what connecting and publishing need: the id and name of the account or Page you connect and its picture, plus the access token Meta issues to MagpieFeed's own Meta app (or to a Meta app of your own, if you connected one before). We do not read your insights, comments or messages. When you connect through MagpieFeed's own Meta app, the details are in the next section.

Facebook, Instagram and Threads

If you use Connect with Facebook or Connect Threads under Channels, you sign in on Meta's own screen and grant MagpieFeed's Meta app access there. Nothing is read from your accounts, and nothing is published to them, before you do.

  • The permissions we ask for. For Facebook and Instagram: pages_show_list, pages_read_engagement, pages_manage_posts, business_management, instagram_basic and instagram_content_publish. For Threads: threads_basic and threads_content_publish. Nothing else.
  • What we read. Right after you sign in: the list of Facebook Pages you manage, including Pages in a Business portfolio (each Page's id and name, and the id and username of the Instagram professional account linked to it), so you can tick the ones to connect; which permissions you granted; and your app-scoped Facebook user id, a number Meta issues for our app only, which we need to act on a deletion request Meta sends us. Later: the id and name of each connected Page or Instagram account, to check the connection still works, and the id and link of each post we publish. For Threads: your profile's id, username, display name and picture, and the id and link of each post we publish. We do not read your personal profile, friends, messages, comments, followers, insights or other people's content, and we do not read posts we did not publish.
  • What we store. For each Page or Instagram account you tick: its id, its name or @username, the id of the Page it belongs to, the Page access token Meta issues for it, and your app-scoped Facebook user id. Pages you do not tick are not stored. Between Meta's sign-in screen and your ticks (at most 30 minutes) the sign-in token is held, encrypted, in your session, and it is dropped once you have chosen. For Threads: the profile's id, @username and picture address, and its access token, which lasts 60 days and which we renew while the channel stays connected. Every token is encrypted at rest. For each post we publish, its id and link and the delivery log described above.
  • What we send. Only posts you wrote or approved (or that an automation you set to Auto-post approved for you): the caption, images or video, and link, to the Page, Instagram account or Threads profile you chose, at the time you chose. We never edit or delete your existing posts.
  • Who else gets it. Nobody. Data from Meta is not shared with any other party, not sent to our language-model provider, not used for advertising, and not used for anything but showing you your connections and publishing to them.
  • How long we keep it. The connection, its token and the ids above: until you disconnect the channel, delete the brand or your account, or Meta tells us you removed MagpieFeed. A Page access token issued this way does not expire on its own; when Meta reports one revoked, we stop using it and mark the channel for reconnecting. Post ids, links and delivery logs stay with the post for as long as your account exists (section 6).
  • How to revoke it and have it deleted. Disconnect the channel under Channels: its token, ids and name are deleted at once. Or remove MagpieFeed in Facebook under Settings, Business integrations, and ask for your data to be deleted: Facebook tells us, and we delete every Facebook and Instagram connection made for you through our app straight away and show you a confirmation code (the steps are on magpiefeed.com/meta/data-deletion/). For Threads, remove MagpieFeed in Threads under Settings, Account, Website permissions: Threads tells us, and we stop publishing and delete that Threads connection straight away. You can also disconnect the channel in MagpieFeed or use the contact form. Backups age out as described in section 6.

YouTube

MagpieFeed uses the YouTube API Services to upload Shorts to a YouTube channel, if you connect one. By connecting it you agree to be bound by the YouTube Terms of Service, and what Google does with your data is described in the Google Privacy Policy.

  • How it connects. Through MagpieFeed's own Google app: you sign in on Google's own consent screen, and no Google Cloud project of your own is needed. We ask for exactly two permissions: to upload videos (youtube.upload), and to view your YouTube account (youtube.readonly), which we use only to read the id, title and picture of the channel you connect. Nothing else.
  • What we read. The id, title and picture of the channel you connect, so you can see which channel it is. We do not read your existing videos, playlists, comments, subscribers, analytics or any other YouTube data.
  • What we store. That channel id, title and picture URL; the access and refresh tokens Google issues (and, for a channel connected with your own Google app before we offered ours, that app's client secret), encrypted at rest; and, for each Short we upload, the video id YouTube returns and the delivery log described above.
  • What we send. Only Shorts you approved (or that an automation you set to Auto-post approved for you): the video file, its title and its description (the caption).
  • Who else gets it. Nobody. YouTube data is not shared with any other party, not sent to our language-model provider, and not used for anything but showing you the connection and publishing to it.
  • Limited Use. MagpieFeed's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. That covers YouTube and the Google sign-in. In particular, we use that information only to provide the features described on this page; we do not sell it, use it for advertising, or use it to build or train artificial intelligence or machine learning models; we do not transfer it to anyone except as needed to provide those features, to comply with the law, or as part of a merger or sale of MagpieFeed with notice to you; and no person at MagpieFeed reads it unless you ask us to (for example in a support request), it is needed for security or to investigate abuse, or the law requires it.
  • How to revoke it. Disconnect the channel in MagpieFeed under Channels, or remove the access at any time in your Google Account's security settings: security.google.com/settings/security/permissions. Either one stops publishing immediately.
  • Deletion. Disconnecting the channel in MagpieFeed deletes its stored tokens, client secret and channel details at once, and we also ask Google to revoke the access. If you revoke access in Google instead, we delete them within 30 days of noticing that the access is gone, or sooner if you ask. Videos already uploaded stay on YouTube until you delete them there.

Your own webhook, exports and RSS

If you configure a webhook, we POST the post's id, brand name, caption, media URL, link, schedule and platform hint to the endpoint you supply, signed with HMAC-SHA256. If you use the ZIP pack, CSV, calendar or RSS exports, that data goes wherever you take the file. Those destinations are your choice and your responsibility.

Caption generation and Site Analysis

Captions, and the keywords, tone and topics proposed for your website, are written by an external language model: OpenCode Zen, a gateway run by Anomaly Innovations, Inc. (Delaware, USA), which routes our requests to DeepSeek models (currently DeepSeek V4.1 Flash). What is sent to it:

  • For a Site Analysis: the website address and, for each sampled page, its URL, title and text excerpt.
  • For a post from a feed: the item's own fields (id, title, trimmed description, prices, currency, availability, brand, category, GTIN, product link), what happened to it (for example a price change), and the name of the automation.
  • For a post from your Content Plan: the Plan Topic, its Post Type, and the excerpt of your page it was drawn from.
  • Always: your brand voice settings — brand name, tone, language, notes and hashtags — and, when a draft caption fails our checks, that draft caption and the reasons, so the model can correct it.

Never your email address, your password, your channel tokens, your API keys, your feed's authentication header or anything from YouTube. Every answer is checked on our server before it is used. When the model is unavailable, or our hourly budget of model calls is spent, the caption or proposal is produced by a deterministic template on our own server instead, and nothing is sent.

Anomaly's own documentation says that the models on Zen are hosted in the United States, that requests to the DeepSeek models are not retained, and that they are not used to train models. It does not name the company that hosts the DeepSeek model for it. We have no separate data-processing agreement with Anomaly, so we rely on those published statements. The lawful basis for sending this text is the contract with you (section 3); the transfer to the US is described in section 5. If any of this changes — a signed agreement, or a move to a provider hosted in the EU — we will update this page and email account holders.

5Where it is stored

The application, the database and the rendered media sit on a server in Finland, rented from Hetzner — inside the EU/EEA. Nothing is copied to another region by us.

Four of the parties above are US-headquartered. Cloudflare handles traffic on a global network, and Google processes the sign-in itself; either may involve processing outside the EEA under the transfer safeguards in their own data-processing terms. Only if you choose "Accept" on a public page, Google (Analytics) and Microsoft (Clarity) may process that visit data in the United States; both are certified under the EU-U.S. Data Privacy Framework. The language-model gateway (Anomaly Innovations, Inc.) is in the United States and says its models are hosted there, so the text described in section 4 is transferred to the US. There is no signed data-processing agreement or standard contractual clauses between us and Anomaly today; the protection for that text is Anomaly's published statement that it is not retained or used for training. If you connect a social platform — Meta, X, Telegram, Discord, Bluesky or YouTube — the post you asked us to publish goes to that platform's own infrastructure, which is generally outside the EEA.

6How long we keep it

  • Rendered images, clips and Shorts: 30 days from when the post was created, once it is finished — published, published manually, or skipped. A nightly job deletes the file and blanks the reference. Posts that are not finished keep their media, so a Manual share post waiting for you to export it is never swept out from under you.
  • Feed items, change events, Content Plans, posts, delivery logs and poll history: for as long as your account exists. There is no automatic purge of these, and we would rather say so than imply one. Deleting a feed deletes its items, events and poll history with it; deleting a brand deletes its feeds, plans, channels and posts with it.
  • Site Analyses: kept with no expiry today, including for addresses pasted by someone who never signed up. A newer analysis of the same site does not replace an older one. Ask us and we will delete the analyses of your domain.
  • Aggregate funnel counts: kept indefinitely; they contain no personal data.
  • Server logs: the web server's access and error logs are rotated daily and deleted after 14 days. The application log is rotated by size (six files of at most 10 MB), and the system journal is capped at 1 GB, so their oldest lines are overwritten as new ones arrive rather than after a fixed number of days.
  • Backups: the database is copied every night to a backup on the same server, and each copy is deleted after 14 days. Something deleted from the live database can therefore survive in a backup for up to 14 days.
  • Your session cookie: 14 days, or until you sign out.
  • Visit measurement (only if you chose "Accept"): the cookies last as listed under Visit measurement. Google Analytics keeps the event data for 14 months; per Microsoft's documentation, Clarity keeps session recordings for 30 days and aggregated data for up to 13 months. Your choice in mf_consent stays in your browser until you change it or clear the site's storage.
  • Your account and everything attached to it: until you delete it. After you delete it, 14 more days, then it is erased (see below).

7How it is protected

  • Everything runs over HTTPS with a valid certificate.
  • Passwords are hashed with Django's password hasher. We cannot read yours.
  • Channel tokens, Bluesky App passwords, own-app client secrets and private-feed authentication headers are encrypted at rest with Fernet.
  • API keys exist only as SHA-256 digests.
  • Credential-looking fields are redacted out of delivery logs before they are stored.
  • Each account only ever sees its own brands, feeds and posts; that scoping is enforced in the queries themselves and covered by tests.

If you give a private feed an authentication header so we can read it, that header is encrypted at rest like every other credential we hold. Even so, prefer a read-only or feed-specific token there rather than a password you use for anything else — that is good practice regardless of what we do.

We are a small operation, not a certified one. This page claims no ISO or SOC audit, because there has not been one.

8Your rights

If you are in the EU/EEA, the GDPR gives you the right to:

  • Access — get a copy of what we hold about you.
  • Rectification — have wrong data corrected.
  • Erasure — have it deleted.
  • Restriction — have us pause processing while a dispute is sorted out.
  • Portability — get it in a machine-readable form. Your posts are already exportable as CSV, ZIP, RSS and calendar files from inside the app.
  • Objection — object to processing we base on legitimate interests.

Email [email protected] and we will answer within 30 days. There is no charge, and we will not ask you to explain why.

If you are unhappy with how we handled it, you can complain to the Croatian data protection authority, AZOP (Agencija za zaštitu osobnih podataka, Zagreb — azop.hr), or to the supervisory authority where you live.

9Deleting your data

Sign in, open the account menu, choose Account settings and use Delete account at the bottom. You confirm with your password (or, if you signed up with Google, by signing in with Google again). If you cannot sign in, use the contact form with the address on the account and we will do it for you.

The moment you delete it: you are signed out everywhere and nobody can sign in to the account or use its API keys; every connected channel is disconnected and its encrypted access and refresh tokens and app keys are deleted (for YouTube we also revoke the grant at Google); automations are switched off, feeds stop being read, and posts waiting in the queue are cancelled, so nothing more is published. A paid subscription is set to end with the current billing period. We email you a link to take the deletion back.

For the next 14 days (the grace period) the rest of your data is kept, switched off, so that link can restore it: open it and the account comes back as it was, except that channels have to be connected again, because their tokens are already gone.

After 14 days a nightly job erases your user record and everything hanging off it: your brands and their settings and logos, your Content Plans and their topics, your feeds and their stored authentication headers, every item and change event ingested from them, your automations, templates, generated posts and their delivery logs, your notifications, your API keys, your billing records with us, the channel records, and the files on our server: rendered post images, Shorts and uploaded logos. What we keep is a single line saying that account number N was erased on a given date and how many rows went with it — no email, name or content. Invoices for anything you paid stay with Stripe, our payment processor, as tax law requires.

Removing a single channel under Channels deletes that channel's stored tokens and keys at once, without deleting the account (see also YouTube).

Site Analyses are stored against a domain, not an account, so deleting your account does not remove them by itself. Email us and we will delete the analyses of your domain too. Backups age out as described in section 6, so erased data can survive in a backup for up to 14 days after the grace period ends.

One more thing to be straight about:

  • You do not need us in order to cut off access. You can revoke MagpieFeed's permission yourself, immediately, in the platform's own settings: Facebook and Instagram under Business Integrations (this covers MagpieFeed's own Meta app, and your own Meta app if you used one), X under connected apps, Bluesky by deleting the App password, Google sign-in and YouTube at security.google.com/settings/security/permissions (or, for an older connection made with your own Google app, by deleting that OAuth client); for Telegram, revoke the bot token with @BotFather, and for Discord, delete the webhook in the channel's settings. That invalidates the credential no matter what we still hold, and it takes effect instantly.

When you remove MagpieFeed (or the Meta app you connected it with) in your Facebook settings and ask for your data to be deleted, Facebook tells us and we delete every Facebook and Instagram connection made for you through that app straight away, including its tokens. Facebook then shows you a link to a status page with a confirmation code. The steps are on magpiefeed.com/meta/data-deletion/.

10Changes to this policy

If we change this page we update the date at the top. If a change materially affects what we do with your data — a new sub-processor, a change of language-model provider, a new category of data — we will email account holders rather than quietly editing the page.

Questions

MagpieFeed, run by a private individual based in Croatia. Operator details are available on request through the contact form. See also our terms of service.