eInvolvePrivacy Policy

We process personal data to run workspaces (entities), listings, search, checkout, payouts, chat, the eInvolve calendar, and safety features. We collect what those features need and do not sell your personal information.

• This policy covers visitors, customers, and providers, including people who use a workspace you invite (roles such as Operator or Producer).
• When you buy from a provider, that provider also sees order, booking, and contact details needed to fulfill. Their own practices apply to how they use that information.
• Material changes are posted on this page with a new “Last updated” date. Capitalized terms follow the Terms of Service unless we say otherwise.
• You can export your data or request account deletion in Settings → Privacy, and you can contact support as described at the end of this policy.

We collect what you submit, what the product generates when you use it, and limited technical data.

• Account: email, name, language, profile, and workspace (entity) settings. Sign-in is email one-time codes and, if you choose it, Google sign-in (identity only — that is not Google Calendar access).
• Commerce: carts, orders, item options you select, addresses, confirmation or QR codes, discounts, affiliate click attribution, refunds, and related status history.
• Payments: Stripe processes cards, Pix, and payouts. We store Stripe identifiers, amounts, and status. We do not store full card numbers on eInvolve servers.
• Communications: in-app chat (including files you attach), ratings, notifications, and support tickets. If you connect WhatsApp Business in Settings, we process messages on that connection.
• Scheduling: availability rules and events on the eInvolve calendar. Google Calendar data only if you connect it in Settings → Integrations (see section 4).
• Location: search and maps (for example radius around an address). In-person Counter (comanda) may, if the venue turns it on, briefly use device location to confirm you are on site; you can still order through staff if GPS is denied.
• Recruitment: job applications, messages, and résumé files you upload when you apply. Partner providers may run optional AI analysis on that eInvolve content (see section 5).
• Technical: IP address, browser and device data, security logs, and cookies needed for sessions and checkout.

We use personal data to provide the product, meet legal duties, and keep the marketplace safe.

• Operate search, listings, checkout, fulfillment, chat, the internal calendar, library (folders, notes, files), and account or role management.
• Charge and pay out through Stripe Connect: a 5% eInvolve platform fee on marketplace sales, optional Partner billing, and Stripe’s own processing fees.
• Send service messages: order and booking updates, security alerts, and support replies. We do not use Google Calendar data for advertising.
• Detect fraud, abuse, and policy violations — including automated content checks on listings and posts you publish on eInvolve.
• Improve the product with aggregated usage. We do not sell personal data.

Google Calendar is optional. We request Calendar access only after a provider connects it in Settings → Integrations. Sign-in with Google is a separate flow and does not grant Calendar scopes.

• Purpose: two-way sync between the eInvolve calendar and the Google calendar you pick. Bookings created or updated in eInvolve can appear on Google Calendar; relevant Google events can update availability in eInvolve.
• Access: we list calendars you subscribe to so you can choose one (`calendar.calendarlist.readonly`), then read and write events on that calendar (`calendar.events`). We do not change sharing, create or delete calendars, or use Google user data for ads or resale.
• Storage: OAuth tokens and the event fields needed to keep that sync working.
• Disconnect in Settings → Integrations, or revoke access in your Google Account. Search, chat, checkout, and in-app scheduling work without Google Calendar.
• The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.
• We do not use Google Calendar or other Workspace or Photos user data to create, train, or improve AI or machine-learning models. We do not transfer that data to third-party AI services, in raw, aggregated, or derived form.
• Write path: events are created on the eInvolve calendar first. A server trigger then syncs them to Google Calendar when you have connected it. AI and bots do not call Google Calendar APIs and do not receive your Google Calendar feed or tokens.
• Messaging bots in chat or WhatsApp that could create bookings are planned and not live. If shipped, they would still only write the eInvolve calendar; Google sync would remain that same trigger.

Optional AI tools run on content that already exists in eInvolve. They do not receive Google Calendar, Gmail, Drive, or Photos API data.

