Privacy Policy

Who operates the service

The operator and data controller is NEXTED GROUP SOCIEDAD LIMITADA, NIF B56576259, VAT ESB56576259, Calle Gregal, 8, 46117 Bétera, Valencia, Spain. Contact service@nextmba.com for support or privacy requests, or telephone +34 667 939 082.

Google user data: purpose and restrictions

We use Gmail and Google Calendar data only to provide the user-facing features you enable: displaying messages, preparing and revising replies, sending replies you explicitly approve, and providing your requested summaries, plans and reminders. Saved drafts, summaries and other content derived from this data are subject to the same restrictions.

We do not use or share this data for advertising, retargeting, marketing campaigns, data enrichment, sale to data brokers or information resellers, creditworthiness or lending decisions, or building datasets for unrelated purposes. These restrictions also apply to our service providers.

We do not use Google Workspace APIs or data obtained through them to develop, improve, or train non-personalized AI or machine learning models. We do not use this data to train or fine-tune general-purpose models, and we do not permit our AI providers to do so. Sharing relevant email or calendar content with OpenAI is limited to generating the assistance described below after your AI permission; it does not authorize model training.

Account and assistant information

We process your account identifier, email address, display name and authentication session to provide your account. We store conversations, memories, uploaded files, preferences, learning progress and schedules when you use those features. Membership and transaction references are used to provide paid access; payment details are processed by the payment provider shown at checkout.

Microphone audio is processed when you choose a voice feature. Relevant conversation context, files and images may be processed to provide the help you request. AI Mail uses your connected Gmail account to display real unread messages, prepare replies and send the displayed reply when you explicitly instruct it to do so.

What Gmail access allows

Gmail is optional and requires separate Google authorization. With your permission, the email assistant uses gmail.readonly to read recent inbox messages, including sender and recipient details, subject, message text and thread identifiers, so it can display messages and help prepare replies. AI Mail loads unread personal correspondence in batches, filters service mail, and checks for new messages while Workplace is open and visible. During a voice review, it can read the latest eight messages in the selected Gmail conversation, including earlier sent and received messages, to understand the sender and prior discussion. It uses gmail.send to send the displayed reply after your explicit voice command or after you confirm Review & send.

It does not use these permissions to delete, move or mark your messages as read. Connecting Gmail does not give us your Google password. For direct Google connections, we store the connected Gmail address, granted scopes, connection timestamps and encrypted access and refresh tokens. AI Mail uses the connection provider described below.

For drafts, we store reply text and the message metadata needed to show and send the reply, including sender, recipient, subject and thread identifiers. Drafts are saved in Workplace under your account and connected mailbox, rather than in Gmail Drafts. Original message text is fetched as needed; relevant excerpts can appear in saved drafts or conversations. Disconnecting Gmail removes its connection credentials, but does not by itself delete existing drafts or conversations.

Optional Calendar access

If you separately enable a Calendar feature and grant calendar.readonly, the assistant reads upcoming events to help prepare plans and reminders. It cannot create, change or delete events with this permission. Event information used in a delivered plan or reminder may remain in your conversation history. Calendar permission is not required just to read and reply to Gmail.

Gmail connection provider

AI Mail connects each user’s own Gmail through Composio’s managed Google connection. It requires separate consent in AI Mail and on Google’s authorization screen, which identifies Composio and lists the requested permissions. Composio stores the Google connection credentials and processes Gmail requests and message content to provide this connection. Your account is bound to your own connected Gmail; it does not share another user’s mailbox. We store an encrypted application project key, individual connection identifiers, connected address, consent time and usage counts.

Unread personal correspondence is loaded in batches. While Workplace is open and visible, we check periodically for new mail and show an indicator or notification. A small cache of message identifiers, senders, subjects and timestamps avoids repeatedly loading the same metadata. This cache is replaced as mail changes and removed when you disconnect or delete your account. Background arrival checks do not prepare AI replies. AI drafting begins when you open AI Mail and grant the separate AI permission.

Use Disconnect Gmail in AI Mail to request revocation and removal of your connected account from Composio. If revocation fails, local access is disabled and the connection information needed to retry is retained. Existing drafts remain under your account and are subject to account deletion. Provider retention is governed by Composio’s privacy policy. Disconnecting AI Mail does not disconnect a separately authorized direct Google integration.

App usage analytics

To understand and improve Onegin, we record app openings, screens, selected features, operation outcomes, call duration and error categories. These records include a random installation identifier, session identifier, platform, app version, approximate country supplied by our hosting service, and link campaign parameters when available. Signed-in events are linked to your verified account. This first-party report does not contain chat text, email content, recording contents or raw IP addresses. Access is restricted to the service owner. Account-linked usage records are removed when you delete your account; verified payment records are handled separately.

AI processing and sharing

