Privacy Policy

PostSpy is built around a simple idea: you tell us what you're watching for, and we tell you when something matches. We collect the least amount of data we can to make that work, we don't sell it, and we don't keep it longer than we have to. The detail is below.

The short version

• We store your email address and your watch list (page URLs, names, what you're looking for) on our servers so the service can run.
• To decide whether a new post matches one of your watches, PostSpy sends a short text snippet from that post to an AI model. The AI returns a yes/no plus a one-line summary in our own voice. We do not store the original post content — only the AI-generated summary we then show you.
• Your match history (the AI summaries + links back to the original posts) is stored on our servers under your account, and also cached in your browser. It is automatically deleted after 28 days.
• We use Stripe for payments and Resend for email delivery. We don't share your data with anyone else and we never sell it.

How PostSpy reads pages (session-bound architecture)

PostSpy analyzes content already loaded during your active, authenticated browsing sessions in your own Chrome browser. It does not perform hidden background browsing or unattended web automation on platforms whose terms disallow it.

Per-platform behaviour:

• LinkedIn, X, Instagram, Threads, and the Facebook main feed — PostSpy only reads posts that are already visible on your screen while you scroll naturally. No autonomous browsing, no scripted scrolling, no background tabs. The extension extracts post text and post URL only — never author names, profile URLs, headlines, or other person-data.
• Facebook Groups — PostSpy may briefly re-check the page on a slow schedule (no more than once per hour) by opening a visible tab and returning focus to your previous tab. Only runs while Chrome is open and you are not idle.
• Marketplaces, job boards, Reddit and similar lower-friction sites — if you opt in to background re-checks, PostSpy may quietly re-load these pages on a jittered schedule while Chrome is open and you are not idle.

The scheduler always honours: ±30% cadence jitter, a 4-minute minimum gap per page, a 150-page-load daily ceiling, an optional sleep window, automatic pause-when-you're-actively-browsing-the-same-site, and the Chrome idle / locked state.

We refer to these two behaviours as Scroll Mode (the high-friction surfaces — LinkedIn, X, Instagram, Threads, Facebook main feed) and Watch Mode (the lower-friction marketplace, job-board, classifieds, Reddit, community-group surfaces). The mode for any given page is determined automatically by the policy table built into the extension; you can see which mode applies to any spy from the spy edit drawer in your dashboard.

Just-in-time TOS classification: when a user adds a spy on a host PostSpy hasn't seen before, our server reads that host's terms of service and an AI classifier slots the host into the right mode. The result — host, tier, reasoning, and the date we read the terms — is cached for 7 days then re-checked weekly. Every classification we've ever made is publicly visible at postspy.ai/policies. We never store the raw terms-of-service body, only its sha256 hash (used to skip a re-classification when the page hasn't changed) and the AI's one-paragraph reasoning. If you believe a host's classification is wrong, email hello@postspy.ai and we'll re-classify on request.

Who we are

"PostSpy", "we", "us", or "our" refers to the operator of the PostSpy Chrome extension and the website at postspy.ai. If you need to reach us, email hello@postspy.ai.

What we collect

Account information

When you sign in to PostSpy with your email address, we create an account record containing:

• Your email address
• A unique account identifier
• Your subscription tier (free or paid) and, if applicable, your Stripe customer ID and subscription status
• Timestamps for account creation and updates

We use a hosted authentication service (Supabase) to issue and verify the magic-link sign-in. We do not handle or store passwords.

Your watches

For each page you choose to watch, we store:

• The URL of the page
• A short name (typically the page's own title)
• Your chosen check frequency ("often", "normal", or "rarely") and pause/active state

The natural-language description of what you're looking for, the AI prompt embedding, and the keyword hints derived from your chat are stored locally on your computer (in your browser's IndexedDB), not on our servers. We need the URL on the server to enforce per-tier limits and to refresh your watch when your browser isn't running.

Match history

When a post on a watched page matches your saved search, PostSpy stores a record of that match consisting of: the AI-generated summary describing the post (our own words, not a copy of the original), the URL back to the source post, the source site name, the match score and intent classification, and a timestamp. This record is stored both on our servers (so your dashboard works from any device) and cached in your browser for offline access.

We do not store the original post text, screenshots, images, or any other content from the source site. The original text is sent to our AI model at the moment of matching and discarded immediately afterwards.

Match records older than 28 days are automatically deleted from both the server and your browser.

Usage and billing

To enforce per-plan limits and bill correctly, we record metered usage on our servers: how many AI matching calls and emails we sent for your account each day, including the small AI model token counts used to compute precise cost. We do not record the content of those calls — only the counts and costs.

Content sent to the AI matching service

When PostSpy needs to decide whether a candidate post on one of your watched pages matches your saved search, it sends two things to Anthropic, our AI provider: (a) your watch description and (b) a short text excerpt from the candidate post (up to roughly 4,000 characters). Anthropic returns a yes/no decision plus a short summary written in our voice. That summary is the only thing PostSpy retains — the original post text is discarded as soon as the AI response is received. Anthropic's own data handling is governed by their privacy policy and their commercial API terms; under those terms, content submitted via the API is not used to train their models.

