Your Privacy is Our Priority

What we access, and why

• Your Google account email address and name: to sign you in when you choose "Sign in with Google" in our mobile app, to show you which Google account is connected, and to keep each connected account separate.
• Google Calendar — your primary calendar only: we read the start and end times of your upcoming events that are not marked "Free", so that nobody can book you at a time you are already busy. Depending on the privacy level you choose when connecting, we also store each event's title and location (and, at the fullest level, its description) — or nothing except that the time is busy. We also create, update and remove events on that calendar for the bookings, lessons, meetings and interviews you schedule in Laabam.One, so they appear in your Google Calendar.
• Gmail — only if you connect Gmail: to show your recent email (the last 7 days, then new mail as it arrives) in the Laabam.One Email Hub; to find bills and receipts sent to you so you can record them as expenses; and to send the emails you choose to send from Laabam.One from your own address. Depending on the privacy level you choose, we read each message's sender, recipients, subject, date and body. To find receipts we search for messages with attachments that look like bills or receipts — up to two years back when you first connect, then new ones as they arrive — and save those attachments to your company's private storage.

How we use it

We use Google user data only to provide and improve the features described above, which you can see and control in the app. We do not use it for any other purpose.

What we never do with Google user data

• Sell, rent or trade it — to anyone, for any purpose.
• Use it for advertising, including personalised, retargeted or interest-based ads, or pass it to advertising platforms or data brokers.
• Use it for marketing or promotional messages, analytics, profiling or research.
• Use it to determine creditworthiness or for lending purposes.
• Use it to develop, improve or train generalised artificial intelligence or machine-learning models — ours or anyone else's.

Google user data and AI

Google user data reaches an AI service in one case only: a receipt that arrived by Gmail, when you open it and ask Laabam.One to read it (AI receipt scan, section 3.1). That attachment alone is sent to OpenAI, solely to extract the vendor, date, amounts and tax details and return them to you; under the OpenAI API terms it is not used to train models. Your calendar events and email messages are never sent to an AI service. AI assistant connections (section 3.2) cannot read your email, attachments or calendar events — when an assistant checks booking availability, it receives only free time slots, never the events behind them.

Who we share it with

We do not share Google user data with anyone, except:

• Service providers that store and process it on our behalf, only to run the features above: our cloud hosting provider (servers and private file storage), and OpenAI for receipts you ask us to read. They may use it only for that purpose and must protect it.
• The recipients of an email you choose to send through Gmail from Laabam.One.
• Where required by law, or where necessary to protect against fraud, abuse or security threats.
• As part of a merger, acquisition or sale of assets — and then only with your explicit prior consent.

Email and calendar data you sync becomes part of your company's Laabam.One workspace: people in your company who have access to the Email Hub, receipts or calendars can see it, according to the roles and permissions your company sets. A record you save from it — such as an expense you create from a receipt — becomes part of your business records and is handled like the rest of them.

Who can read it

Our staff do not read your Google user data unless you ask us to (for example, by sharing a specific message or event with our support team), it is necessary for security purposes such as investigating abuse, it is required to comply with applicable law, or it has been aggregated and anonymised for internal operations.

How we protect it

The access tokens Google issues to us are encrypted before they are stored. Google user data travels over encrypted connections and is stored in your company's own workspace on our servers, protected by the measures in section 5; receipt attachments are kept in private storage that is not publicly accessible.

How long we keep it, and how to delete it

• Calendar events you delete or move in Google Calendar are removed or updated in Laabam.One at the next sync.
• You can disconnect a Google account at any time from the Email Configuration settings or the Calendar Sync page in Laabam.One. We stop reading from and writing to it immediately. What was already synced stays in your company's workspace until you ask us to delete it.
• You can also remove Laabam.One's access from your Google Account at any time at myaccount.google.com/permissions.
• To have the Google user data we hold deleted — including stored tokens, synced calendar events, email and saved receipt attachments — email privacy@laabam.one. We delete it within 30 days. Records you saved into your books from it follow section 6.
• Deleting your Laabam.One account deletes all Google user data we hold (section 10).