Privacy Policy

Last updated: October 6, 2026

Stanmer Software ("we", "us", "our") operates Stanmer Archiving at archiver.stanmersoftware.com (the "Service"). The Service lets organizations archive content from the social media accounts and websites they own or manage. This policy explains what information we collect, how we use it, and the choices you have.

1. Who this policy applies to

• Customers: organizations that subscribe to the Service, and the users they authorize.
• People whose content appears in a customer's archive, for example someone who commented on a customer's Facebook Page, Instagram post or YouTube video, or whose name or content appears on a customer's website. For that content, our customer is the data controller and we process it on the customer's behalf and according to the customer's instructions.

2. Information we collect

• Account information: name, email address, organization name and a securely hashed password.
• Connected platform data: when you connect a Facebook Page, an Instagram professional account or a YouTube channel, we receive an access token and, with your authorization, retrieve that account's content: posts, stories, videos, captions, descriptions, media, comments and replies, engagement and view counts, and public profile information. Where you grant the corresponding permission, we also retrieve account insights: follower or subscriber counts and the number gained and lost each day.
• Website captures: when you add a website you run or are authorized to archive, we visit its publicly accessible pages with an automated browser and store a copy of each page (its text, a screenshot when it changes, and a replayable archive file), including any content of other people that appears on those pages. We do not sign in to websites or capture pages that require a login.
• Analysis results: if your organization turns on comment sentiment analysis, we store the labels it produces for each comment (see section 5).
• Usage and security data: sign-in times, IP addresses and actions taken in the Service, recorded in an audit log for security and compliance.

3. How we use information

We use information only to:

• provide the Service, including archiving, search, export and scheduled synchronization;
• produce the reports and dashboards your organization sees, such as engagement, audience growth and, if your organization turns it on, comment sentiment;
• notify your organization's users when commenters they have chosen to follow comment on your accounts;
• secure accounts and prevent fraud and abuse;
• provide support and communicate with you about the Service; and
• comply with legal obligations.

We do not sell personal information. We do not use archived content for advertising, and we do not use it to train artificial intelligence or machine learning models.

Commenter following: an organization's users can choose to be notified when a particular commenter comments on the organization's accounts. This uses the commenter's public name or handle as it appears in the organization's own archive, is visible only to that organization, and can be turned off at any time.

4. Google user data

We request read-only access to YouTube data, and, where the customer grants it, read-only access to YouTube Analytics (the number of subscribers gained and lost each day), solely to archive and report on the connected channel for the customer who authorized it. If the customer turns on comment sentiment analysis, comments on their videos are analysed on our own servers only to show that customer the results (section 5); this data is not used to train any model. We do not transfer this data to others except as necessary to provide the Service, to comply with applicable law, or as part of a merger, acquisition or sale of assets with notice to users. Our staff do not read this data except with the customer's permission, when necessary for security purposes, or to comply with applicable law. YouTube data is also subject to the Google Privacy Policy.

5. Comment sentiment analysis (optional, in testing)

An organization's owner or administrator can turn on comment sentiment analysis. It is off by default. When it is on, comments in that organization's archive, from the start date the organization chooses, are read by a language model that labels each one as positive, negative, neutral or mixed, notes whether it is about the organization, the post's subject or other commenters, and lists the topics it raises. The post a comment replies to is used as context.

• The model runs on our own servers. Comment text is not sent to any outside artificial intelligence provider.
• The labels are shown only to that organization's users, in its reports and archive. They are produced automatically, can be wrong, and are not used to make decisions about the people who wrote the comments.
• Archived content is not used to train or improve the model.
• The organization can turn the feature off at any time; analysis then stops. Labels are deleted with the comments they describe, or sooner on request.

If we ever offer analysis by an outside provider, it will be a separate option the organization must choose, and we will update this policy before it is available.

6. Meta data (Facebook and Instagram)

We access Facebook Page and Instagram professional account data only with the account owner's authorization, and only to archive and report on that account for the customer. Our use of this data complies with the Meta Platform Terms.

7. Website archiving

Websites are captured by an automated browser that identifies itself as "StanmerArchiving" and, by default, follows the website's robots.txt instructions. Customers may only add websites they run or are authorized to archive. Archived pages are shown to the customer through a separate address (archiver-replay.stanmersoftware.com) so that archived pages cannot access the customer's account; each archived copy is reachable only through a short-lived link issued to the customer's signed-in users.

8. How we share information

We share information only with service providers that help us operate the Service, under agreements that require them to protect it:

• Cloudflare (network security and delivery: connections to the Service pass through Cloudflare)

We may also disclose information when required by law, to protect the rights and safety of our users or the public, or in connection with a merger, acquisition or sale of assets. A customer's archive is visible only to that customer's authorized users.

9. Security

Data is encrypted in transit using TLS. Platform access tokens are encrypted at rest. Each customer's data is logically isolated from other customers', and security-relevant activity is recorded in an audit log that cannot be altered. No system is perfectly secure; if a breach affects your information, we will notify you as required by law.

10. Retention and deletion

• Archived content, including website captures, screenshots and analysis labels, is retained until the customer deletes it or closes their account.
• After an account is closed, we delete its data from active systems within 30 days and from backups within 90 days.
• Customers can disconnect a platform account or stop capturing a website at any time. This stops further collection and, for platform accounts, deletes our stored access token.
• You can also revoke our access directly from your Google or Facebook account settings (Instagram access is granted through Facebook and can be removed there).

See Data deletion for step-by-step instructions.

11. Your rights

Depending on where you live, you may have the right to access, correct, delete or export your personal information, and to object to or restrict its processing. To exercise these rights, contact [email protected]. If your information appears in a customer's archive, we will refer your request to that customer as the data controller and assist them in responding. We will not discriminate against you for exercising these rights.

12. Cookies

We use a single essential cookie to keep you signed in. We do not use advertising or third-party tracking cookies.

13. Children

The Service is intended for businesses and organizations. It is not directed to children under 16, and we do not knowingly collect their personal information.

14. Where data is stored

Data is stored and processed in the United States.

15. Changes to this policy

We will post any changes on this page and update the date above. If we make material changes, we will notify customers by email before they take effect.

16. Contact us

Stanmer Software
[email protected]