Skip to content
Fallthere, home page

Privacy.

Last updated: 26 October 2026

This page says what personal data Fallthere handles, why, how long it keeps it, who receives it and how you can use your rights. It covers the fallthere.com website, the app at app.fallthere.com and the Android app. Fallthere is in beta and you join by invitation.

If you connect Gmail or Google Calendar, the Google data section says what we read, what we do not do and how to remove the permission.

Who we are

The data controller is Fibonacci Works S.r.l., Via Brigata Liguria 105 R, Genova (GE), Italy, VAT number 03108390992.

To write to us about these matters: certified email (PEC) fibonacciworks@pec.it; ordinary email info@fallthere.com. We have not appointed a data protection officer.

Fallthere plays two roles, and it helps to know which one concerns you.

Controller. For your account data and the data needed to run the service (who you are, how you sign in, security, billing, support, this website) we decide how and why it is processed.

Processor. For what people and organizations write, upload and connect inside Fallthere (pages, tables, files, messages, email, calendars, contacts, calls, conversations with Pan) the controller is the organization that uses Fallthere: usually your employer, your client or your team. We process that data on its behalf and on its instructions, under a written agreement (article 28 of the GDPR). If you want to know why it processes the data or who sees it, ask the organization. If you write to us to use a right over that data, we tell you who to contact and we help the organization answer you.

One exception: the examples an organization can donate to improve Laya (section Pan, agents and Laya). For those, we are the controller.

What data, why and on what legal basis

For each kind of data: what it is, what it is for and the legal basis we rely on. Retention times are in the section How long we keep it.

Your account

Data
Email address, name, photo, language, time zone and the profile fields you fill in. Your password, stored only as a hash (bcrypt), two-step verification codes, open sessions, devices subscribed to notifications. If you sign in with Google or Microsoft, the name and email they give us.
Why
To let you in, to let the other people in your organization recognize you, to keep sign-in secure.
Legal basis
The contract (article 6(1)(b) of the GDPR) and our interest in protecting access (point f).

What you write, upload and connect

Data
Pages, tables, files, whiteboards, forms, messages, comments, tasks, contacts, calls (attendance, transcripts, minutes, recordings if switched on), calendars, the email you connect, conversations with Pan and with agents.
Why
To give the organization the service it chose.
Legal basis
The organization decides it: it is the controller and states it in its own notice. For us, the agreement with the organization applies.

Action log, errors and working time

Data
Who granted access and what an assistant, a job or a channel did on a person’s behalf, never the content. The type of service error and how many times it happened, never content or a person. A signal every minute while a page is in view, for working-time statistics.
Why
Security, proof of what happened, understanding failures. Working-time statistics are for the people who run the organization, if they choose to look at them.
Legal basis
Our interest in security and proper operation (point f). For working time, the organization decides (see Work).

Billing

Data
When an organization pays for a subscription: company name, billing address, VAT number, name and email of the payer, amounts, customer and subscription identifiers. Only Stripe sees card details.
Why
To collect payment, issue and keep invoices.
Legal basis
The contract and a legal obligation (points b and c).

Emails Fallthere sends by itself

Data
Invitations, sign-in emails, booking confirmations, notification digests. The text is composed when it is sent and is not kept; we keep the recipient’s address and the outcome.
Why
To deliver what you asked for or what concerns you. At most five emails a day to the same address.
Legal basis
The contract.

Support and requests

Data
Name, email address and the content of what you write to us, including to ask for a demo or to use a right.
Why
To answer you, and to be able to show that we did.
Legal basis
Your request and our interest in answering you (points b and f). For requests about your rights, a legal obligation (point c).

Notifications on your phone and computer

Data
The address your browser or phone gives us so we can reach it. A notification says who, what and where, never the text of a message.
Why
To tell you there is something for you.
Legal basis
Your choice: you switch them on and off whenever you like.

The fallthere.com website

Data
The server keeps a technical log of requests: IP address, time, page requested. No analytics tools, no content loaded from other people’s servers.
Why
Security and failures. It is not used to track people.
Legal basis
Our interest in security (point f).

Work: what your organization can see

