Privacy Policy
Context is designed to let you create, exchange, and manage contact information with strong user control. This policy describes the data Context processes in the app and on related services.
What Context collects
- Account data you provide, such as your name, email address, and authentication details when you use online features.
- Profile and platform data you choose to store or share, including usernames, links, notes, and optional photos.
- Contact records you create, scan, import, or exchange within the app.
- Optional location data when you choose features that store exchange locations, show nearby contacts, or use live mutual exchange proximity.
- Approximate location (your city/region) when you browse nearby events, and the events you choose to save with an Interested or Going status.
- Optional push notification tokens used to deliver mutual exchange notifications on online accounts.
- Diagnostic and crash data used to improve app stability.
How Context uses data
- To create and manage your profile and saved contacts.
- To exchange selected profile data with other users when you explicitly scan, share, import, or accept a contact exchange.
- To support optional online backup, restore, and multi-device sync for signed-in users.
- To power optional nearby and notification features when you enable them.
- To show events near you, let you share your event status with contacts you choose, and optionally sync saved events to your Google Calendar when you connect it.
- To troubleshoot bugs, crashes, abuse, and service issues.
Google Calendar integration
Google Calendar connection is optional. If you connect it, Context requests permission to view and edit events on calendars you own so it can create, update, and delete the Google Calendar events that you choose to sync from Context. Context currently performs these actions on your primary Google Calendar and does not fetch or display your unrelated Google Calendar events.
- Context sends the synced event title, date and time, location, description, and participation status to Google Calendar.
- Context stores the connected Google account email, the Google event identifier, and sync status locally so it can update or delete the same event later. Context does not receive or store your Google password.
- Disconnecting Google Calendar stops future synchronization and clears Context's local calendar links. It does not delete events that were already created in Google Calendar.
- You can also revoke Context's access from your Google Account permissions. A future sync will then ask you to reconnect only if you choose to use the integration again.
Context's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google Calendar data obtained through the API is not sold, used for advertising, or used to train generalized AI models.
Sharing
Context shares data only when you initiate an exchange flow, choose to back up or sync to your online account, or use supporting services required to deliver those features. Context is not intended to sell personal data.
Service providers used to deliver features: Firebase (Google) for accounts, sync, notifications, and crash reporting; Mapbox for maps and geocoding (receives coordinates you look up); EDM Train for nearby event listings (receives your approximate area); and Google Calendar only if you connect it for event sync. Event statuses you share are visible only to people already in your contact list, in the circles you select.
QR encryption and its limits
QR codes and share links use AES-256-GCM with a shared key included in every Context app. Anyone who extracts that key from the app can decode a copied QR code or share link. This protects against casual inspection, but does not provide confidentiality against a motivated attacker or restrict access to one recipient. Share only details you intend someone with a copy to read.
Cloud data is protected by encrypted network connections and service access controls. Context does not provide end-to-end encryption for cloud backups or contact notes.
Storage and retention
Context stores app data locally on your device. If you use online features, selected profile, contact, media, and metadata may also be stored in Context cloud infrastructure backed by Firebase services. Data is retained until you delete it, remove your account, or it is otherwise removed as part of normal service operations.
When you ask us to delete your account, we acknowledge the request within 7 days and delete your account data from our active systems within 30 days of receiving it. Crash and diagnostic reports are held by Firebase Crashlytics, not in your account, and they are tied to an app-generated identifier. Crashlytics retains crash reports and associated identifiers for 90 days before beginning removal from live and backup systems, so they can outlast the 30-day window. This applies in offline mode too, because crash reporting is separate from your account.
Your choices
- You can use Context in offline mode with reduced cloud-dependent functionality.
- You can disable nearby visibility, privacy-sensitive live features, and notifications in Settings.
- You can connect or disconnect Google Calendar in Settings and revoke access at any time through your Google Account.
- You can export your data, import backups, sign out, or delete your account from within the app. See the data-deletion page for step-by-step instructions, including how to request deletion after uninstalling.
Contact
For privacy questions about Context, contact jp.caldwell30@gmail.com.