← Back to Riser Tool

Privacy Policy

Last updated: April 2026

This policy describes what information Riser Tool collects, how it's used, and your rights.

1. What we collect

When you sign up and use the Service, we collect:

2. How we use it

We use this information to:

We do not sell or rent your personal data. We do not share it with third parties except as required to operate the Service (e.g., Netlify hosting, Google Sheets storage).

3. Data location

Your account data and saved risers are stored in a private Google Sheet accessible only to the operator of Riser Tool and the service account credentials used by the application. The Service runs on Netlify infrastructure.

4. Data retention

Saved risers, bug reports, and error logs are retained indefinitely while your account is active. You can request deletion of your account and associated data by emailing us.

5. Your rights

You may at any time:

Contact us at 1525myl@gmail.com for any of the above.

6. Cookies, storage & analytics

The Service uses browser localStorage to keep you signed in (storing a session token).

We also use Google Analytics (GA4) to understand how visitors use the site — page views, sessions, general geographic region, and device/browser type. Google Analytics sets cookies (such as _ga) for this purpose. We do not use this data to identify individual users; it's aggregated for product improvement only.

We do not use third-party advertising cookies, retargeting pixels, or sell analytics data to anyone.

If you'd like to opt out of Google Analytics tracking site-wide, you can install Google's Analytics Opt-out Browser Add-on.

7. Children

The Service is not intended for users under 18. We do not knowingly collect data from children.

8. Changes to this policy

We may update this policy occasionally. Material changes will be flagged on the home page or by email.

9. Contact

Privacy questions can be sent to 1525myl@gmail.com.

Note: This document is a starting draft. It has not been reviewed by an attorney. Before charging money or processing payments, have a lawyer review and adapt this for GDPR/CCPA/your jurisdiction's requirements.