Vagant · Updated November 10, 2026
Privacy policy
Vagant helps people discover study places and connect with other members. You can browse without an account or location permission.
What changed on November 10, 2026
This page now names everything we store, including check-ins, Study Passport pages, push tokens and crash reports; says that only photos added to a place are held for review; explains who can see Scenes, public lists and reviews; and says how long backups and server logs are kept and what happens if a backup has to be restored. Scenes shared with Everyone are now shown only to signed-in members, and a member you block, or one we suspend, no longer has their reviews shown to you.
Information we use
For accounts we store your name, email address, authentication identifiers, and a password hash when you use a Vagant password. Firebase processes sign-in information. We store your saved places, profile bio and pictures, connections, messages, circles, study plans, Scenes, check-ins, Study Passport pages, submissions, reviews, photos, seating reports, and support requests so these features work. If you allow notifications, we store your device's push token to send them; the app asks our server to remove it when you sign out, and it is deleted with your account. When the app crashes or hits an error, it sends our server a report of the error, the screen it happened on, and the app version and platform, with email addresses, ids and other identifying details removed; reports are written to our server logs without your account or network address. Optional usage counts are switched off on our server at present, so none are kept. If we switch them on and you have turned them on in the app, it sends events such as searching, opening or saving a place, with the time since the app opened, the number of results, the length of the search text, the filters used and a random session id; they carry no account, search text or place, and are deleted after 30 days. Feedback you send from the app is stored with its topic, message, the place it is about and, if you add one, your email address; it is not linked to your account and is kept after you delete your account unless you ask support to remove it.
Location and photos
Location is requested when you choose to find nearby places. Coordinates can be sent to our server to retrieve nearby results. We do not publish your live location or store your GPS position. If you check in at a place, add a page to your Study Passport or share a Scene, we keep that place and its date with your account; check-ins are visible only to you unless you change who can see them. A seating report identifies the place you report on and when. Uploaded images are resized, re-encoded, and stripped of embedded metadata, including any location. Photos you add to a place are held until a moderator approves them. Profile pictures, header photos, pictures you choose to show on your Spirit, Scene photos, and photos in messages and circles appear to their audience as soon as you add them and can be reported. Photos in your Study Passport are visible only to you.
Who can see information
Other signed-in members can find you by name and see whether you are connected. Where you appear to them, such as in a circle, a Scene or a list, they also see your profile picture and campus. Accepted connections can see your bio and exchange messages. Scenes you share with Everyone are shown to every signed-in member, with your name, the place, the time, what you wrote and any photo; people without an account cannot browse or open them. A Scene's photo is served to anyone who has its link, which the app gives only to members who can see the Scene. Scenes you share with Friends are shown only to your accepted connections. Your reviews show your name to anyone who opens the place, including people without an account, except members you have blocked or who have blocked you. Places you suggest never show your name to other members. Lists you make public can be opened by anyone, including people without an account. People without an account see only the name of the person who made a list and of anyone added to it as a collaborator; signed-in members also see their profile picture and campus. Moderators can review reported content and support requests to address abuse. Messages are access-controlled, but are not end-to-end encrypted.
Services that help Vagant work
Vagant's servers and database run on Fly.io in the United States. The app signs you in through Firebase Authentication, and through Google Sign-In when you choose it. Notifications are sent through Expo's push service and Apple Push Notification service, which receive your device's push token and the notification's title and short text. Google Places provides hours and photos for some places; when a Google photo is shown, your device loads it from Google. Map services on your device and external directions links may receive network information when you use them. Directory listings come from OpenStreetMap (© OpenStreetMap contributors, ODbL), Overture Maps Foundation places data (CDLA-Permissive 2.0, with Foursquare OS Places under Apache 2.0 and AllThePlaces under CC0), and the Institute of Museum and Library Services Public Libraries Survey (public domain); each listing names its sources, and photographs from Wikimedia Commons carry their author and licence. Your device loads Wikimedia Commons photographs directly from Wikimedia. Provider content is attributed where displayed. The website loads fonts from Google. Vagant does not sell personal information or use advertising tracking.
Retention and deletion
Account content is retained while your account is active. You can initiate account deletion in your profile after confirming your identity. This removes your account and associated member content; independently maintained place records can remain without an account attribution, and so can reports you filed about other members, including what you wrote in them, so moderators can still act on them. Temporary deletion safeguards prevent old sign-in tokens from restoring deleted accounts. Backups are copies of our database and uploaded photos that we make before changes to the service, and we test changes on copies of them. We delete these copies by hand: once a week we remove every copy, on our servers or off them, that is more than 30 days old, so no copy is kept for more than 37 days. If we have to restore a backup, an account or content deleted after that backup was made could come back with it: we do not yet keep a separate record of deletions that would let us find and remove those before the service is back online. If that happens to your account, ask support and we will delete it again. Server logs record each request's path, which can include the id of the place, member or content it was about, its result and timing, the network address of a request refused for coming too fast, the crash reports described above, and the service's own errors, which can include the details a failed request was handling. Our hosting provider keeps these logs for no more than 30 days; at present it keeps them for 7. A history of moderation and community actions is kept after an account is deleted, without that account's name or email. Unresolved support requests are kept until handled and then removed from the support queue.
Your choices and contact
You can decline location access, block members, sign out, request access or correction, or ask a privacy question through Vagant support. Do not include passwords or authentication tokens in a request. Vagant is intended for people aged 18 or older. If you believe a child has provided information, contact support.
We will update this page when our data practices change and provide notice of material changes through the service.