Your context, on your terms.

Who we are

Context is a product of EdgeFirst. Questions about this policy or your information can be sent to founder@edgefirst.app.

Information you choose to connect

Context may process information you choose to provide in the app, including plans, notes, health information, and connected-service data. Your phone remains the source of truth, and you choose what a connected agent or service may access.

Google sign-in, Calendar, and Contacts

Google connections are optional. Context requests Google Calendar and Google Contacts separately, immediately before you choose each feature. Context uses openid and your Google account email only to identify the account you connected.

With Calendar permission, Context reads event and calendar details to provide schedule awareness, connect meetings with people and notes, and answer calendar questions for agents you authorize. With Contacts permission, Context reads names, email addresses, organizations, titles, and photos to fill People. Both permissions are read-only: Context cannot create, edit, or delete Google Calendar events or Google Contacts.

How Google user data is stored and shared

Google access and refresh tokens are stored in the iOS Keychain on your device and are not uploaded to Context servers. Calendar events are stored in Context's on-device database. When you enable agent calendar access, the relevant event index is included in your end-to-end encrypted Context manifest and is available only to agents you authorize. Turning agent calendar access off removes that index on the next sync.

Google contacts you import become People in your Context database. They may be included in your end-to-end encrypted Context data under the same sync and agent-access controls as other People records.

How Google user data is used and protected

Context uses information received from Google APIs only to provide or improve the user-facing Context features you choose to use. Context does not sell Google user data, use it for advertising, or use it to train generalized artificial intelligence or machine-learning models. Humans do not read Google user data except when you give affirmative permission, when needed for security, or when required by law.

We use reasonable safeguards to protect information in transit and at rest. The use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. See the Google integration guide for scope-by-scope details.

Sharing

Context does not sell personal information. We share information only as needed to deliver a feature you request, with a service or agent you explicitly authorize, to protect Context and its users, or when legally required.

Retention, disconnection, and deletion

You can decline either Google permission, stop Contacts import, disable agent calendar access, remove a Contacts connection, or disconnect Google in Context. You can also revoke Context from your Google Account security settings. Disconnecting stops future collection and removes tokens from the device, but does not by itself delete Google-derived information already imported or encrypted into your Context data.

Information remains until you delete the applicable records, disable the applicable sync control so the manifest can update, or request account deletion. To request help with access, correction, or deletion, visit Support or email founder@edgefirst.app.

Changes

We may update this policy as Context evolves. If a change materially affects how we use Google user data, we will update this page and seek consent before using that data for a new purpose.