YOUR INFORMATION. YOUR CHOICES.
Privacy policy
Get Context app and supporting services.
Last updated October 6, 2026
About Get Context
Get Context helps you save memories, organize collections, share selected content, and ask Cue questions. Michael Griffin operates Get Context. This policy covers the app and its supporting services, not the separate marketing website.
Contact hello@getcontext.studio with privacy questions or requests. The first invitation-only beta is intended for adults age 18 or older in the United States.
Information you provide
We process your email address, account identifier, and authentication information to provide account access and recovery.
Content you save may include titles, notes, photos, links, tags, places, addresses, plans, dates, reflections, and collections. Content you enter about other people may also be included.
Your optional profile information may include your name, photo, birthday, home city, interests, goals, people you spend time with, barriers to activities, weekend preferences, reconnection preferences, and preferred travel distance. We use profile information to save your choices and personalize supported app experiences.
Sharing involves the selected content, space membership, invitations, and recipients' email addresses. Support email includes the information you send us.
Device storage and cloud sync
The app stores content on your device. Signing in alone does not upload an existing guest library. Enabling cloud sync uploads supported memories, collections, and attached photos so they can be available across your signed-in devices.
Profile changes, including your photo and personal-context choices, sync separately when you save them. Offline profile changes retry while the app is open. Sharing selected content also uploads it separately from your personal-library sync choice. Local reminders are not included in personal-library sync.
Turning off sync does not erase content already uploaded. Signing out is not deletion: a cached account library may remain on the device for use when that account signs in again.
Using Cue
Cue sends your question and recent conversation through our service to OpenAI to generate a response. An explicitly attached memory includes its title and note.
Before using private-memory search, we ask permission to send your chat and up to five matching excerpts, their titles, and memory identifiers. Search uses private titles and notes in your signed-in account's library on this device. It does not search shared spaces or send attached photos or separate location, tag, and reflection fields. Personal information written in a title or note may be included in an excerpt. This is not a background upload of your entire library.
Permission is remembered for your account on that device. You can revoke it in Account Settings, which clears the current conversation and stops automatic memory use until you allow it again. Starting a new chat, signing out, or quitting clears the conversation but does not revoke permission. Revocation cannot recall a request already sent.
The app does not currently save a cloud archive of Cue conversations. We disable OpenAI's response-storage option and optional training-data sharing in the Get Context organization. This does not mean zero retention. OpenAI describes default abuse-monitoring retention of up to 30 days, with exceptions for legal obligations and protection from harm. See OpenAI's API data controls.
Sharing and service providers
Members of a shared space can access content shared there. New shares from the native app create independent copies: editing or deleting your personal original does not automatically change those copies. Older shares from the earlier website may link to an original memory, so changes to that original can affect what members see. Recipients may keep copies outside the app that we cannot remotely erase.
We use Supabase for authentication, the cloud database, and file storage; OpenAI for Cue; Resend for account and invitation email; Google Workspace for support email; and Apple for TestFlight distribution. These services handle information needed for their functions. Our Supabase project is hosted in Canada; processing by our providers is not restricted to the United States or that database region.
During this beta, Get Context does not display advertising, sell personal information, or track users across other companies' apps and websites for advertising. This does not prevent the provider processing and user-directed sharing described here.
TestFlight feedback
Apple collects TestFlight crash and usage information and shares information with developers, including device and operating-system details, installs, sessions, and crashes. Tester information can include your invitation email address. Submitted feedback can include comments and screenshots. Avoid including private memories or other people's information unnecessarily. See Apple's TestFlight privacy notice.
We use beta diagnostics and feedback only to investigate problems and improve Get Context. Downloaded feedback is covered by the cleanup process below; Apple-held records have separate retention.
Retention and deletion
Account information and cloud content are not automatically erased because an account becomes inactive.
Deleting a memory propagates when cloud sync runs. Deleted cloud memories become eligible for permanent cleanup after 30 days. Replaced memory and profile photos become eligible after 30 days unless still referenced by another memory or profile. Existing unused photos with an unknown replacement date receive a 30-day grace period from discovery. Cleanup uses batches and retries, so removal is not guaranteed at an exact instant.
Unaccepted invitations expire after 30 days. Their records and associated delivery records are scheduled for removal within the following 30 days. This does not remove an already accepted membership.
Accepted invitations and their associated delivery records become eligible for permanent cleanup 90 days after acceptance. An hourly job removes eligible records in batches; outages or backlogs can delay completion. This removes invitation history, not shared-space memberships or shared content. For any older accepted invitation without a recorded acceptance date, the 90-day period starts when that missing date is identified during the cleanup rollout.
You can request account deletion in the app. You must first delete spaces you own so their impact on other members is explicit. Completed account deletion removes active account cloud records and photos and this device's account cache. It does not remotely erase guest libraries, exported files, other-device offline caches, or copies held by recipients.
A limited recovery receipt helps confirm deletion after an interrupted connection. It contains an account identifier, hashed random proof, and timestamps. Recovery expires seven days after completion; expired receipts are scheduled for removal within 30 days of expiry and may be removed sooner. Temporary photo-cleanup records remain until cleanup is confirmed.
Operator-managed account removal also keeps limited records to carry out and verify the removal: account and request identifiers, a case reference, a confirmation fingerprint, processing status, timestamps, and file paths needed for cleanup. Unfinished records remain while removal is being resolved. Completed records become eligible for cleanup after seven days; cleanup currently occurs in batches when a later operator removal begins, so this is not a guaranteed seven-day deletion deadline. Support correspondence follows the separate support-record schedule below.
Resolved support conversations and downloaded beta feedback become due for deletion 90 days after resolution. We review them monthly and remove due items during that review, rather than automatically on day 90. Provider backups, recovery systems, and logs are separate from active records and may retain information after active copies are removed. We do not promise immediate deletion from every provider system.
Your choices and requests
You choose what to import, sync, share, and send to Cue. The current app does not automatically upload your full photo library or address book. Places you enter can be stored in your memories. Local reminders require notification permission, which you can change in device settings.
For privacy requests, email hello@getcontext.studio. We verify account ownership before account changes and may ask you to confirm a request through your registered email or authenticated app controls. Do not send passwords, authentication codes, or API keys.
The app's Export my memories option saves a file containing your personal memories and attached photos. It does not include your profile or shared spaces, and the exported file is not encrypted. Choose a private destination. Contact us for requests involving information outside that export; it is not a complete export of all account information.
Security and age eligibility
We use HTTPS for service requests and the device Keychain for authentication credentials. No storage or transmission method is completely secure; we do not promise end-to-end encryption.
This beta is not offered to anyone under 18. Report suspected underage accounts to hello@getcontext.studio. We will investigate reports and arrange controlled removal of confirmed ineligible accounts, addressing shared-space impact. An allegation alone is not grounds for immediate deletion.
Policy changes
We will notify users by email of material changes to this policy.
Context
Home
YOUR INFORMATION. YOUR CHOICES.
Privacy policy
Get Context app and supporting services.
Last updated October 6, 2026
About Get Context
Get Context helps you save memories, organize collections, share selected content, and ask Cue questions. Michael Griffin operates Get Context. This policy covers the app and its supporting services, not the separate marketing website.
Contact hello@getcontext.studio with privacy questions or requests. The first invitation-only beta is intended for adults age 18 or older in the United States.
Information you provide
We process your email address, account identifier, and authentication information to provide account access and recovery.
Content you save may include titles, notes, photos, links, tags, places, addresses, plans, dates, reflections, and collections. Content you enter about other people may also be included.
Your optional profile information may include your name, photo, birthday, home city, interests, goals, people you spend time with, barriers to activities, weekend preferences, reconnection preferences, and preferred travel distance. We use profile information to save your choices and personalize supported app experiences.
Sharing involves the selected content, space membership, invitations, and recipients' email addresses. Support email includes the information you send us.
Device storage and cloud sync
The app stores content on your device. Signing in alone does not upload an existing guest library. Enabling cloud sync uploads supported memories, collections, and attached photos so they can be available across your signed-in devices.
Profile changes, including your photo and personal-context choices, sync separately when you save them. Offline profile changes retry while the app is open. Sharing selected content also uploads it separately from your personal-library sync choice. Local reminders are not included in personal-library sync.
Turning off sync does not erase content already uploaded. Signing out is not deletion: a cached account library may remain on the device for use when that account signs in again.
Using Cue
Cue sends your question and recent conversation through our service to OpenAI to generate a response. An explicitly attached memory includes its title and note.
Before using private-memory search, we ask permission to send your chat and up to five matching excerpts, their titles, and memory identifiers. Search uses private titles and notes in your signed-in account's library on this device. It does not search shared spaces or send attached photos or separate location, tag, and reflection fields. Personal information written in a title or note may be included in an excerpt. This is not a background upload of your entire library.
Permission is remembered for your account on that device. You can revoke it in Account Settings, which clears the current conversation and stops automatic memory use until you allow it again. Starting a new chat, signing out, or quitting clears the conversation but does not revoke permission. Revocation cannot recall a request already sent.
The app does not currently save a cloud archive of Cue conversations. We disable OpenAI's response-storage option and optional training-data sharing in the Get Context organization. This does not mean zero retention. OpenAI describes default abuse-monitoring retention of up to 30 days, with exceptions for legal obligations and protection from harm. See OpenAI's API data controls.
Sharing and service providers
Members of a shared space can access content shared there. New shares from the native app create independent copies: editing or deleting your personal original does not automatically change those copies. Older shares from the earlier website may link to an original memory, so changes to that original can affect what members see. Recipients may keep copies outside the app that we cannot remotely erase.
We use Supabase for authentication, the cloud database, and file storage; OpenAI for Cue; Resend for account and invitation email; Google Workspace for support email; and Apple for TestFlight distribution. These services handle information needed for their functions. Our Supabase project is hosted in Canada; processing by our providers is not restricted to the United States or that database region.
During this beta, Get Context does not display advertising, sell personal information, or track users across other companies' apps and websites for advertising. This does not prevent the provider processing and user-directed sharing described here.
TestFlight feedback
Apple collects TestFlight crash and usage information and shares information with developers, including device and operating-system details, installs, sessions, and crashes. Tester information can include your invitation email address. Submitted feedback can include comments and screenshots. Avoid including private memories or other people's information unnecessarily. See Apple's TestFlight privacy notice.
We use beta diagnostics and feedback only to investigate problems and improve Get Context. Downloaded feedback is covered by the cleanup process below; Apple-held records have separate retention.
Retention and deletion
Account information and cloud content are not automatically erased because an account becomes inactive.
Deleting a memory propagates when cloud sync runs. Deleted cloud memories become eligible for permanent cleanup after 30 days. Replaced memory and profile photos become eligible after 30 days unless still referenced by another memory or profile. Existing unused photos with an unknown replacement date receive a 30-day grace period from discovery. Cleanup uses batches and retries, so removal is not guaranteed at an exact instant.
Unaccepted invitations expire after 30 days. Their records and associated delivery records are scheduled for removal within the following 30 days. This does not remove an already accepted membership.
Accepted invitations and their associated delivery records become eligible for permanent cleanup 90 days after acceptance. An hourly job removes eligible records in batches; outages or backlogs can delay completion. This removes invitation history, not shared-space memberships or shared content. For any older accepted invitation without a recorded acceptance date, the 90-day period starts when that missing date is identified during the cleanup rollout.
You can request account deletion in the app. You must first delete spaces you own so their impact on other members is explicit. Completed account deletion removes active account cloud records and photos and this device's account cache. It does not remotely erase guest libraries, exported files, other-device offline caches, or copies held by recipients.
A limited recovery receipt helps confirm deletion after an interrupted connection. It contains an account identifier, hashed random proof, and timestamps. Recovery expires seven days after completion; expired receipts are scheduled for removal within 30 days of expiry and may be removed sooner. Temporary photo-cleanup records remain until cleanup is confirmed.
Operator-managed account removal also keeps limited records to carry out and verify the removal: account and request identifiers, a case reference, a confirmation fingerprint, processing status, timestamps, and file paths needed for cleanup. Unfinished records remain while removal is being resolved. Completed records become eligible for cleanup after seven days; cleanup currently occurs in batches when a later operator removal begins, so this is not a guaranteed seven-day deletion deadline. Support correspondence follows the separate support-record schedule below.
Resolved support conversations and downloaded beta feedback become due for deletion 90 days after resolution. We review them monthly and remove due items during that review, rather than automatically on day 90. Provider backups, recovery systems, and logs are separate from active records and may retain information after active copies are removed. We do not promise immediate deletion from every provider system.
Your choices and requests
You choose what to import, sync, share, and send to Cue. The current app does not automatically upload your full photo library or address book. Places you enter can be stored in your memories. Local reminders require notification permission, which you can change in device settings.
For privacy requests, email hello@getcontext.studio. We verify account ownership before account changes and may ask you to confirm a request through your registered email or authenticated app controls. Do not send passwords, authentication codes, or API keys.
The app's Export my memories option saves a file containing your personal memories and attached photos. It does not include your profile or shared spaces, and the exported file is not encrypted. Choose a private destination. Contact us for requests involving information outside that export; it is not a complete export of all account information.
Security and age eligibility
We use HTTPS for service requests and the device Keychain for authentication credentials. No storage or transmission method is completely secure; we do not promise end-to-end encryption.
This beta is not offered to anyone under 18. Report suspected underage accounts to hello@getcontext.studio. We will investigate reports and arrange controlled removal of confirmed ineligible accounts, addressing shared-space impact. An allegation alone is not grounds for immediate deletion.
Policy changes
We will notify users by email of material changes to this policy.
Context
A little more context for your life.
© 2026 Context