• Live today (where your plan allows): item photo improve and job-application analysis for Partner; an in-app assistant with instructions you set; search over the public /info help pages; automated moderation of content you post on eInvolve.
• Partner quotas (when Partner is active): curriculum analysis is metered per monthly amount, as shown in Settings. Curriculum analysis is for the employer (provider), not the candidate.
• We send only the eInvolve payload needed for that feature (for example chat text, item text, or help-center copy) to third-party AI APIs (currently OpenAI, xAI Grok, and Google Gemini). None of those calls include Workspace or Photos API data.
• Image improve (`/ai/images/generate` and `/ai/images/improve`) is not enabled in this build. The endpoint is reserved; when it returns, it will process item photos uploaded to eInvolve only.
• Planned: chat and WhatsApp bots that use AI to talk with customers. Booking, if agreed, would be written on the eInvolve calendar, then synced to Google Calendar only through the trigger in section 4. That bot flow is not implemented yet.
• You can disconnect Google Calendar and change AI instructions (including whether AI-created eInvolve events should sync out) independently in Settings.

Your library can hold ordinary notes and secret notes. Secret notes are encrypted in your browser before they reach our servers.

• For secret notes we store ciphertext and metadata only. We cannot read the title, body, or attached files. Keys are handled in the app and a separate key vault; the main eInvolve API does not hold plaintext.
• If you lose access to your account keys, we cannot recover secret-note contents. Sharing a secret note delivers keys to recipients you choose; you can revoke access.
• Ordinary (non-secret) notes, folders, purchased files, and catalog saves are stored so we can show them in your library and fulfill orders.
• Linked storage counts toward your workspace quota (baseline plus Partner bonus while Partner is active), as shown in the product.

We share data to run the product, when you ask us to, or when the law requires it. We do not sell personal information.

• The other party to a transaction or chat: order, booking, and contact details needed to complete the work or resolve a dispute.
• Processors: Stripe (payments and Connect payouts); Google (sign-in if you use it, Calendar APIs only if you connect Calendar); maps; email delivery; hosting and file storage; WhatsApp if you connect it; third-party AI APIs (OpenAI, xAI Grok, Google Gemini) only for eInvolve content as in section 5.
• Affiliates you work with: commission and attribution data on referred orders. The 5% platform fee is unchanged.
• Legal and safety: lawful requests, fraud, or to protect users and eInvolve. Business transfers (merger or sale) keep this policy’s protections as far as the law allows.

We use cookies and similar storage to keep you signed in, remember preferences, and secure checkout.

• Essential cookies cover authentication, session, workspace selection, and checkout security.
• Preference cookies may store language and interface choices.
• Blocking essential cookies will stop sign-in or checkout from working.
• Platform ads are not live. We do not use third-party advertising cookies on the core marketplace today; if that changes, we will update this section.

We use technical and organizational measures meant to protect personal data, including HTTPS, access control, and role permissions inside a workspace.

• Staff and systems that touch production data are limited by role.
• Payment cards stay with Stripe. Secret notes stay encrypted on the client as described in section 6.
• No transmission or storage is perfectly secure. Use a unique password and protect your email inbox (it receives sign-in codes).
• You are responsible for who you add as Operator, Producer, or other roles in your workspace.

We keep data while your account is active and as long as needed for the purposes in this policy or the law.

• Orders, payouts, and tax-relevant records may be kept after you leave, for accounting, chargebacks, and legal holds.
• Chat that you persist stays with the thread. Non-persisted chat files are dropped on a short retention window (currently three months) as described in-product.
• Google Calendar tokens are kept only while the connection is active; we stop using them when you disconnect.
• Account deletion can be scheduled in Settings → Privacy. Secret-note ciphertext is deleted with the note; we still cannot reconstruct plaintext we never had. Some records we must keep for disputes or law.

Depending on where you live, you may access, correct, delete, or restrict certain processing.

• Use profile, integrations, and Settings → Privacy (export and deletion request) where the product offers them.
• Contact support with subject “Privacy request” and the email on the account. We may need to verify it is you.
• Disconnect Google Calendar, WhatsApp, and AI tools in Settings without deleting the whole account.
• EEA, UK, and similar regions may have extra rights (objection, portability, complaint to a supervisory authority).

We may revise this policy when the product, the law, or our processors change.

• The date at the top is when this page last changed.
• Continued use after a change means you accept the update, unless the law requires another step.
• For material changes we may also email or show an in-product notice.

Privacy questions, export help, and deletion requests go through support.

• Use Contact Support on eInvolve with subject “Privacy request”.
• Include the email on the account so we can verify ownership.
• We aim to respond within the time the applicable law requires.