Privacy Policy
Effective: July 27, 2026
EzPanda Inc. respects your privacy. This Privacy Policy describes how we collect, use, disclose, and protect personal information when you use Slopsleuth (the "Service"). Subscription payments are processed and billed by our wholly-owned subsidiary, WP North Entertainment Group Ltd.; charges may appear under either name.
What we collect
- Account information — name, email (via Google OAuth)
- Payment information — handled by Stripe; we never see or store full credit-card numbers
- Manuscripts — text content you upload for audit (see below)
- Usage data — aggregate, cookieless web analytics (pages visited) and standard server access logs (request paths, timestamps); we do not meter individual audits
- Ad-click identifier — only if you reach us by clicking one of our ads, so we can tell which ads bring in subscribers (see Measuring our own ads below)
Manuscript handling — our commitment
An uploaded manuscript is staged briefly on disk during parsing,
then deleted before any audit runs. Specifically: when you
upload a file, our backend writes it to a Cloud Run container's
ephemeral local /tmp directory only long enough for
python-docx (or the text reader) to parse it into memory — typically
milliseconds. The temp file is then unlinked from disk before any of
the five audit functions execute. From that point on, audits operate
on the in-memory parsed manuscript only.
We do not retain copies of your manuscripts on our servers, in backups, or in any persistent storage. The Cloud Run containers that run Slopsleuth are ephemeral — they have no persistent disk, and their temporary storage is held in memory and discarded when an instance is replaced. We do not log, transmit, or redistribute manuscript text. We do not use your manuscripts to train, fine-tune, or improve any machine-learning model — ours or any third party's. (Slopsleuth does not currently run any machine-learning models; audits are pattern-based regex with hand-tuned thresholds.)
The audit report exists only in your active session and is never written to our storage; the only lasting copy is the PDF or text report you choose to download to your own device. We do not meter or keep a record of individual audits. The account data we retain is limited to your profile and subscription details (name, email, plan, and billing identifiers), with payments handled by our processor, Stripe; standard server logs record request metadata such as timestamps and IP addresses, never manuscript content. None of these records contain your manuscript. See our Methodology page for the full end-to-end description of how an upload is processed.
How we use information
- Provide and operate the Service (run audits, return reports)
- Manage your Account, authenticate logins, and process payments
- Communicate about Account and service-related notices
- Detect, investigate, and prevent fraud or abuse
- Comply with legal obligations
We do not sell your personal information for money, and we never use your manuscripts or audit output for advertising or profiling. Our public marketing website is set up to show third-party ads, though none are being served at present — see Cookies & advertising below for exactly how that works and how to opt out.
Sharing
We share personal information only with:
- Stripe Inc. — for payment processing
- Google LLC — for sign-in (we receive name, email, Google ID)
- Google AdSense and advertising partners — if and when ads are served on our public marketing website, cookies and device/online identifiers collected there to serve, personalize, cap, and measure advertising (see "Cookies & advertising" below)
- Google Ads — the click identifier described under "Measuring our own ads", so we can tell which of our ads lead to subscriptions
- Hosting/infrastructure providers — under written agreements that restrict use to operating the Service
- Legal compliance — if required by law or to protect rights
Your rights
Depending on where you live, you may have the right to access, correct, delete, or port your personal information. Contact support@slopsleuth.app to exercise these rights.
Cookies & advertising
The Slopsleuth web application
(my.slopsleuth.app) uses only the cookies required to operate
the Service: authentication, session, and Stripe checkout. We do not run
advertising or cross-site tracking inside the audit tool itself, and no
manuscript content or audit output is ever shared with advertising
partners.
Our public marketing website (slopsleuth.app)
carries the code for advertising served by Google AdSense.
No ads are currently being served on it, so the cookies
below are not presently set by AdSense — but the code remains in place, and
if ad serving begins the following applies:
- Google and its partners use cookies and similar technologies — including the Google advertising / DoubleClick cookie — to serve and personalize ads based on your visits to this and other websites.
- Third-party vendors and ad networks may set or read cookies and identifiers in your browser to measure ad performance and limit how often you see a given ad.
- Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to our site and/or other sites on the internet.
Measuring our own ads
We advertise Slopsleuth on Google Search. When you arrive from one of our
ads, Google appends a click identifier (gclid) to the link.
We store that identifier — along with any campaign parameters on the link
and the time of your visit — in a first-party cookie
(sl_attr) on slopsleuth.app for
90 days. If you go on to start a subscription, we report
that click identifier, the time, and the plan amount back to Google Ads so
we can tell which ads actually bring in subscribers.
- We never send Google your name, email address, or any part of your manuscript or audit results. The report contains only the click identifier, a label ("Trial start"), a timestamp, and an amount.
- The cookie exists solely to connect one signup to the ad that produced it. We do not use it to build a profile of you, and we do not use it to target you with further advertising.
- If you did not arrive from one of our ads, this cookie is never written and nothing is ever reported.
- We do not set this cookie at all for visitors in Europe. If your browser reports a European time zone (the EEA, the UK, Switzerland, or the EEA's Atlantic islands), the cookie is skipped entirely and the click is simply never attributed. The check happens inside your browser — it involves no network request, no third party, and no location lookup.
-
Anywhere else, you can prevent it by blocking or clearing cookies for
slopsleuth.app, or by removing thegclidparameter from the address bar before the page loads.
You can control or opt out of personalized advertising:
- Manage Google ad personalization: adssettings.google.com
- Industry opt-out tools: aboutads.info/choices and optout.networkadvertising.org
- How Google uses data from sites that use its services: policies.google.com/technologies/partner-sites
Where consent would be required (including the EEA, UK, and Switzerland), we do not set non-essential advertising cookies at all. Rather than ask you to accept them, we skip them: no ads are currently served on this site, and the ad-measurement cookie described in "Measuring our own ads" is never written for visitors whose browser reports a European time zone. There is consequently no consent to give or withdraw, and no cookie banner.
We do not sell your personal information for money. Depending on your jurisdiction, any use of advertising cookies described above may be treated as "sharing" or a "sale" of personal information for targeted advertising under certain U.S. state privacy laws (such as the CCPA); the opt-out tools above let you exercise those choices.
Contact
EzPanda Inc.
Email: support@slopsleuth.app