What SlipGuard collects, why, and how you can control it

This Privacy Policy describes what SlipGuard collects when you use the Service, why, and the choices available to you. It describes what the application actually does — nothing here refers to a service, tracker, or data use that does not exist in the product.

1. Information You Provide

• Account information: your name, email address, and password (stored as a one-way hash, never in plain text) when you register.
• Betting slip content: the selections you enter manually, or the screenshots/PDF documents you upload, and the text extracted from them — sport, competition, event, market, selection, and odds for each leg.
• Journal entries: the free-text reflections you choose to write about your own analyses.

2. Information Collected Automatically

• Session data: a session cookie and a CSRF (cross-site request forgery protection) token, both strictly necessary to keep you securely signed in. SlipGuard does not set any analytics, advertising, or third-party tracking cookie — confirmed directly against the running application, not merely asserted.
• Standard server logs: IP address, browser type, and request timestamps, generated by the web server for security and troubleshooting purposes.

SlipGuard does not currently use any third-party analytics service (such as Google Analytics) or advertising pixel. If that ever changes, this Policy will be updated first.

3. How We Use Your Information

• To run the deterministic structural risk analysis you request and show you the result.
• To maintain your History, Journal, and Planning History so you can revisit past analyses.
• To keep your account secure (authentication, rate limiting on sign-in attempts).
• To operate and improve the Service itself.

We do not use your betting slip content or journal entries for advertising, and we do not sell your personal data to anyone.

4. Cookies

SlipGuard uses only the session and CSRF-protection cookies described in Section 2 — both strictly necessary for the Service to function securely, and neither used for tracking or advertising. Because no non-essential cookie is set, no separate cookie-consent banner is used; this Policy is the disclosure.

5. Third Parties

We do not share your personal data with third parties for their own marketing purposes. Infrastructure providers that help us operate the Service — such as hosting and database providers — may process data strictly on our behalf, under contractual confidentiality, solely to keep the Service running. As of this Policy's last update, SlipGuard's production infrastructure has not yet been provisioned; this section will name specific providers once it has, rather than naming them speculatively now.

6. Data Retention

We retain your account and analysis data for as long as your account remains open, so your History, Journal, and Planning History stay available to you. If you delete your account (available at any time from your Profile page), your personal data is removed, other than what we are required to retain for a limited period for legitimate security or legal purposes.

7. Security

Passwords are hashed, never stored in plain text. Every customer-owned record (your slips, analyses, journal entries) is access-controlled so only you can view it — enforced at the authorization layer, independently verified, not merely declared. We encourage you to use a strong, unique password.

8. Your Choices and Rights

• You can review and update your account information at any time from your Profile page.
• You can delete your account at any time from your Profile page.
• You can delete individual slips, analyses, or journal entries you no longer want to keep, subject to the same durability rules that already apply inside the product (analysed records are archived rather than silently destroyed, to protect the integrity of your own history).

9. Children's Privacy

SlipGuard is intended for users aged 18 and over (see our Terms of Service). We do not knowingly collect information from anyone under 18.

10. Changes to This Policy

We may update this Policy as the Service evolves. We will update the "Last updated" date above whenever we do.

11. Contact

[A dedicated support and privacy contact channel has not been established yet — see the Contact page.] Questions about this Policy should be directed there once available.