Service Providers & Data Transfers
This page explains which external services can receive information when you use LifeOrg and for what purpose. Some alternatives depend on the service configuration; not every provider receives every request. Read it together with the Privacy Notice and the information shown for the feature you choose.
1. Google Gemini — AI processing
Purpose: personal AI assistance and text/image recognition when you use those features, plus automated moderation of place photographs submitted for publication. Inputs can include a prompt, selected feature context, an image and, for place-photo moderation, the place name and address. The health AI setting applies to its described optional health path, not all photo moderation.
LifeOrg uses the paid Gemini API through a project with active billing. The contracting provider for our Serbian billing address is Google Cloud EMEA Limited, Ireland. Google processes prompts and responses under the Data Processing Addendum incorporated into the paid-service terms and does not use them to improve its products.
Google retains prompts, supplied context and outputs for 55 days to detect and prevent abuse, maintain service safety and make required legal or regulatory disclosures. Authorized Google staff may review flagged content. These abuse-monitoring logs may be used to train models specifically for policy enforcement, but not general-purpose AI models.
Optional developer logging of requests and responses is disabled in our Gemini project. The project’s developer-log retention setting is 7 days, after which logs covered by that setting are marked for deletion; we keep no saved developer datasets there. That setting does not shorten Google’s separate 55-day abuse-monitoring period or set a deletion deadline for LifeOrg’s own records and AI history. We do not voluntarily contribute customer content or datasets for Google’s product or model improvement.
Google handles account, billing and technical usage information separately under its controller-to-controller terms and Privacy Policy. An Irish contracting entity does not mean all processing takes place in Ireland or the EU: Google’s terms allow processing and temporary storage in countries where Google or its agents have facilities. We do not offer zero retention or EU-only Gemini processing. Contact privacy@lifeorg.app to exercise rights or request information about applicable transfer safeguards.
2. DigitalOcean Spaces — file storage
LifeOrg uses DigitalOcean Spaces for object storage associated with images and other uploads. Stored objects can include personal account attachments and content intended for shared or public features. Object access depends on the feature and publication state; approved public photographs do not have the same audience as private account attachments.
Storage, backups and administrative access can involve different locations. You can request the region and arrangements relevant to your data from privacy@lifeorg.app.
3. MapTiler — maps loaded on your device
Map resources can be requested directly from MapTiler by your browser or app. Those requests disclose your IP address and technical request details to MapTiler and can indicate the map area being viewed. This differs from a search relayed only through LifeOrg’s server.
4. Geoapify and configurable search alternatives
Geoapify is the default server-side geocoding/place-search provider. Search requests can include text, place identifiers, language, location bias and coordinates. Coordinates may be precise when supplied to the relevant feature; they are not necessarily reduced to a city-level approximation.
Mapbox and Google Maps are configurable alternatives for relevant map/geocoding requests. Their inclusion here describes supported alternatives and does not state that each receives every request. A provider used for a search receives the query and location parameters required for that request. Ask support if you need to identify which configured provider handled an affected result.
5. Telegram — website contact-form delivery
When you submit the public website contact form, its contents are delivered to the operator through Telegram. This includes the name, email address and message you enter. Do not use that form to send passwords, authentication codes, medical documents, full payment-card details or unnecessary sensitive information.
You can instead contact the relevant LifeOrg email or the operator’s postal address. Choosing email avoids this form’s Telegram delivery route, but email has its own delivery and security characteristics.
6. Core infrastructure and recipient roles
LifeOrg also operates identity, database, cache and observability components. A software project’s name does not itself identify a separate recipient: use of a database or monitoring library does not mean its original software vendor receives your account content. The relevant recipients are the parties actually hosting, operating or supporting the deployment.
Authorized infrastructure providers may process account records, stored content, technical identifiers, diagnostics or support information as needed for their role. We assess the actual data flow and applicable responsibilities when selecting a service; where required, the relationship must be governed by a data-processing agreement and appropriate security and transfer terms.
7. Google — incoming email
Google provides the incoming email delivery route for addresses at lifeorg.app. Email sent to these addresses can therefore disclose the sender and recipient addresses, message content, attachments and delivery information to Google for email handling.
Authorized people handling the mailbox may read correspondence as needed for their duties. Email delivery is a separate purpose from the AI assistance described above; contacting a LifeOrg mailbox is not a request to send your message to an AI assistant. Include only information needed for your question. The applicable retention and international-processing arrangements can be requested from privacy@lifeorg.app.
8. Transfer safeguards and updates
Relevant processing may occur in Serbia and in other countries where a recipient operates or enables access. GDPR transfers, where applicable, and Serbian transfers must each meet their own legal requirements. EU adequacy, EU contractual clauses and Serbian transfer mechanisms are not interchangeable labels.
The appropriate mechanism depends on the recipient and processing. Contact privacy@lifeorg.app to request information about the relevant countries and a copy or explanation of applicable safeguards for your data.
We update this notice when relevant providers or data flows change, and give additional notice or obtain consent where required before a changed purpose or processing takes effect. The Privacy Notice sets out your rights and supervisory-authority contacts.