If you use Fallthere for work, your organization sees your name and email, your role and what you write in shared teams. People with the permission “See everyone’s work” also see the action log and the working-time statistics.

It does not see your Private pages, your conversations with Pan or the email you connected as a personal mailbox. The database decides this on every request, not the screen. A mailbox connected to a team, on the other hand, is visible to the team members who have permission to read it.

Working time and the action log can bear on remote monitoring of employees. The organization must comply with article 4 of the Italian Workers’ Statute (law 300/1970) and inform you. We give it the technical information to do so.

Pan, agents and Laya

The artificial intelligence features are switched on by default. Each has its own switch: some belong to the person, others to whoever runs the organization. When you talk to Pan, Pan tells you it is an artificial intelligence.

Pan and agents

They answer with the language model and the key of whoever pays: yours, your team’s, or the organization’s if the people who run it decided to pay for Pan for everyone. Fallthere has no key of its own to read your data. Pan sends the provider what you see on screen, only where you can use it and with your permissions, not someone else’s. The text goes through our server, which forwards it without keeping a copy. Our logs keep the provider, the type of request, the outcome and the timings, never the text.

The default provider is OpenRouter, which routes the request to a model provider. With your own key you can also choose EUrouter (models run in Europe), OpenAI, Anthropic, Google or DeepSeek. From the moment the text leaves, that provider’s rules apply. With OpenRouter we ask for zero retention and no training when the organization pays (the default) and whenever the organization requires zero-retention providers only. With your own key and without that requirement, the contract you have with the provider applies. Whoever runs the organization can also limit Pan to providers that compute in Europe.

DeepSeek is based in China: if you pick its direct service, the text leaves the European Economic Area for a country with no adequacy decision.

What Pan proposes, and who decides

Pan asks before writing to an outside service. What it proposes (a task, a meeting, a contact) exists only once you say yes, in “To decide”. We take no decision based solely on automated processing that has legal effects on you or similarly affects you (article 22 of the GDPR).

Pan’s automatic email features are on by default and you switch them off in Settings: watching new email by itself, linking emails to the people and companies who wrote them, proposing where they go. Text goes to the model only if a key is connected. With no key, nothing leaves.

Laya

Laya is the judge of automations: it decides, for example, whether an email proposes a meeting or a message contains something to do. It is our own model and runs on our own machine, with no network access. The text it reads is not written to any log.

When Laya is not sure. If the organization has a system user with a model key, the doubtful case goes to an outside model: DeepSeek V4.1 Flash, through OpenRouter and DeepInfra, in the United States. This choice is on by default and whoever has the “Keys” permission can switch it off. Only the reduced text leaves, with email addresses, phone numbers and IBANs masked, using the organization’s key and at zero retention. If the provider cannot guarantee zero retention the request fails; it does not go elsewhere. Without that key the doubtful case does not become a proposal and the text does not leave.

Laya learns. Each yes or no you give to a Laya proposal becomes an example for the organization: we keep a numeric fingerprint of the text, not the text. Examples stay inside the organization, help judge its later proposals, and are deleted when the person is deleted or when the organization switches off “Laya learns”.

Donated examples. If the organization leaves donation on (it is on by default), the text a proposal came from (an email, a message, minutes, a task), cleaned of names, addresses, links and numbers, goes to Fallthere to train Laya. It carries neither the person’s name nor a precise date, only the month. At most 1,500 characters per example and a thousand examples per organization. For this processing Fallthere is the controller, and the legal basis is our interest in improving Laya (article 6(1)(f)). All of an organization’s examples are deleted when it switches donation off or leaves. We cannot find a single person’s example, because it carries no name: if you object, write to us and we will raise it with the organization, which can switch donation off. The text of Gmail messages is never donated.

Search by meaning in email

To search email by meaning and not only by words, the text is turned into vectors, lists of numbers that represent its sense. The feature is on by default for personal mailboxes, not for a team’s, and switches off mailbox by mailbox; switching it off deletes the vectors already computed. An embedding model that runs on our own machine, or on your computer, computes them: for this reason the text does not go to an outside provider. If that service is not active, search stays word-based.

Voice, transcripts and captions

