Privacy Policy

\n Last updated: {new Date().toLocaleDateString(\"en-US\", {\n year: \"numeric\",\n month: \"long\",\n day: \"numeric\",\n })}\n

\n\n

Overview

\n Anchor is a personal location logging application built on the\n decentralized AT Protocol network. All location check-ins are stored\n exclusively on your Personal Data Server (PDS), which you control.\n Anchor's servers do not store or cache your check-in data. This\n privacy policy explains how your data is handled within this\n decentralized architecture.\n

\n\n

Data Storage and Ownership

\n Your Data, Your Server:{\" \"}\n All location check-ins are stored exclusively on your Personal Data\n Server (PDS), which you control. Anchor's servers read your\n check-ins directly from your PDS when displaying feeds—we do not\n store or cache your location data.\n

\n Public Visibility:{\" \"}\n Location check-ins are stored unencrypted on your PDS and are\n publicly accessible to anyone who knows how to query AT Protocol\n records. This is by design of the AT Protocol's open architecture.\n

\n Data Portability:{\" \"}\n Since your data lives on your PDS, you can export, migrate, or\n delete it at any time through your PDS provider.\n

\n\n

What Anchor Stores

\n Anchor operates with minimal data storage. The only information\n stored on Anchor's servers is:\n

\n OAuth sessions:{\" \"}\n Encrypted authentication tokens to keep you logged in\n
\n Error logs:{\" \"}\n Technical logs for debugging (no personal location data)\n

\n\n

\n What Anchor Does NOT Store\n

\n Anchor does not store, cache, or index any of the following:\n

\n Your location check-ins or coordinates\n
Venue names or addresses
Photos or images you upload
\n Text descriptions or messages\n
Your location history

\n All of this data is written directly to your Personal Data Server\n (PDS) and read from there when needed. Anchor acts as a client\n application that communicates with your PDS—we are not a data\n warehouse.\n

\n\n

How We Use Your Information

\n To authenticate you via AT Protocol OAuth\n
\n To write check-ins directly to your PDS on your behalf\n
\n To read check-ins from your PDS and the PDS of users you follow\n
\n To resolve venue information via OpenStreetMap/Overpass API\n
\n To maintain and improve the Anchor service\n

\n\n

Third-Party Services

\n Anchor integrates with several third-party services to provide\n functionality:\n

\n AT Protocol Network:{\" \"}\n For decentralized data storage and social connectivity\n
\n Bluesky:{\" \"}\n For authentication and following relationships\n
\n OpenStreetMap/Overpass API:{\" \"}\n For venue search and location enrichment\n
\n Val Town:{\" \"}\n Our hosting platform for the web service\n

\n\n

Data Security

\n We implement appropriate security measures to protect OAuth\n sessions, which are encrypted using industry-standard methods. Since\n we do not store your location data, the security of your check-ins\n depends entirely on your chosen PDS provider's security practices.\n

\n Important:{\" \"}\n Location data stored on your PDS is not encrypted and is publicly\n accessible through the AT Protocol. Only check in at locations\n you're comfortable sharing publicly.\n

\n\n

Your Rights and Choices

\n Access:{\" \"}\n You can access all your data through your PDS\n
\n Deletion:{\" \"}\n You can delete check-ins through the Anchor app or directly on\n your PDS\n
\n Data Portability:{\" \"}\n You can export your data from your PDS at any time\n
\n Account Deletion:{\" \"}\n You can disconnect from Anchor by revoking OAuth access in your\n Bluesky settings\n

\n\n

Children's Privacy

\n Anchor is not intended for users under 13 years of age. We do not\n knowingly collect personal information from children under 13. If\n you become aware that a child has provided us with personal\n information, please contact us so we can take appropriate action.\n

\n\n

Changes to This Privacy Policy

\n We may update this privacy policy from time to time. We will notify\n users of any material changes by updating the \"Last updated\" date at\n the top of this policy. Continued use of Anchor after changes\n indicates acceptance of the updated policy.\n

\n\n

Contact Us

\n If you have questions about this privacy policy or Anchor's privacy\n practices, you can:\n

\n Open an issue on our{\" \"}\n \n GitHub repository\n \n
\n Contact us on Bluesky at{\" \"}\n \n @dropanchor.app\n \n

\n\n

\n 🔒 Remember: Your Location Data Is Public\n

\n By design of the AT Protocol, your location check-ins are stored\n unencrypted and are publicly accessible. This enables\n decentralization and data portability, but means anyone with\n technical knowledge can access your location history. Please only\n check in at locations you're comfortable sharing publicly.\n

\n\n

\n \n ← Back to Anchor\n \n

\n );\n}\n","deleted","label",[174,175,156],"frontend","components","permalink","https://www.val.town/x/tijs/anchor-appview/code/frontend/components/PrivacyPolicy.tsx","extension","actionData","errors"]