Overview
Social Archiver is designed as a local-first archive tool. Your archive is intended to live on your device, while the service may process the minimum data needed for authentication, sync, quota enforcement, billing status, and support.
Data we process
- Account information such as email, username, authentication identifiers, and device identifiers.
- Archive metadata needed for sync, deduplication, quota accounting, and web sharing when enabled.
- Billing metadata such as entitlement state, product identifiers, provider customer IDs, and renewal events.
- Support messages and diagnostic logs when you contact us or submit feedback.
- If you connect a Threads account, the Threads data described in "Connected Threads accounts" below.
Google place search and enrichment
Search text and result candidates are transient. We send the text and language or region settings needed for an explicit search, return the candidates to your client, and do not persist or cache that text or the official candidates in Social Archiver storage.
After you select a result, we may retain the selected Google Place ID and strictly normalized place facts, bounded public review text, photo URLs and dimensions, and acquisition provenance in the associated archive. We do not retain review authors, raw HTML, or raw provider responses for this flow.
Google Maps Platform processes official search requests. For the selected place only, Social Archiver may use an approved public-page acquisition path and Bright Data as an enrichment fallback processor. These providers process requests under their own terms and privacy policies.
Telemetry and retention
Aggregate operational telemetry may include non-sensitive usage type, outcome, latency, cost-control state, and fallback reason. It does not include search text or Google Place IDs.
Transient search text and official candidates are discarded after the request. Selected place data and provenance follow the retention of the associated archive and are removed from Social Archiver-controlled storage when that archive or your account is deleted, subject to limited backup, security, billing, and legal retention. Third-party processors may retain their own request records under their policies and contractual obligations.
Local archives
Saved posts, notes, and media are primarily stored locally by the mobile app, browser extension, or Obsidian plugin. If you enable sync or web sharing, related content and metadata may be sent to Social Archiver servers so those features can work.
Connected Threads accounts
Connecting a Threads account is optional. It lets you post to Threads from Social Archiver and save public Threads posts and profiles. When you connect, Meta asks you to approve the permissions these features use, and we receive and keep:
- Your Threads user ID and username, to show which account is connected.
- A Threads access token and its expiry time. The token is encrypted with AES-256-GCM before it is stored and is renewed automatically while the connection is active.
- For posts you send to Threads: the content you chose to post, and the resulting Threads post ID, link, and delivery status.
We use this data only to:
- Publish posts you send to Threads, and delete such a post from Threads when you delete the archive it came from.
- Fetch public Threads posts you ask to save, and public profiles and recent public posts of Threads accounts you choose to follow.
Threads data is processed on our hosting infrastructure. We do not sell it or use it for advertising. Public posts you save become part of your archive and follow the "Local archives" section above.
You can remove Threads data at any time:
- Disconnect Threads in Social Archiver settings. This deletes the stored token and account identifiers right away.
- Remove Social Archiver under Website permissions in your Threads account settings. Meta notifies us and we stop using the token. If you also request deletion, we delete the connection and the Threads post IDs and links we recorded, and give you a confirmation code.
- Delete your Social Archiver account, which deletes all of the above, including the content of posts you sent.
- Email [email protected].
Billing providers
Mobile purchases are processed through Apple or Google. Web purchases, when available, are processed through the checkout provider shown at purchase time. Social Archiver receives billing events required to update your entitlement, such as purchase, renewal, cancellation, refund, or expiration status.
No unauthorized access
Social Archiver does not ask for or provide access to another person's private accounts, credentials, devices, or restricted data. You are responsible for only saving content you are lawfully allowed to access and keep.
Contact
For privacy questions or account requests, contact [email protected].
Social Archiver is operated by Build and Deploy.