Privacy
Last updated 2026-10-22
Present Agent, including Present Gift Context, is owned and operated by Ensemble Ventures Inc. For support, contact support@presentagent.vip.
Present (“we”) is a private gift-memory product at context.presentagent.vip. This page explains what we store, what we do not store, and the controls you have.
What we collect
- Account. Email address and auth identity from our sign-in provider (Clerk).
- People & occasions you add. Names, relationships, notes, dates, budgets, gift history, shortlists, and review decisions (candidate / confirmed / dismissed).
- Optional Google connection. If you connect Google, we store an encrypted OAuth token on our servers and import only the signals described on the Google data page. Imports land as reviewable candidates — not automatic facts.
- Operational logs. Standard request logs, reminder delivery status codes, and audit events inside your account (for example privacy export or delete).
- Beta waitlist. We store your email and signup source to send confirmation and invitation emails. If you complete the beta application, we also store your first name, ChatGPT usage, workspace type, occasion timing, and consent, to help Gui select and support cohorts. You can also choose to tell us your main goal, whether you organize personal or business gifts, your business name, and how you heard about Present, so we can understand which needs and discovery sources lead to useful experiences. Unconfirmed applications expire after 7 days. Confirmed applications not selected for a cohort expire after 90 days. Reply to an email or write support@presentagent.vip to leave the list. This does not delete a separate Present account.
What we do not do
- We do not sell your data.
- We do not scan Gmail in the background or store raw messages. Optional read-only Gmail access runs only when you request clues for a saved person; its profile, time, message-count, content, and retention boundaries are described on the Google data page.
- We do not use your people data to train public models. When Gemini is enabled, optional note extraction and gift-idea requests send the profile context needed for that request to Google Gemini. Selected-person Gmail processing has tighter limits described on the Google data page.
- We do not run a product catalog, checkout, or Shopify integration in this product.
Chat with Present
In-app chat stores your messages, attachment filenames, extracted text or transcripts, replies, and proposed memories privately in your account. Google Gemini processes the content you send, recent turns in that conversation, a bounded recipient name roster, and relevant confirmed profile context to answer you. Chat does not connect to or search Google sources on your behalf.
Screenshots and audio are processed transiently; Present does not store the original files. Recording begins only when you press Record voice and allow microphone access. You can listen and remove a recording before sending. Transcription can make mistakes, so check names and dates. Extracted memories remain proposals until you choose to review them; AI-extracted details enter the existing candidate review flow.
Conversation history is included in your account download and removed by account data deletion. You can also delete an individual conversation; separate memory reviews and saved profile information remain until you remove those separately. No phone calls are placed by this chat feature.
ChatGPT beta connection
The current read-only beta retrieves confirmed context you saved in Present. It does not save profile changes or submit feedback from ChatGPT. The proposal and automatic-draft features described below apply only to connections where those capabilities are separately enabled; they are not available through the read-only beta connection. Save changes and answer optional beta questions in Present instead.
If you connect Present to ChatGPT, Clerk asks you to authorize the connection. Present receives only the minimum structured arguments in a Present tool call. We do not receive your ChatGPT password, full chat history, other conversations, hidden model reasoning, or data from other connectors. A supported minimum structured fact reaches Present only when you explicitly ask to save it, or when you separately enable automatic context drafts for clearly stated, non-sensitive relationship, preference, occasion, budget, gift-memory, or shortlist details about an existing recipient. Automatic drafts exclude conversation excerpts, inferred facts, birth years, sensitive information, purchases, and outcomes.
Confirmed recipient context returned by Present becomes available to the active ChatGPT workflow that called the tool. Returned details may remain in your ChatGPT conversation after you disconnect Present or delete data in Present; manage that conversation separately in ChatGPT. Ordinary conversation is not saved to Present. Durable updates are proposal-only: they do not change a recipient profile until you open the returned Present review page and approve the exact diff while signed in.
We retain privacy-minimized raw tool telemetry for at most 30 days: tool name, result class, latency, endpoint version, proposal/read class, and keyed pseudonymous account, client, session, and request references. Raw prompts, recipient content, tool arguments and results, email addresses, OAuth tokens, and authorization codes are excluded. Per-minute abuse counters contain only a keyed pseudonym and expire after two days. The protected reliability monitor returns only aggregate counts, rates, latency, and fixed reason codes. Alert emails contain only the UTC hour and fixed reason codes.
When ChatGPT supplies an anonymized conversation identifier with a tool call, Present converts it immediately into an account-bound keyed pseudonym so calls in one conversation can be evaluated together. The original identifier is not stored. Conversation evaluations contain only fixed tags, bounded numeric scores, tool-result counts, evidence references, and fixed outcome categories; they do not contain prompts, transcripts, recipient details, product text, URLs, or free-form feedback. These rows expire after 30 days and are removed on account deletion. Tool activity alone is not treated as evidence that a gift decision was useful or successful.
Present also records a closed set of privacy-minimized product milestones such as account creation, connection completion, first useful read, context confirmation, share opening or acceptance, and structured beta feedback. Raw product-learning events expire after 30 days. A compact keyed-pseudonymous milestone row—dates and milestone categories only—is retained for at most 400 days so we can measure episodic 30, 60, and 90-day return without retaining prompts or recipient content. It never contains names, profile facts, gift ideas, free-text feedback, OAuth credentials, capability tokens, or complete URLs. Account deletion removes account-linked raw telemetry and the milestone row.
Linking beta participation connects the invited, verified Present account to the application and cohort. Operators can record delivery and setup evidence, assistance, support time, blockers and next actions. Customer reporting excludes records classified as staff, smoke tests or unknown. Leaving the beta suppresses future beta outreach and blocks the linked account at Present's managed ChatGPT OAuth endpoint. We retain a hashed account reference and withdrawal time separately from the application to prevent its removal from restoring access. This is a pseudonymous access-suppression record, not anonymous data. Provider grant revocation and research held elsewhere need separate cleanup.
The beta check-in also offers optional short research feedback, with a separate agreement before it is stored. These summaries and their consent evidence are restricted to beta operators, not placed in operational telemetry. Research retention is reviewed at cohort closeout; contact support to withdraw consent or request removal. Product account deletion and research removal are separate requests.
In-product beta questions are optional and use fixed answer choices. Verbatim research feedback and conversation transcripts are not placed in operational telemetry. If we conduct qualitative conversation review, it is collected separately with explicit consent and only the fixed, content-free evaluation may enter the operational learning system. Share, feedback, and individually attributed invitation URLs are excluded from browser analytics.
Where data lives
Production data is stored in a private Postgres database (Neon) scoped by account. Connector tokens are encrypted at rest with a server-side key. Email reminders are sent through Resend from reminders@send.presentagent.vip only when you have opted into Planning assistant and an occasion is inside your reminder window.
Your controls
- Recipient-owned sharing. Your self profile can create an optional link containing only the profile shown on that page. Gifters must accept the first import and every update. Revocation stops future access but cannot erase information someone already accepted. Feedback links expose only the listed preferences and keep corrections pending for gifter review.
- Agent permissions. Recommendations only is the default. Account → Agent permissions lets you opt into or out of planning workflows at any time. This setting is separate from connected-source permissions.
- Download. Account → Download my data exports your archive, including privacy-minimized email delivery events still inside their retention window.
- Delete. Account → delete removes your people, occasions, evidence, gifts, shortlists, audit trail, connector tokens, and account-linked email delivery events, raw product/tool events, and pseudonymous product milestone row. An anonymous aggregate count of deletion requests may remain.
- Disconnect Google. Account → disconnect revokes the stored grant on our side; you can also revoke access in your Google account settings.
- Disconnect ChatGPT. Remove Present from ChatGPT's plugin or connector settings. If its provider grant remains, contact support to revoke that provider grant. Present's bearer-token controls do not revoke ChatGPT's OAuth access. Some older connections use access tokens that remain valid until expiry even after the provider grant is revoked; contact support if access appears to continue.
- Review queue. Imported suggestions stay candidates until you confirm or dismiss them. Only confirmed facts leave via the demand-context export.
Retention
We keep your data while your account exists. Deleted accounts are removed from the application database. Backups and provider logs may retain residual copies for a limited operational window.
Raw Gmail messages and excerpts are processed transiently and are not retained. Short gift-related candidates derived from Gmail remain until you dismiss them, delete the related person, or delete your account.
Resend delivery webhooks are retained for at most 30 days using only event type, timestamps, provider identifiers, and a one-way hash of the recipient address. Subjects, recipient addresses, and raw webhook payloads are not stored.
Google Limited Use
Present's use and transfer of information received from Google Workspace APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use raw or derived Workspace data to train or improve a generalized AI or machine-learning model.
Contact
Questions: support or support@presentagent.vip.