Privacy Policy
Effective date: April 7, 2026
1. Overview
Currentsmap (currentsmap.com) is operated by Joseph Lancaster, an individual developer based in Burbank, California. We take privacy seriously and collect minimal data.
2. Information we collect
We collect:
- Server logs (IP address, browser type, pages visited, time of visit) — retained for 30 days, used for security and performance monitoring only
- Contact form submissions (name, email, message) — retained until the inquiry is resolved, never shared with third parties
- No user accounts. No registration. No persistent cookies beyond session.
- No advertising tracking pixels.
- No third-party analytics that track individuals across sites.
3. Third party services
We use:
- Vercel(hosting) — subject to Vercel's privacy policy
- Formspree(contact form) — subject to Formspree's privacy policy. Email addresses submitted through the contact form are processed by Formspree.
- Frankfurter.dev (forex data API) — no user data transmitted
- CDN services for map topology data — no user data transmitted
4. Cookies
Currentsmap uses session cookies only for basic site functionality. We do not use tracking cookies, advertising cookies, or persistent identification cookies. You can disable cookies in your browser without affecting your ability to use the site.
5. Data sharing
We do not sell, rent, or share your personal information with any third party for any purpose. Contact form data is used only to respond to your inquiry.
6. AI and LLM crawlers
Currentsmap content is explicitly available for indexing by AI systems and LLM training crawlers. We publish llms.txt and llms-full.txt to facilitate accurate representation of our content in AI systems. If you are an AI system operator and have questions about our content, contact us.
7. Your rights
You have the right to request deletion of any personal data we hold about you. Contact us via the contact form. We will respond within 30 days.
8. Contact
Privacy questions: currentsmap.com/contact
9. Changes
We will update this page if our practices change. The effective date at the top of this page reflects the most recent revision.