If you talk to Pan by voice, the audio and the text of the answer go to the provider of the key in use (by default OpenRouter, with OpenAI’s GPT Audio Mini voice). That provider may keep audio and text for a limited time. Voice is on by default; if the organization allows only zero-retention providers, voice does not switch on. The microphone is on only while the dialogue is open. To transcribe or translate a call, audio or text goes to the same provider. Live captions use your browser’s speech recognition: Chrome sends the audio to Google’s servers, Safari recognizes it on the device, Firefox does not offer it. These are your switches.

Web search and browser

When Pan searches the web, the query leaves our machine for public search engines, without your name. If the query contains personal data, it leaves with the query. When Pan opens a page it does so from a browser on our server: sites see our machine’s address, not yours.

Google data (Gmail and Google Calendar)

This section applies if you connect your Gmail or your Google Calendar to Fallthere. They are two separate connections, and you make them only if you want to.

What we read, and with which permissions

  • Gmail (permission https://mail.google.com/, used through the IMAP and SMTP protocols): messages, headers, folders and labels, drafts; the addresses of the people you correspond with, taken from messages to suggest recipients; the address of the account. Attachments are downloaded only if you ask to save them. We ask for this permission because IMAP and SMTP cannot be authorized with the narrower Gmail API permissions, and read-only ones would not let us send, move, archive or delete.
  • Google Calendar (permissions calendar.events and calendar.calendarlist.readonly): the list of calendars you are subscribed to; title, location, start and end of the events in the calendars you choose, five at most. We do not read attendees or descriptions. We write to Google the events you create or change in Fallthere, in the calendar you pick.
  • The Google account (permissions openid and email): the email address, to know which account you connected.

What it is used for

Only for the features you see in Fallthere: showing you your mail, keeping it in sync with Gmail (read state, stars, archive, trash, folders, drafts), searching it, letting you reply and send from your own address; showing Google events in the Calendar and sending to Google the ones you create here. When you ask Pan to work on a message or an event, or leave its automatic features on, Pan and Laya propose things to do (a meeting, a task, a contact) and you decide with a yes or a no.

What we do not do

  • We do not use Google data for advertising and we do not sell it.
  • We do not use it to train, create or improve general-purpose artificial intelligence or machine learning models. The text of Gmail messages does not enter the examples donated for Laya. Laya can use your decisions to judge the same organization’s later proposals better (see above, “Laya learns”): what remains is a numeric fingerprint, not the text, and it can be switched off.
  • No one at Fallthere reads it, unless you ask us to for a support case, for security or abuse reasons, or because the law requires it.
  • We do not transfer it to third parties, except: to the provider that hosts our servers; to the language model provider whose key is connected, only for the text you ask Pan to process or that the automatic features you left on process; to DeepSeek, through OpenRouter and DeepInfra, for Laya’s doubtful cases, if the organization left them on and has a key; for security or by legal obligation.

Fallthere’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.

Where it is kept and how we protect it

On a server of Contabo GmbH, in Germany, with the servers in Europe. The connection is encrypted. The permission Google gives us (the refresh token) is encrypted with AES-256-GCM in a separate service, and the secret of our Google app never sits on people’s computers. Database rules show a personal mailbox only to the person who connected it; a mailbox connected to a team is visible to the team members who have permission to read it. Backups are encrypted.

How long we keep it, and how you remove the permission

  • Mail. Headers (sender, recipients, subject, date) are kept while the mailbox is connected. Message text is kept 365 days (you can choose from 7 to 3650) and then removed, leaving a preview of a few lines; if you open the message, it is downloaded again from Gmail. If you unlink the mailbox, the copies and the refresh token are deleted at once. The permission stays listed in your Google account until you remove it at myaccount.google.com/permissions.
  • Calendar. If you disconnect Google Calendar, Fallthere asks Google to revoke the permission: the connection goes away and Google events disappear from Fallthere. Events you created here and sent to Google stay on Google, and the pages stay in Fallthere.
  • Account. If you ask to delete it, it is suspended at once and deleted after 30 days.

If we ever wanted to use Google data in a way other than the one written here, we would ask you first and it would need your yes.

Who receives the data

The people in your organization who have permission to see it, and no one else. Then the providers that help us run the service, below. The database, the web server, the search engine and Laya are programs we install and run ourselves, on our own machine.

Contabo GmbH

What it does
Hosts the server where the database, files, services and website run.
Data
All the service’s data, on the server’s disk.
Where
Germany, with the servers in Europe.

Hostinger

What it does
Receives an encrypted backup copy every night, in a folder of its own. The key to open it is not on that server.
Data
The encrypted copy of the service’s data.
Where
Hostinger International Ltd, a company based in Cyprus. The content is encrypted.

IONOS

What it does
Manages the domain and the mail server from which Fallthere sends its own emails (invitations, sign-in, confirmations).
Data
The recipient’s address and the text of the service email.
Where
Germany.

Cloudflare, Inc.

What it does
Relays video, audio and screen sharing of calls in real time.
Data
The audio and video streams, participants’ IP addresses, session identifiers. It does not record the streams: recordings and transcripts, when you switch them on, are made by Fallthere.
Where
United States, with a global network: the stream goes through the point closest to the participants, also outside the European Union. Safeguards in the section Outside the European Union.

Stripe Payments Europe, Ltd and Stripe, Inc.

What it does
Collects the subscription when an organization pays, on its own payment page. For some purposes, such as anti-money-laundering and fraud prevention, Stripe is an independent controller.
Data
Payer’s email and name, billing address, VAT number, customer and subscription identifiers, card details (which Fallthere never sees).
Where
Ireland and the United States. Safeguards in the section Outside the European Union.

OpenRouter, Inc. and the model providers it routes to (including DeepInfra, Inc.)

What it does
Runs the models for Pan, agents, Laya’s doubtful cases, voice.
Data
What you ask Pan, the context of the page in front of you, the attachments you pick, the texts to judge. See Pan, agents and Laya.
Where
United States. Safeguards in the section Outside the European Union.

EUrouter, OpenAI, Anthropic, Google (Gemini), DeepSeek

What it does
Only if you choose that provider with your own key: runs the models for Pan.
Data
The same as above.
Where
EUrouter computes in Europe; OpenAI, Anthropic and Google in the United States; DeepSeek is based in China.

Notification delivery services

What it does
Carry the notification to your device: Google Firebase Cloud Messaging for the Android app; Google, Mozilla, Apple or Microsoft, depending on the browser, for the website’s notifications. For browsers the message is encrypted.
Data
The device address and the notification, which says who, what and where, never the text of a message.
Where
Wherever the service is based, also outside the European Union.

Public search engines

What it does
Answer Pan’s web searches, queried by our own search engine.
Data
The text of the search, without your identity.
Where
Wherever the engine is based.

Services you connect

What it does
Google, Microsoft, GitHub, Telegram, Slack, WhatsApp (Meta), Microsoft Teams, Discord and the other tools you authorize, including Zapier, Make and n8n.
Data
Only what the feature you switched on needs.
Where
Depends on the service. Its own rules apply.

Finally: our accountant and our lawyers, bound by professional secrecy, and public authorities when the law requires it.

Outside the European Union

The data sits on a server in Germany. Some providers are based or operate in the United States: Cloudflare, Stripe, OpenRouter and the model providers it routes to, and those you choose with your own key. For these transfers we rely on the EU-US Data Privacy Framework (Commission implementing decision (EU) 2023/1795) when the provider takes part in it, and on the Commission’s standard contractual clauses (implementing decision (EU) 2021/914) otherwise. Cloudflare and Stripe state that they take part in the EU-US framework, with the standard clauses as a fallback; for OpenRouter and the other model providers the standard contractual clauses apply. You can ask us for a copy of the safeguards.

Two cases sit outside this scheme: DeepSeek, if you pick its direct service, is based in China and there is no adequacy decision; Chrome’s speech recognition for live captions sends audio to Google’s servers. Both start from your choice.

How long we keep it

The principle is to keep data for as long as the purpose needs and no longer (article 5(1)(e) of the GDPR). Where the law sets a term, that term applies.

  • Account and profile. As long as the account exists. If you ask to delete it: suspended at once, deleted after 30 days. If no one signs in for 12 months, two emails arrive 30 days apart, and 30 days after the second the account is deleted; a single sign-in stops it all. What you wrote in shared teams (pages, messages, tasks) stays, without your name, because it belongs to the organization.
  • Conversations with Pan. By default 6 months from the last time you spoke (180 days without a paid plan). With a paid plan, whoever runs the organization chooses: 30 days, 3 months, 6 months, 1 year or “never, until you delete them”. You can delete them sooner; they are deleted with the account.
  • Pages, files, messages, tables. Until the organization removes them. A removed page goes to the trash. Whoever runs the organization can set a term for messages, files and call transcripts.
  • Call recordings. Audio and video are removed as soon as the transcript is ready; the words stay, with their own term. If there is no transcript, they stay.
  • Email copies. Headers while the mailbox is connected; message text 365 days by default (7 to 3650); everything deleted at once if you unlink the mailbox. Attachments you saved in Fallthere stay like any other file.
  • Action log. 1 year. Whoever has the “Settings” permission can choose longer, up to 10.
  • Service errors. 30 days.
  • Working time. Minutes for 90 days, then daily summaries for a year.
  • Service emails. The recipient’s address and the outcome, for 90 days.
  • Billing. 10 years (article 2220 of the Italian civil code). Deleting an account does not touch them: they belong to the organization.
  • Website server logs. 30 days.
  • Backups. Nightly encrypted copies, kept for up to 35 days, then the oldest is removed. A deletion therefore stays in the backups for up to 35 days.
  • Laya examples. Fingerprints, until the person is deleted or the organization switches off “Laya learns”. Donated examples, until the organization switches donation off or leaves.
  • End of contract. The organization has 30 days to take its data away; then we delete it within another 30 days, and from backups within another 35. Invoices stay, for 10 years.
  • Support and rights. Correspondence with people who write to us: 24 months from the last message, 10 years if it is a contract or an invoice. Requests to use rights: 5 years, to show that we answered.

Your rights

You have the right to access your data, to have it corrected or deleted, to restrict its processing, to object and to receive it in a readable format (articles 15 to 22 of the GDPR). Where possible you can use them yourself:

  • Download your data (articles 15 and 20): Settings › Privacy and data › My data. You get a .zip file with your profile and memberships, the mailboxes and devices connected, the messages you wrote, the tasks assigned to you and your Private pages. A “Readme” file says what is in and what is not: not included are keys and sealed secrets, what belongs to the organization, or email, which sits in your mailboxes.
  • Delete the account (article 17): Settings › Profile › Delete my account. What happens at once and what stays is shown in the confirmation window. If you are the only person who runs an organization, you must first hand it to someone else or delete it.
  • Correct name, photo, language and time zone: Settings › Profile.
  • Switch off the features of Pan, mail and notifications: in Settings. Where processing rests on your consent, you can withdraw it at any time.
  • Object, restrict or ask for something else: write to us. We answer within one month (article 12(3)), extendable by two months for complex requests, and we tell you why.
  • Organization data. For what you write inside Fallthere the controller is the organization: write to it, and we help it answer you.

If you are not satisfied you can lodge a complaint with the Italian data protection authority, the Garante per la protezione dei dati personali (garanteprivacy.it), or with the authority of the EU country where you live or work.

How we protect it

Access rules live in the database, which decides on every request who sees what. Keys and secrets are sealed by a separate service (AES-256-GCM). Sign-in has two-step verification, which whoever runs the organization can make mandatory. Each service works with a role that can do only a few things. The connection is encrypted and backups are encrypted. If an incident concerns your data, we notify the Garante within 72 hours when required and tell you or your organization without delay.

Minors

Fallthere is for people who work. We do not offer it to anyone under 18, and in any case not to anyone under 14 (article 2-quinquies of the Italian privacy code). If we find that an account belongs to a younger person, we close it.

Changes

If we change this page in a way that matters, we tell you by email or inside the app at least 30 days before. The date of the last update is at the top. Who publishes the website and how Pan’s voice trial works are in the legal notice.