Cookies and local storage

The PostSpy website uses cookies and local storage only to keep you signed in across page loads. We do not run advertising trackers, analytics that profile individual users, or third-party social pixels on our site.

What we don't collect

• We do not collect or store your password for any third-party site you have PostSpy watch. You sign in to those sites directly in Chrome; we never see those credentials.
• We do not record your general browsing history. PostSpy only reads pages whose URLs you have explicitly added to your watch list.
• We do not access your microphone, camera, contacts, files, or location.
• We do not build a profile of you to sell to advertisers.

How we use your information

We use the information described above to:

• Run the PostSpy service — checking your watched pages, matching new posts against your saved searches, and sending you matches.
• Authenticate you and keep you signed in.
• Process payments and apply the limits associated with your plan.
• Communicate with you about your account (sign-in links, billing notifications, important service updates).
• Investigate abuse, debug problems, and maintain the integrity and security of the service.

Who we share information with

We share data with a small set of service providers, each only as needed to operate PostSpy:

• Supabase — hosts our database and authentication. Receives your email address, account record, watch metadata, and usage logs.
• Anthropic — provides the AI matching model. Receives your watch description and the candidate post text excerpt at the moment a decision is needed; does not retain the content after the API response.
• Resend — delivers match-notification emails on our behalf. Receives your email address and the message contents (summary text + link to the original post).
• Stripe — handles paid-plan billing. Receives your email address, account identifier, and payment details. PostSpy never sees your card number.
• Netlify — hosts the postspy.ai website. Receives standard web-server log data (IP, user-agent) for requests you make to the site.

We do not sell your personal information. We do not share it with advertisers, data brokers, or analytics platforms that build cross-site profiles. We will only disclose information to a third party outside of the providers above if we are legally required to (for example, in response to a valid subpoena).

Where your data lives

• Account information, watch metadata (including your saved-search description), match history (AI summaries only), and your settings: stored in our Supabase database.
• Locally-derived data your browser keeps for performance (the embedding vector for your search description, recently-seen post IDs to avoid duplicate matches, a cached copy of your match list): stored on your own computer, in your Chrome profile's IndexedDB.
• Usage and billing logs: stored in our Supabase database.
• Server logs: generated by Netlify (web) and Supabase (functions); rotated according to their standard policies.

How long we keep it

• Account data: kept while your account is active. Deleted on request (see "Your rights" below).
• Watch metadata: kept while the watch exists. Deleted within 24 hours of you removing the watch.
• Match history: kept for 28 days from the time of the match, then automatically purged from both our servers and your browser. Removable any time by deleting individual matches from the dashboard, clearing your account, or uninstalling the extension.
• Original post content: never stored after the AI matching call returns.
• Recently-seen post IDs (used to avoid re-matching the same post): kept locally for 48 hours, then automatically purged.
• Usage logs: retained for up to 24 months to support billing, fraud detection, and historical cost analysis.
• Server access logs: retained per our hosting providers' standard rotation (typically 30–90 days).

Your rights

You can, at any time:

• Sign out of the extension from the side panel or the Options page.
• Remove individual watches (deletes them from our servers).
• Clear your match history by clearing the extension's storage or uninstalling it.
• Cancel a paid subscription from the billing portal accessible inside the side panel.
• Request export or deletion of your account data — email hello@postspy.ai from the address on your account and we'll action it within 30 days.

Depending on where you live, you may have additional rights under laws such as the EU GDPR, UK GDPR, the Australian Privacy Act, or the California Consumer Privacy Act, including the right to access, correct, or restrict processing of your personal information. We honour all reasonable requests to exercise these rights.

Security

We use standard industry practices to protect your data: all traffic to and from postspy.ai is encrypted in transit (HTTPS), authentication is handled by a managed service that issues short-lived tokens, and access to our production database is restricted to a small number of authorised individuals. No system is perfectly secure; if we ever experience a data breach affecting your information, we'll notify you promptly.

International users and transfers

PostSpy is operated from Australia. Our service providers (Supabase, Anthropic, Resend, Stripe, Netlify) operate globally and may process your data in regions including the United States, Europe, or Asia. When data is transferred internationally, it remains subject to this Privacy Policy and to those providers' own privacy commitments.

Children

PostSpy is not intended for children under 16. We do not knowingly collect personal information from anyone under 16. If you believe a child has provided us with information, please contact us so we can remove it.

Changes to this policy

We may update this policy from time to time as the service evolves. Material changes will be announced via email to the address on your account at least 14 days before they take effect. The "Last updated" date at the top of this page always reflects the current version.

Contact

Questions, requests, or concerns about this policy or how we handle your data: hello@postspy.ai.