For chat, learning, coaching and creative tools, OpenAI receives the messages, relevant conversation history, saved memories, preferences, task instructions and business or website information you provide for the requested feature. Uploaded photos, reference images, attachments and microphone audio are included when you choose the corresponding feature. Optional Calendar features may share relevant event details to prepare the plan or reminder you request. We collect this information from your interactions, uploads and separately authorized integrations, and use it to provide and personalize the assistance you request.

Before sending personal data to OpenAI, a third-party AI service, we show an in-app disclosure and ask you to choose Allow sharing with OpenAI or Not now. Sending a message, opening the app, accepting general terms or granting microphone access does not grant this AI permission. We record your affirmative choice with its disclosure version and time. Without current permission, AI requests and scheduled AI work are blocked; you can continue using features that do not require AI. We ask again when the disclosure materially changes. With that permission enabled, opening AI Mail automatically prepares missing replies for the loaded unread messages. This sends message text, sender, subject and drafting instructions to OpenAI before a voice session starts. Editing with Mia sends the selected email, current reply and your instructions. Voice features send microphone audio and relevant email context to OpenAI. If you enable a scheduled email or assistant skill, it may process newly retrieved content while you are away solely to deliver that enabled feature.

OpenAI processes this content to return your replies, revisions, summaries and voice assistance, not to develop, improve or train non-personalized AI or machine learning models. Our email drafting requests disable API response storage; this does not imply that a provider has no security or legally required retention. See OpenAI’s data processing terms for its processing commitments.

We require third parties receiving personal data to provide the same or an equivalent level of protection as this policy, including confidentiality, appropriate security, limited processing purposes and applicable deletion obligations. OpenAI processes API data under its data processing terms; API content is not used to train models by default. Providers may retain limited data for security or legal obligations under their applicable terms. Our application hosting and database providers process integration data to retrieve messages, securely maintain your connection and save your drafts. Google processes requests to its Gmail and Calendar services; OpenAI receives the relevant content described above after AI permission. We transfer Google data to these providers only as necessary to operate the features you enable, subject to the Google API Limited Use restrictions. We do not transfer Gmail or Calendar content to advertising networks, data-enrichment services or payment processors.

Other account services use Supabase for authentication and the payment provider shown at checkout for payment details. Using those services does not authorize access to your mailbox or calendar for unrelated purposes. Data may be processed outside your country; where required, applicable data protection safeguards apply.

Google API Limited Use

NEXT MBA’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google user data is not sold, shared for advertising, used for credit decisions, or transferred for unrelated purposes. Human access is limited to cases permitted by that policy, such as access you explicitly authorize for support, necessary security investigations or legal obligations.

Storage, security and deletion

Google OAuth tokens are encrypted at rest. Access to account data requires authentication. Tokens remain stored until you disconnect the integration or delete the account. Disconnecting Google access deletes the stored shared Google credentials and requests revocation; it also disconnects Calendar if it uses those credentials.

Saved conversations, drafts, memories, files and preferences remain until deleted through available account controls, account deletion, or when no longer needed to provide the service. Deleting the account initiates removal of its stored content and connected-account credentials. Limited deletion records and records required for security, billing or law may remain. Provider retention is governed by the applicable provider agreements.

Your choices and rights

Use Account & privacy to review or withdraw AI permission and initiate account deletion. Withdrawal stops new AI requests and scheduled AI work; it cannot recall information already processed. Close any active voice session when withdrawing permission. You can also revoke Google access in your Google Account connections.

Contact service@nextmba.com to request access, correction, deletion or a copy of your personal data, or exercise applicable objection and restriction rights. You may also complain to your competent data protection authority. We may need to verify your identity before acting on a request.

Optional Meta advertising measurement

Some iOS versions of Onegin include Meta’s app events SDK to measure installations and subscriptions resulting from our advertising. In those versions, this integration starts only after you allow tracking in Apple’s App Tracking Transparency prompt. Declining does not restrict Onegin’s features. This permission is separate from permission to use AI or connect Gmail or Calendar.

After permission, Meta receives app installation and activation events and automatic App Store purchase, subscription and trial events. Associated data can include the advertising identifier and other device or SDK identifiers; app version, device model, operating system, language and time zone; event times; product and transaction identifiers, price and currency; and SDK technical diagnostics. Payment-card details are not included.

Meta may combine this data with information from its services and other sources for advertising measurement and delivery. Its processing and retention are described in the Meta Privacy Policy and Meta Business Tools Terms.

We do not include Gmail or Calendar content, chat messages, notes, meeting recordings, transcripts, uploaded files or AI prompts in these measurement events. Automatic screen-title, app-link metadata and product-improvement collection are disabled in this integration. The Google data restrictions above continue to apply.

You can withdraw this permission in iPhone Settings → Privacy & Security → Tracking by turning off Onegin. Future automatic app-event logging and advertising-identifier collection are disabled when the app observes that permission has been withdrawn; information already received by Meta cannot be recalled by changing this setting. Website cookie consent does not grant permission for this native iOS integration.

Changes to this policy

We publish updates here and change the date above. New permissions or materially different uses of Google data require appropriate notice and consent before they take effect.