Privacy policy

Nexional is the trade name owned by Jose Angel Dorado Gonzalez. Economic activity, contracting and invoicing are carried out by Jose Alvaro Ruiz Romero (Spanish tax ID 32733354F), as stated in the current legal notice. Privacy contact: [email protected]. This policy covers the website, application and Google connections. For data processed by a business customer in its mailboxes and operations, that business determines the purposes and Nexional provides the service on its behalf; requests concerning that data should also be addressed to that business.

Access depends on the authorised connection and enabled features. openid and https://www.googleapis.com/auth/userinfo.email identify the connected account and its email address. Nexional stores connection identifiers, granted permissions and OAuth tokens to perform authorised features; it does not request your Google password.

Gmail
https://www.googleapis.com/auth/gmail.send

Send messages, confirmations, reminders and quotes with the specified recipients and attachments.

Gmail / Email Inbox
https://www.googleapis.com/auth/gmail.modify

Read messages, senders, recipients, subject, body, snippets, labels and threads; manage labels, read status and archiving. Inbox reading and management require this additional permission.

Calendar
https://www.googleapis.com/auth/calendar.events

Read, create, update and delete events to synchronise bookings: identifiers, title, description, dates, location and participants according to the operation.

Calendar
https://www.googleapis.com/auth/calendar.calendarlist.readonly

List available calendars and their metadata to select the linked calendar.

Drive / Sheets
https://www.googleapis.com/auth/drive.file

Access files created with Nexional or explicitly selected through Google Picker: file and folder identifiers and metadata, uploaded documents and spreadsheet or row content needed for configured automations. Sheets uses this scope; general access to all spreadsheets is not requested by default.

Older connections may retain broader permissions previously granted (gmail.readonly, gmail.compose, mail.google.com, calendar, calendar.readonly, spreadsheets, drive.metadata.readonly or drive). These are not requested by default in the reviewed version. Check actual permissions in your Google account; this page does not change any authorisation.

Data is used to provide selected features: Email Inbox and the email assistant to view threads, prepare replies and handle enquiries; bookings to synchronise appointments and send confirmations and reminders; quotes to send proposals; and Sheets and Drive automations to record bookings, quotes, catalogue, cost control and invoice registers or upload documents, according to configured bindings. Connecting Google does not enable every module. Message and calendar recipients receive the data needed for those operations. Automatic replies depend on business settings.

Account management, enquiries and contracted service provision are based on contract performance or pre-contractual steps; invoicing obligations on legal requirements; security on the legitimate interest in protecting the service, subject to balancing; and optional analytics on consent. OAuth authorisation enables technical access and does not replace the legal basis the business must have for processing third-party data.

OpenAI processes draft generation requests: these may include the mailbox address, subject, thread summary, latest customer message, recent history (up to six messages in the draft route), user instructions and partial draft. The email assistant may include message text, conversation context and business knowledge when generating replies or invoking modules. This may contain personal data and confidential content: anonymisation is not guaranteed. Google access tokens are not part of the draft prompt.

Google provides the connected APIs. OpenAI receives the content needed for the AI features described above. Anthropic is planned as an alternative provider (fallback) to process the same type of email context if the primary provider fails; it is not active in the reviewed code. Activation requires checking configuration, informing users of its introduction and ensuring terms compatible with this policy. Other assistant routes support Google Gemini as an alternative provider when configured. Data is also stored in the service database and cache. Hosting identity, locations and subprocessors must be specified in the service contractual information.

On the website, Cloudflare hosts functions and verifies Turnstile (including the IP address when available); Resend delivers contact or demo requests with their data and metadata. The chat sends what you type to the Nexional API. AI or infrastructure providers may process data outside the EEA. Before enabling transfers, countries, contracting entity, processing agreements and the applicable mechanism (adequacy decision or standard contractual clauses, with additional measures where needed) must be verified. This policy does not itself establish signed contracts or European data residency.

Nexional’s use and transfer of information received from Google APIs must comply with the Google API Services User Data Policy, including its Limited Use requirements. Processing is restricted to user-requested, visible features, and transfers are restricted to those needed to provide them, security, legal obligations or other cases permitted by that policy. Google data is not sold or used for advertising, advertising profiles, credit assessment or training general-purpose AI or machine learning models. The AI use described here is inference to fulfil a request, not training.

Human access to Google data is restricted to permitted cases: affirmative consent for specific data, security and abuse investigation, legal compliance, or permitted internal operations on aggregated and anonymised data. These restrictions also apply to recipient providers. Use to improve general-purpose models is not authorised. Before activating a provider, its terms and effective training and retention settings must be checked; zero retention is not promised by default.

The backend encrypts stored OAuth tokens and integration secrets with Fernet/MultiFernet, using server-configured keys and support for previous keys. It decrypts them on the server when calling APIs. Connection access checks business ownership (account_id); the OAuth flow checks authorisation state and validity. Calls to Google and default AI endpoints use HTTPS. These measures do not amount to end-to-end encryption of email content or establish encryption of the entire database, backups or logs. Content must be processed by the server and the providers described here.

Tokens are retained while the connection is needed. When a connection is deleted in Integrations, the backend marks it revoked, disables its bindings, deletes its secrets and attempts to revoke the token with Google. Remote revocation may fail or be skipped when authorisation is shared with another connection. You can revoke access directly in your Google account connections. Disconnection does not automatically delete original Gmail messages or records already incorporated into Nexional, Drive documents, Sheets rows or Calendar events.

Email may persist in thread and message cache tables, conversations and module records; expiry of a temporary cache does not erase those copies. Temporary detail cache uses 180 seconds and mailbox processing state defaults to 180 days, subject to configuration; these are not global retention periods. To request deletion of Nexional copies, email [email protected]. Data no longer needed will be deleted or anonymised, except for legal obligations or the defence of claims. Operational periods for databases, logs, backups and providers must be finalised with the controller before this version is published.

You may request access, rectification, erasure, restriction, objection and portability where applicable, and withdraw consent without affecting prior lawful processing, by emailing [email protected]. Identify your account and the processing concerned; additional identity information will only be requested when necessary. Requests are handled within GDPR time limits (generally one month, subject to legally permitted extensions). You may complain to the Spanish AEPD or your competent supervisory authority. Where the business customer is the controller, Nexional will assist with the request. AI may make mistakes; request human review of responses and any decision affecting you.

Browsing analytics is separate from Google OAuth processing. The website loads Google Tag Manager and Microsoft Clarity on production domains when analytics is accepted; Meta Pixel only when configured and advertising is accepted. Emails, files, events, cells and tokens obtained through Google OAuth must not be sent to those services. Cookie consent does not authorise Google access or AI email processing. Change it using Cookies in the footer. Your choice is stored in the browser for six months. Remote tag container content requires separate oversight.

Current legal notice, cookies and terms