Privacy
What personal data Feedkeep holds, why we hold it, and what you can ask us to do about it.
Who we are
Feedkeep watches public Instagram profiles on behalf of its customers and keeps a record of what those profiles publish and what changes.
Write to contact@feedkeep.io about anything on this page.
1. Customers
Data you give us by using Feedkeep.
- Your email address and a password, stored scrambled so it cannot be read back.
- If you sign in with Google: the number Google gives your Google account, so it can be recognised the next time. Nothing else from your Google account is kept.
- Which plan you are on, whether it is paid, and when it renews.
- Which profiles you watch, when you added them, and any notes or labels you attach to items. Notes are private to your account.
- A record of actions that cost money — refreshes, imports — used for billing and limits.
- Web server logs, which record your IP address as any web server does. Used to run the service and to distinguish a person from an attack.
Card details never reach us. They are entered into the payment processor’s own form and held by them.
Lawful basis
Performance of a contract: you asked for the service and it cannot be provided without this data. Server logs are held on the basis of legitimate interests in keeping the service running and secure.
Retention
For as long as you hold an account. On closure the account is deleted, apart from invoices, which tax law requires us to keep and which are used for nothing else.
2. Archived profiles
A customer chooses which public profiles Feedkeep watches. The subject of a profile is not a customer, is not asked, and is not notified. This section states what is held about them.
Source
What the profile shows to anyone on the public internet, read through a third-party company that specialises in public Instagram data.
What is held
- Username, display name, biography, links, profile picture, category, verification status, follower and following counts.
- Public posts, reels, stories and highlights, kept as the original file at the quality published.
- A dated record of changes: additions, edits, and items no longer present on the profile.
- The raw responses received, so an error in how they were read can be corrected without fetching again.
- Other fields a profile makes public, which Instagram adds to and removes from over time.
What is not held
- Anything from a private account. A profile that is private, or becomes private, cannot be read, and only that fact is recorded.
- Messages, or anything else never made public.
- Email addresses and phone numbers, unless the profile has published them at any point while we have been watching it, or Instagram exposes them.
Where an item is no longer on a profile, that is what is recorded. Instagram does not allow anyone outside to distinguish a deleted post from one archived by its author, and no such claim is made.
3. Followers and accounts followed
Where a customer enables follower tracking for a profile, Feedkeep keeps a list of the accounts that follow it and the accounts it follows. For each: username, display name, profile picture, whether the account is public and whether it is verified, and when the connection was first and last seen.
Nothing further. No posts, no archive, no history beyond the connection. It exists so a customer can see that an account gained or lost followers.
It is off by default, set separately for each profile and each direction. Turning it off stops the collection.
4. Lawful basis for sections 2 and 3
Legitimate interests. That basis requires a purpose, a demonstration that the processing is necessary for it, and a weighing against the interests of the people concerned.
Purpose
Feedkeep is sold for four uses:
- Keeping a copy of your own profile.
- Monitoring a competitor or a brand — what a company publishes, and what it removes.
- Keeping a record that has to hold up: what was published, when, and when it disappeared.
- Journalism and research, where what was published before removal is the point.
Necessity
A record of what was removed cannot be produced without having kept a copy while it was there. A service holding only what is currently on a profile would not do the thing it is bought for.
Limits
- Only material that was already public. Nothing hidden, nothing purchased, nothing obtained by signing in as anyone.
- Customers’ archives are private to the customers watching them, and search engines are instructed not to index them. The single exception is a public demonstration of the product, showing a small number of large public accounts so the service can be judged before it is bought. Those profiles, and only those, are open to search engines and their pages may appear in search results. They are shown in good faith for that purpose, and any account is removed from the demonstration on request — see section 11.
- Private accounts are not supported, and the service is not sold as a way to monitor a private individual.
- Follower tracking, which is the widest collection here, is off unless a customer turns it on.
- Objections are considered and answered — see section 11.
Sensitive material
Some public posts are sensitive by nature. Feedkeep does not search for, filter for or index such material, and it is not what the service is for. Where it is present it is present because the person published it publicly themselves, which the law treats differently from sensitive data that has been uncovered.
5. Why individual notice is not given
Holding personal data obtained from a source other than the person normally requires telling them directly. That is not possible here: it would mean contacting every follower of every archived account, whose contact details we do not hold, which would require collecting far more data about far more people than is held now.
The law permits a public notice instead where individual notice would involve disproportionate effort. This page is that notice. It is why it sits on the public website rather than inside the product, and why search engines are asked to index it.
6. How long data is held
There is no fixed deletion date for archived material. An archive is built because a customer paid for it to exist, and its value is that it continues to exist.
Access ends when a subscription ends. A customer who stops paying stops seeing the archives they were watching, at the end of the period they paid for.
The material itself is kept for at least 90 days after the last customer watching a profile has gone. A customer returning inside that window finds their archive as they left it. Past it, nothing is guaranteed: where the material is still held it may be restored, and where it is not it is gone.
What is retained after that is determined by:
- Whether any customer still watches the profile.
- Whether the material is needed for the establishment, exercise or defence of a legal claim, by us or by a customer.
- The cost of continuing to store it.
Material is removed when none of those apply. Profile records — that an item existed on a date and was removed on another — are kept, being a small fraction of the size of the files they describe.
7. Who else handles the data
These companies hold or handle part of it on our behalf. Each acts only on our instructions, under data-processing terms forming part of our contract with them.
- Server hostThe machine running Feedkeep and its database, in Germany.
- File storage providerImages and videos, and nightly database backups.
- Instagram data providerReads public pages on our behalf. Receives the username of a profile being checked and nothing about any customer.
- Payment processorYour name, email and card details, held by them. We never see or store a card number.
- Email providerYour address, in order to send to it: the code that opens an account, and a password reset when you ask for one.
Google, if you choose to sign in with it. Google tells us your email address and that it has confirmed it, and learns that you signed in to Feedkeep. For that, Google acts under its own privacy policy rather than on our instructions. Nothing is sent to Google if you sign in with a password.
Personal data is not sold, and is not shared with anyone for advertising. None of the above receives an archive.
8. Where the data is
The server and database are in Germany. Some companies in section 7 are based outside the European Union, or store data outside it. Where that happens the transfer is covered by the standard contractual clauses published by the European Commission, or by an adequacy decision where one applies.
9. Cookies and tracking
This website sets no cookies. No advertising pixel, no tag manager, nothing from a social network, and no request to any other company: every file this page loads is served from feedkeep.io.
Since 5 September 2026 visits to this website are counted, and since 11 September 2026 so are visits to the public demonstration at demo.feedkeep.io, which is counted separately. Both use analytics software we run ourselves on the same server as the rest of the service. It sets no cookie and stores nothing in your browser. For each visit it records the page address, the page title, the site you arrived from, your screen size and your browser language. What a customer does inside their own account is not counted.
Your IP address is used, at the moment of the request, to work out an approximate location and to derive a short-lived identifier that separates one visit from another. It is not kept: there is no field in that database that holds an IP address. Nothing collected here is shared with anyone, is used for advertising, or can follow you to another website.
You can turn it off for yourself. Setting a value named umami.disabled in your browser’s local storage stops the script sending anything at all, and the rest of the site works exactly as before. Browsers keep that storage separately for each address, so it is set once on feedkeep.io and once on demo.feedkeep.io.
Inside the product, one cookie keeps you signed in. It is necessary for the service to function and is used for nothing else. That is why there is no consent banner here.
This page will be updated before that changes, not after.
10. Rights
If you are a customer
You can ask for a copy of what we hold about you, ask us to correct it, ask us to delete it, ask us to restrict what we do with it, and ask for it in a portable form. Close your account and it is deleted. Requests are answered within one month and are free.
If your profile is in an archive
You may ask what is held about you, ask for it to be corrected, and object to it being held. Requests are answered within one month. Proof that you control the account is required before any request is answered, and no archive is released to anyone who has not provided it.
The right to object and the right to erasure are not absolute rights. Section 11 sets out the grounds on which a request is refused.
11. Objections and removal requests
Write to contact@feedkeep.io stating the profile and that you control it. We reply within one month.
Each request is decided on its facts, and refusal is a normal outcome. The law allows a controller to refuse where it has compelling legitimate grounds that override the objection, and where the material is needed for the establishment, exercise or defence of legal claims. Keeping a record that can be relied on later is a stated purpose of this service, so that ground applies to much of what Feedkeep holds.
Two facts about the service shape the answer:
- There is one archive per profile, shared by every customer watching it. Removing a profile does not remove one copy; it removes the record for every customer at once, including any who are relying on it.
- Everything held was published publicly by the account itself, and nothing was obtained privately.
Where a request is refused we state which ground applies. You may complain to a data protection authority — see section 15.
Requests concerning an account belonging to a child are treated differently: see section 13.
The most effective way to stop any service from archiving or monitoring an account is to make it private rather than public. A private account cannot be read by Feedkeep, and cannot be read by anyone else outside Instagram either. Nothing published to the public internet can be recalled from everyone who saw it.
12. Security
- All traffic is encrypted, and archives are behind a login.
- Images and videos are served through temporary links that stop working within the hour.
- The database is backed up nightly, off the machine. A backup is restored and its rows counted every week to confirm the backups work.
- Access to the underlying systems is limited to the operator.
13. Children
Feedkeep is for businesses and adults and is not offered to anyone under 18. Archives of accounts belonging to children are not knowingly built. Where one is reported and confirmed, it is removed.
14. Where you live
This policy is written to the European rules, which are the strictest of the major regimes. The rights in section 10 are named differently elsewhere.
European Union and EEA
As written above.
United Kingdom
The United Kingdom retains an equivalent law and the same rights apply. The supervisory authority is the Information Commissioner’s Office.
California
You may request what is held, request a copy, request correction or deletion, and you will not be treated differently for asking. We do not sell personal information and do not share it for cross-context behavioural advertising. No part of the service does either, and we run no advertising.
Elsewhere
Local law applies where you are. Write to us at the address above.
15. Complaints
Complaints can be made to us at the address above, and to the data protection authority in the country where you live or work, with or without contacting us first.
16. Changes
Changes are published on this page with the date. A change that materially affects people whose profiles are archived is published before it takes effect.
Questions, and requests to be removed from an archive: contact@feedkeep.io