FilAI and transcription
OpenRouter can intermediate messages, images, extracted text, agenda or memory context and transcription. Model execution services and Jev/TypeSafe decisions may also take part. A model publisher is not necessarily its execution provider.
Other offered connections are OpenAI, Google Gemini, Mistral, Groq and DeepSeek. Ollama and compatible APIs use the configured server address. Your account uses its actual connection, with potentially different models for analysis, memory, vision and audio. The connection key authenticates to that provider; Fil passwords should not be sent to AI.
Web search and page reading
SerpAPI provides search results from queries prepared from your request. Google Custom Search can provide images. Queries can contain places, dates, names or other details from your text and are not inherently anonymous.
When Fil reads a page or shared link, its destination receives a request from the Fil server and the requested URL, which may contain personal parameters. When you open a link yourself, the destination receives a request from your device under browser rules.
Places, routes and maps
Geoapify may receive coordinates or place queries for geocoding and place search. Google Maps Platform, including Geocoding and Routes, may receive an address, origin, destination, arrival time and travel mode.
OpenStreetMap supplies some diagnostic map backgrounds. Tile requests expose the viewed area and device IP. Event titles, notes and summaries used to understand a place may separately be processed by the account’s AI connection.
Calendars and imports
Google Calendar and Microsoft can connect through OAuth. Apple iCloud and other CalDAV servers use the requested credentials. Device calendars and ICS files are other sources. Fil encrypts necessary connection secrets and imports selected events into your account.
Imported information can then be used by Fil organisation features, including AI context when enabled. Disconnecting a source and deleting previously imported entries are separate operations. Original copies remain with the source provider.
Notifications and updates
Expo, Apple Push Notification service and Firebase Cloud Messaging can deliver mobile notifications using tokens, titles, text and navigation data as appropriate. Web push uses Google, Apple, Mozilla or Microsoft services depending on browser; the Web Push protocol encrypts its payload.
Expo/EAS distributes app updates and resources, generating technical download requests from your device. Local notifications, alarms or widgets do not by themselves require uploading your entire agenda to a push service.
Hosting, memory and diagnostics
The website and backend currently run on Gabriel Angotti’s personal infrastructure. PostgreSQL stores business data. Memory also uses a graph index and numerical representations calculated by an embedding model on the server. The reviewed implementation does not require an external embedding API for this.
Private Inspector diagnostics can receive AI requests, responses, metadata and processing steps in Preview. Inspector is not publicly exposed, and the reviewed production instance does not send it traces. Diagnostic copies and backups should not be treated as automatically erased with an account item.
Read service information
These documents may change. Linking them does not mean a specific contract, European location or zero-retention setting has been verified for your connection. For personal or compatible servers, also consult their operator.
Questions or a data request?
Write to Gabriel Angotti with the relevant account address. Do not include passwords or API keys.
contact@heyfil.com ↗