Google integration

Every user connects their own Google account, in Lumo under Settings, Gmail. You then see Google's consent screen and choose which permissions you grant. Only the Gmail read permission is needed to connect. You may untick the others.

Lumo asks for these permissions:

• Read Gmail (gmail.readonly). Lumo files mail you exchange with people who are already in your workspace on that person, the organization and the deal. Your team then sees the full customer history in one place.
• Send Gmail (gmail.send). You send an email from Lumo with your own address. Lumo only sends an email you write and confirm yourself.
• Calendar events (calendar.events). Meetings with known contacts appear as meetings in Lumo, and meetings you plan in Lumo appear in your calendar. Bookings through your scheduling page reach your calendar the same way.
• List of your calendars (calendar.calendarlist.readonly). Your scheduling page can then take all your calendars into account, not only your main calendar.
• Busy or free (calendar.freebusy). The scheduling page only asks when you are busy, without the content of your events.
• Your email address (openid and userinfo.email). Lumo then knows which Google account belongs to your connection.

An admin can also connect Google Analytics per workspace (analytics.readonly). Lumo then only reads the visitor figures of the chosen property for the reports in Lumo.

• For mail, Lumo first reads only the headers, such as sender, recipients and subject. Only when a known contact takes part does Lumo fetch and store the content. Lumo does not store mail with unknown people.
• Lumo does not label, archive, change or delete anything in your Gmail and creates no drafts.
• Lumo does not read events you marked as private or confidential, and no focus time, out of office or working location.
• Lumo only changes or deletes calendar events that Lumo created itself. Deleting is off by default.
• We do not sell data from Google, do not use it for advertising and do not pass it to data brokers.
• We do not use data from Google to train or improve AI models, neither ours nor anyone else's.
• Lumo never asks for your Google password. Signing in always happens on Google's own page.

Connected mail is private by default: only you see it in Lumo. Per connection you can choose to let your team see the mail too. This is enforced per row in the database, so it applies wherever mail is visible in Lumo, including search, export and the API.

Sales Surge staff do not read your data from Google. That only happens when you explicitly ask for it, for example in a support request, when it is needed for security or to investigate abuse, or when the law requires it.

If an admin switches on the AI assistant in the workspace, the assistant can use mail or events to answer a question you ask. Only then does that part go to the AI provider, and the provider does not train models on it. See AI in Lumo in the privacy statement.

The data is stored in Lumo's database at Supabase in London, United Kingdom. The keys Google issues (the access token and the refresh token) are encrypted with AES-256-GCM. They never leave the server and are never written to logs.

We share data from Google only with the service providers needed to deliver Lumo, such as hosting and the database. They are listed on the sub-processors page.

• Google's keys are kept as long as your connection exists. When you disconnect, we revoke them at Google and delete them at once.
• Mail and events linked to a person, organization or deal are kept as long as they are in the workspace. They are then part of the workspace's customer history, which belongs to the customer.
• Mail not linked to a contact is deleted by Lumo after the workspace's retention period. The default is 2 years (730 days). The customer can change that period.
• Google Analytics: when an admin disconnects, we revoke the key at Google and Lumo reads nothing more.
• When the agreement with the customer ends, we delete the personal data at the customer's request, as the data processing agreement describes.

• In Lumo. Go to Settings, Gmail, and choose Disconnect. You then choose whether the stored mail stays or is deleted for good. Google's keys are deleted in both cases. You can also exclude a single mail thread: Lumo then deletes the stored mail of that thread and skips the thread from then on.
• At Google. You can also revoke Lumo's access at myaccount.google.com/permissions. Lumo then stops reading and sending at once.
• On request. Email info@sales-surge.nl if you want us to delete data from Google. We respond within one month. If the data is in your employer's workspace, we coordinate the request with that customer.

Lumo is a product of Sales-Surge B.V., Professor W.H. Keesomlaan 12, 1183 DJ Amstelveen, the Netherlands. Chamber of Commerce (KvK) 99261758.

Send questions about the Google integration or your data to info@sales-surge.nl or call +31 6 5350 9843. See also the privacy statement and the terms of use.