1. What this covers
This note covers the LensBounty website (lensbounty.com) and the test-build app behind it. It's written to match what the software actually does today - nothing more, nothing less.
2. What we collect
Only what the product needs to run:
- Account basics: your email address and display name.
- Your password - hashed, never stored in plain text. We store a salted PBKDF2 hash; we cannot read your password back. Even so, don't reuse a password from another site in a test build.
- Your terms record: which terms version you accepted, for which role, and when.
- What you post: bounty titles, briefs, locations, rewards, deadlines - and, for shooters, the photo links you submit.
We do not ask for or store payment details, government ID, or precise device location. If the landing-page list view asks for your location to sort by proximity, that happens in your browser only - it is never sent to our servers.
3. How we use it
- To run the marketplace: showing open bounties, matching submissions to bounties, resolving winners.
- To show your display name to the other side of a bounty you're part of.
- To sign you in and keep your session working.
- To enforce the terms you accepted (that's what the terms record is for).
4. What we don't do
- No advertising, no ad trackers, no selling or renting your data. Ever.
- No analytics scripts or tracking pixels in this test build.
- No sharing your email with other users - counterparties see your display name only.
- Submission links are private: only you and the posting business can see a submitted photo link. Browsing shooters see a submission count, nothing more.
5. Where your data lives
Account and bounty data is stored in Cloudflare Workers KV on Cloudflare's network. The website itself is served by Netlify. Your session is a signed token kept in your browser's localStorage - signing out deletes it from your browser.
Lawyer review: a real policy needs to state storage regions, data processing agreements with Cloudflare/Netlify, and a documented retention schedule.
6. Third parties your browser talks to
Loading LensBounty pages makes your browser request resources from a few outside services. Like any web request, those services see your IP address and basic request data:
- Cloudflare - runs the API the app talks to.
- Netlify - serves the website files.
- Google Fonts - serves the typefaces.
- CARTO / OpenStreetMap and unpkg - serve the landing-page map tiles and the Leaflet map library.
None of these are given your account data by us; they're infrastructure your browser loads directly.
Lawyer review: depending on where users are (EU/UK especially), third-party font and tile loading may require consent handling. Decide before launch whether to self-host fonts and how to treat map tiles.
7. The test build and resets
This is a working test build. Accounts and bounties are real records, but the data may be reset or wiped between builds. Don't store anything here you can't afford to lose, and assume anything you post may disappear when we iterate.
8. Deleting your data
Ask, and we'll delete your account record and what you've posted. There's no self-serve delete button yet in the test build - contact us and we'll handle it manually.
Lawyer review / build item: a real launch needs self-serve deletion, a stated response window, and handling for data referenced by resolved bounties (e.g. a winner's record).
9. Your choices
- Sign out to remove the session token from your browser.
- Use a throwaway or unique password - this is a test build.
- Deny the location prompt on the landing page; sorting falls back to downtown Orlando.
- Ask us to delete your account at any time.
10. Age
LensBounty is for adults. You must be 18 or older to create an account, and we don't knowingly collect data from anyone under 18. If we learn we have, we'll delete it.
11. Changes to this note
If how we handle data changes, this page changes with it and the date at the top moves. Material changes will be flagged in the app the same way terms updates are.
12. Contact
Questions or deletion requests: add your contact email here before launch.