How we handle captured content

Marketpon includes a browser extension that records social media posts you have already viewed, so you can study what performs. Because that involves content authored by other people, this page sets out exactly what happens to it — in more detail than a privacy policy usually carries, because the detail is the point.

It records; it does not crawl

The extension reads what your own logged-in browser has already rendered to you, on pages you navigated to yourself. It is a recorder, not a crawler, and the distinction is architectural rather than rhetorical:

• It sends no requests of its own to any social platform.
• It holds no platform credentials and cannot sign in as anyone.
• It cannot reach a page you have not opened. There is no list of URLs to fetch, no queue, and no server-side fetching of platform content.
• It does not defeat access controls. If a platform will not show you something, the extension cannot see it either.

In practice this means the extension can only ever hold a subset of what you personally were shown while using the platform normally.

What is recorded

For each post you scroll past on a page you opened:

• The post’s public text, its public engagement counts, its format, and when it was posted.
• The post’s public URL, and the display name and handle of the account that published it.
• Thumbnail image URLs, so the post is recognisable in your library.
• Any note you chose to write about why you saved it.

What is never recorded

• Private messages, direct messages, or anything behind a follow-only or friends-only wall.
• Contact details, email addresses, or phone numbers.
• Any content from a page you did not open yourself.
• Your own browsing outside the social platforms the extension is scoped to.

Who can see it

Captured content is stored against your brand workspace only. It is not pooled, not shared between customers, not aggregated into any cross-customer dataset, and not sold. Another Marketpon customer studying the same public account builds their own separate library; they cannot see yours and you cannot see theirs.

We do not use captured content to train any machine-learning model, ours or anyone else’s.

What it is for

Analysis. The library exists so you can see which formats, hooks and posting times work in your space, expressed as counts and medians computed from what you captured.

It is not a republishing tool. Marketpon does not offer a way to post someone else’s content as your own, and studying a competitor’s approach does not entitle you to copy their words or images. Reproducing a third party’s content is your responsibility and is covered by our Terms of Service.

Keeping it, and deleting it

• Captured content stays until you delete it or close your account.
• Deleting a capture removes it from your library.
• Closing your account deletes the workspace and everything captured into it.
• Content is stored encrypted in transit and at rest, on infrastructure listed in our Privacy Policy.

If a post is yours and you want it removed

If you authored a post that a Marketpon customer has captured and you want it removed from their library, write to privacy@marketpon.com with a link to the post. We will locate and delete copies of it.

Note that we hold a record of a post that was public when it was viewed; we are not the publisher of it, and removing it here does not remove it from the platform it was posted to.

Platform terms

Each social platform sets its own rules about automated access and data collection. The extension is designed to sit inside normal browsing rather than automated access, but you remain responsible for your own compliance with the terms of any platform you use it on.

Where a platform offers an official API for something, we use it. Publishing, analytics and account connection all go through official APIs with permissions you granted.

Questions

privacy@marketpon.com. A person reads it.