Effective date: 26 May 2026 · Last updated: 4 October 2026 · Version 2.4
This Privacy Policy explains how BrinGET.ai ("we", "us", the "app") collects, uses, shares, and protects your personal data when you use our web app, iOS app, or Android app. It also describes the rights you have over your data under the EU General Data Protection Regulation (GDPR), the UK GDPR, and similar laws (CCPA/CPRA in California, PIPEDA in Canada, the Australian Privacy Act).
The data controller for BrinGET.ai is Extradock LLC (an Ohio limited liability company), doing business as BrinGET.ai ("BrinGET.ai", "we", "us"). You can reach us at:
If you are in the EU/EEA and would like an EU representative under GDPR Art. 27, please email dpo@bringet.ai and we will provide one.
Under GDPR Art. 6, every kind of personal data we process must have a lawful basis. Here's a category-by-category breakdown.
| Category | What's in it | Why we need it | Legal basis (GDPR Art. 6) |
|---|---|---|---|
| Account data | Email address (required), display name, optional phone number, password hash, avatar color. | Authenticate you and let you sign in across devices. | Contract (6(1)(b)) |
| Content you create | Lists, list items, contacts, activity events, todos, list memberships. | Provide the core service: store, sync, and share your lists. | Contract (6(1)(b)) |
| AI personalization context | Free-text fields you choose to fill in under Settings → Personalize the AI: "About you", "Location", "Always avoid", and "Anything else." You can put as much or as little as you like. | Tailor the AI's list suggestions to your actual life. | Consent (6(1)(a)) — you choose what to enter; you can clear it any time. If you write things that reveal religious belief, health, or other special-category data under GDPR Art. 9, we process them under Art. 9(2)(a) explicit consent. |
| AI prompts and responses | The full text of prompts you send the in-app AI assistant and the responses it returns. Stored as ai_prompt_logs. |
Improve the model, build aggregated insight products (e.g. "most-requested party items by region"), and debug bad outputs. | Consent (6(1)(a)) — controlled by the toggle in Settings → Data & privacy. Off = we don't write these rows. |
| Behavioral analytics | Events like app.open, list.create, item.add, AI turn counts, button clicks. Stored as analytics_events. Includes a session id, browser/device platform, truncated IP prefix (never the full IP), referer. |
Understand which features are used, fix bugs, build product roadmaps, build aggregated insight products. | Consent (6(1)(a)) — same toggle as above. |
| Affiliate link activity | When you tap a shopping link we tag for affiliate commission, we may record the click: the merchant (e.g. Amazon), the list/item it came from, the destination URL, and your user id. Stored as affiliate_link_events. |
Measure which retailers and links are useful, attribute affiliate commissions, and improve the shopping experience. | Consent (6(1)(a)) — controlled by the same "Help improve BrinGET.ai" toggle in Settings → Data & privacy. Off = we don't write these rows. |
| Quote requests | When you tap "Get quotes" on an event list you own and then tap "Send request": event type, the specific occasion if one is selected (optional — for example a bat mitzvah or a christening; see §4.2), event date (optional), the city or region you typed, guest count (optional), the vendor categories you ticked (florist, bakery, catering, …), free-text notes (optional), a contact email (prefilled from your profile, editable), and a contact name (optional). Stored as quote_requests together with the list it was sent from, the exact payload that was shared, the consent version (quotes-v2; quotes-v1 for requests sent before the occasion field existed) and timestamp, the request's status, and a short note from our team. List items, list members, contacts, and anything else on the list are never part of a request. |
Pass your request to a small number of vendors that serve your area so they can reply with a quote (see §4.2). | Consent (6(1)(a)) — given per request when you tap "Send request"; nothing is sent otherwise. Contact us to withdraw a request (§4.2). |
| Operational logs | Anthropic and OpenAI token counts and cost per AI call (no prompt content), email send/failure events, push fan-out totals, admin audit log entries. | Bill us for our own infrastructure, detect abuse, debug, comply with auditing duties. | Legitimate interest (6(1)(f)) — running a stable, fraud-resistant service. |
| Server logs | Request URL, status code, IP address, user agent, timestamp. | Operate, debug, and secure the service; investigate abuse. | Legitimate interest (6(1)(f)). Retained ≤ 30 days. |
| Device contacts (mobile only) | With your permission, the app reads your device address book (names, phone numbers, emails) on your device only to show a searchable picker; some flows use the OS picker instead, which needs no permission. We store only the contacts you explicitly select or save: name, first email, first phone number. | Pre-fill the in-app "add contact" form and let you assign items to people without retyping. | Consent (6(1)(a)) — the OS permission prompt. Your address book itself is never uploaded to or stored on our servers; only individually selected contacts are. |
| SMS recipients | Phone numbers and message bodies for transactional SMS sent via Twilio. | Notify list members about assignments and urgent rescues. | Legitimate interest (6(1)(f)) for the recipient; the sender represents a basis to message that contact (see ToS). STOP opt-out is honored automatically. |
The personalization fields under Settings → Personalize the AI are free-text. If you choose to write information that reveals special-category data — for example religious beliefs ("we keep kosher"), health information ("nut allergy"), or political views — we process that only on the basis of your explicit consent under Art. 9(2)(a), which you give by typing it in. You can clear any field at any time in Settings → Personalize the AI, and it will be removed from your profile and from future AI prompts.
No advertising trackers. No third-party analytics SDKs (we run our own first-party analytics, described above). No location data beyond a coarse country-level signal derived from your IP address (used to pick a regional shopping roster) and any city or region you type yourself (in the AI personalization fields or a vendor quote request, §4.2). No camera access. No browsing history outside BrinGET.ai.
Some screens offer a microphone button so you can dictate text instead of typing. It is entirely optional and only listens while voice input is active (after you tap the button). Voice input is handled by your platform's own speech recognition, not by us:
BrinGET.ai never records, receives, or stores the audio itself — we only receive the transcribed text, which is placed in the input box for you to review, edit, or delete before sending. If your device or browser does not support voice input, the microphone button does not appear.
Settings → Data & privacy contains a switch labelled "Help improve BrinGET.ai." It controls the consent (Art. 6(1)(a)) basis for three specific things:
analytics_events)ai_prompt_logs)affiliate_link_events)When you toggle it off, we stop writing new rows of either kind for your account, immediately. Existing rows are not deleted by toggling — to remove historical rows as well, use the "Export and delete my data" controls in the same screen, or delete your account.
Toggling it off does not stop the operational logs, server logs, or content storage in section 2 — those are required to keep the service running and don't rely on consent.
To run BrinGET.ai we share data with the following sub-processors. Each is bound by GDPR-compliant Data Processing Agreements and (where data leaves the EU/EEA) the European Commission's Standard Contractual Clauses.
| Sub-processor | Role | Data shared | Region |
|---|---|---|---|
| Supabase | Authentication, database, realtime sync. | Account data, content, analytics_events, ai_prompt_logs, AI usage events. | EU/US (region-selectable per project) |
| Anthropic | Primary AI assistant model (Claude). | Your AI prompts and personalization context (only when you interact with the assistant). Anthropic does not retain prompt content for training under our API agreement. | US |
| OpenAI | Backup/alternate AI assistant model. Used for the in-app AI assistant when configured as the active provider or as automatic failover if the primary provider is unavailable. | Your AI prompts and personalization context (only when you interact with the assistant and a request is served by OpenAI). OpenAI does not retain or train on API content under our API agreement. | US |
| Vercel | Web hosting and serverless functions. | Standard request logs (IP, URL, timestamp). | Global edge network |
| Resend | Transactional email. | Recipient email, sender name, message body. | US |
| Twilio | Transactional SMS (assignment + urgent notifications). | Recipient phone number, message body, invite token. | US |
| Firebase Cloud Messaging (Google) | Android push notifications. | Device token, payload. | US |
| Apple Push Notification service | iOS push notifications. | Device token, payload. | US |
| Capgo | Delivers app updates to the iOS and Android apps (the web part of the app) without an app-store update. | A random installation ID generated by the app (not an advertising or hardware identifier, and not linked to your account), device platform, operating-system, app and update versions, update events (checked, downloaded, installed, rolled back, failed), app health signals (crashes and app errors), and the IP address of the request (used to pick the nearest server and derive the country). No account data, lists, or content. | Global edge network |
| Sentry (optional) | Error monitoring (only if our DSN is set in deployment). | Error stack traces, scrubbed request context. | US/EU |
| Affiliate / retailer networks (Amazon Associates, eBay Partner Network, Walmart, Target, and other retailers in our shopping roster) | Affiliate commission attribution when you click a tagged shopping link. | The click, our publisher/affiliate tag, and standard click metadata sent to the destination retailer or its affiliate network. We do not send your account profile. | US / global (varies by retailer) |
The affiliate / retailer networks above are independent recipients, not our sub-processors: when you choose to open a tagged shopping link, the destination retailer (and its affiliate network) receives the click and our publisher tag so any resulting purchase can be attributed to us. Their handling of your data is governed by their own privacy policies. See §5 below for how this relates to "sale"/"sharing" under California law.
For transfers from the EU/EEA, UK, or Switzerland to the United States, we rely on the EU-US Data Privacy Framework where the recipient is certified, and on Standard Contractual Clauses (SCCs) plus supplementary measures otherwise.
BrinGET.ai exposes a remote
Model Context Protocol (MCP)
connector at /api/mcp. If you choose to connect a third-party
AI assistant (for example Claude.ai, ChatGPT, Perplexity, Cursor, Grok, or
any other MCP-aware client) from Settings → Connectors,
that assistant — and its provider — becomes a recipient of the BrinGET data
needed to fulfill your requests.
Unlike the sub-processors in §4, the providers of the assistants you connect are not our sub-processors. Each provider is an independent controller you've chosen to engage; their handling of your data is governed by their own privacy policy. We make the connection technically possible (OAuth, scopes, RLS-aware tools); the choice to use it and which provider to use is yours.
list_audit alongside in-app actions, with the originating client (OAuth client name or PAT id) attributed.401 invalid_token.You can find each provider's data-handling terms here: Anthropic (Claude.ai), OpenAI (ChatGPT), Perplexity, xAI (Grok), Cursor.
On an event list you own (a bridal shower, a wedding, a birthday, and so on) you can tap "Get quotes" to ask vendors for quotes. The sheet shows exactly what will be shared, and nothing leaves the app until you tap "Send request" — that tap is your consent (Art. 6(1)(a)). There is no automatic or background sharing, no targeting, and no advertising. This consent is separate from the Settings → Data & privacy toggle in §3, which has no effect on quote requests.
quote_requests (see §2 and §6).Because you direct each request yourself, sending one is not a "sale" of your personal information and is not "sharing" for cross-context behavioral advertising under California law — see §5 and §7.1.
We may build and share aggregated, anonymized reports derived from analytics events and AI prompt content (e.g. "the top 50 items on shared birthday-party lists in Q2 2026, by region"). Aggregation is designed so individual users cannot be re-identified: minimum cohort sizes apply, free-text fields are sampled and bucketed, and outputs are reviewed before release.
We do not sell raw personal data, raw prompt text, or row-level event data, and we do not share them with third parties for their own purposes — with one limited exception: when you click a shopping link we have tagged for affiliate commission, the destination retailer or its affiliate network receives that click and our publisher tag for attribution (see §4). Under California's CPRA this transfer for cross-context attribution may be considered "sharing." You can stop it by turning off the Data & privacy toggle (which also disables affiliate-click logging) — see §7.1. If you turn off the toggle, your data is also excluded from any new aggregation going forward.
Vendor quote requests (§4.2) are a different kind of transfer: the vendors receive your request for their own purpose — replying to you with a quote — but only because you directed us to send it by tapping "Send request." A disclosure you direct is not a sale, and it is not "sharing" for cross-context behavioral advertising under the CPRA. The Data & privacy toggle and the "Do Not Sell or Share" control in §7.1 keep working exactly as before and do not need to cover quote requests — you control those by choosing whether to send one, and you can withdraw a sent request by contacting us.
| Data | Retained for |
|---|---|
| Account, profile, content (lists, items, contacts, todos) | While your account is active. Deleted on account deletion. |
| analytics_events | While your account is active, then deleted on account deletion. Aggregated insights derived from them may persist. |
| affiliate_link_events | While your account is active, then deleted on account deletion or when you withdraw the Data & privacy consent. Aggregated/merchant-level totals may persist. |
| quote_requests (vendor quote requests, §4.2) | While your account is active, then deleted on account deletion. Contact us to withdraw a request earlier. A vendor that has already received a request holds its copy under its own privacy policy. |
| ai_prompt_logs | Up to 30 days, then auto-deleted by a daily purge. Also deleted on account deletion or when you withdraw consent. Aggregated insights derived from them may persist. |
| AI usage events (token counts, cost — no prompt content) | Up to 24 months for billing reconciliation, then deleted. |
| Email/SMS/push event records | Up to 24 months, then deleted. |
| Admin audit log | Up to 12 months, then auto-deleted by a daily purge. |
| Admin impersonation sessions (super-admin login-as records, kept for security investigations) | Up to 12 months, then auto-deleted by a daily purge. |
| Server logs (Vercel) | Up to 30 days. |
| Backups | Up to 30 days; deletion requests are reflected in the next backup rotation. |
Wherever you live, you can:
If you are a California resident, you have the right to know, access, correct, and delete your personal information; the right to opt out of "sale" or "sharing" of personal information; and the right not to be discriminated against for exercising these rights. We do not sell your personal information for money; the only transfer that may qualify as "sharing" is the affiliate-click attribution described in §4–§5. Vendor quote requests (§4.2) are disclosures you direct yourself by tapping "Send request"; they are not a sale or "sharing" for cross-context behavioral advertising, so the opt-out below does not affect them — you control them by choosing whether to send one, and you can withdraw a sent request by contacting us. To exercise the opt-out, use "Do Not Sell or Share My Personal Information" under Settings → Data & privacy, which suppresses usage analytics, AI prompt logging, and affiliate-click attribution. We also honor Global Privacy Control (GPC) browser signals as an automatic opt-out: when your browser sends GPC, data collection is turned off without any further action from you (you can still opt back in from the same Settings screen).
BrinGET.ai is not directed to children under 13 (or under 16 in the EU/EEA where local law sets a higher digital-consent age). We do not knowingly collect personal data from children below those ages. If you believe a child has created an account, contact us and we will delete it.
Data in transit is encrypted with TLS. Account data at rest is protected by Supabase's encryption-at-rest controls and database-level row-level security. Admin actions are logged and gated by role. Passwords are hashed by Supabase Auth; we never see your plaintext password. No system is perfectly secure — if we become aware of a breach affecting your personal data, we will notify you and the relevant supervisory authority within 72 hours, as required by GDPR Art. 33–34.
If we change this policy in a material way, we'll update the "Effective date" above, increment the version, and notify signed-in users in-app or by email. Non-material edits (typos, clarifications) may be made without notice; we'll always preserve the previous version on request.
Privacy questions or requests: privacy@bringet.ai
Data Protection Officer: dpo@bringet.ai
Security disclosures: security@bringet.ai