Privacy Policy

Summary

PeekVault is a tool for browsing archived social media snapshots. We aim to collect as little personal data as possible while keeping the service reliable.

Information you provide

When you use the tools, you may submit inputs such as usernames or URLs. We process these inputs to query the Wayback Machine and generate results and exports.

Information we may collect automatically

• Basic logs: like most websites, our hosting provider may collect standard server logs (e.g., IP address, user agent, timestamps, and request paths) for security and debugging.
• Analytics: we use Vercel Analytics to understand aggregated usage, including page views, search outcomes, result interactions, and export interest. We also log these events on our servers with a random session ID stored in this tab for up to 24 hours. From your first search, a random browser ID is kept in a first-party cookie (pv_client) for up to 12 months, so a visitor is counted once however many tabs they use; our logs keep only a one-way hash of it. Event logs include the entry page and referral campaign, but do not include uploaded archive contents.

Third-party services

PeekVault communicates with third-party services to provide functionality:

• Internet Archive / Wayback Machine: used to retrieve CDX snapshot data and archived URLs.
• X (Twitter) embed services: if you use tweet previews, your browser may load resources from platform.twitter.com, and our servers may request embed markup from publish.twitter.com.
• Cloudflare R2: we store selected operational logs and analytics events in a private bucket for reliability and usage analysis.
• Google AdSense: if ads are enabled, Google and its partners may use cookies, web beacons, IP addresses, and similar identifiers to serve ads, measure ad performance, limit repeated ads, and help keep advertising relevant.

These third parties may process data under their own privacy policies. We encourage you to review their terms if you use those features.

Checkout

PeekVault sells one-time access passes through Stripe's hosted Managed Payments checkout. Stripe processes your payment information; we do not receive or store your full card details. We send Stripe the selected plan, tool and offer, file format, result count, acquisition source, random session, search and click IDs, and a one-way browser identifier when available. These connect a verified payment to the offer you used. Search text and uploaded archive contents are not included in payment metadata or checkout return links.

A signed, first-party, HTTP-only cookie keeps your paid access until its expiry. Separate signed payment receipts stay in this browser for up to 60 days so we can recover a completed purchase if you did not return from checkout. The submitted search target may be kept in this tab's session storage for up to 24 hours to reopen your search after checkout. It is not sent to Stripe. We log checkout creation and verified payment events without card details or customer email addresses. Stripe keeps purchase records under its own privacy policy.

Advertising cookies and choices

Third-party vendors, including Google, may use cookies to serve ads based on prior visits to PeekVault or other websites. Google's use of advertising cookies enables Google and its partners to serve ads based on visits to this site and other sites on the Internet.

You can learn how Google uses information from sites and apps that use its services at policies.google.com/technologies/partner-sites. You can opt out of personalized advertising at Google Ads Settings.

Data retention

Search reliability logs can include the public username or URL you searched, the outcome and request duration. Our private Cloudflare R2 archive keeps selected operational logs and analytics events for up to 400 days, and sanitized ingest copies for up to 60 days. We remove IP addresses, user-agent strings, the usernames and URLs you searched, and browser cookies before writing to this archive. Our hosting and analytics providers have their own retention periods. The tab session ID expires after 24 hours and the browser ID 12 months after your last search; neither deletes events already recorded.

Contact

If you have privacy questions, please reach out via Contact.