01
Our role and contact details
Neuphlo I/S, Danish company registration number DK45010430 ("Neuphlo", "we", "us", or "our"), is the data controller for account identity, billing, product operations, service communications, security, support, and our own business administration.
An organisation may decide why and how its members use workspace content. In that situation, the organisation may be the controller for that content and Neuphlo may act as its processor under the applicable agreement. The organisation’s own privacy information and instructions may also apply. Questions and data-protection requests can be sent to help@neuphlo.com.
02
Information we collect
Depending on how you use and configure Neuphlo, we process account and profile data such as name, email address, profile image, user identifiers, sign-in state, invitations, notification preferences, and external identity or OAuth provider identifiers, tokens, scopes, and connection status.
Workspace and collaboration data can include workspace name, logo, description, business email and address details; owners, members, roles, permissions, invitations, and Phlos (AI agents); Rooms, participants, messages, threads, reactions, attachments, Work, Pages, files, links, resources, history, and activity records.
AI, device, tool, and project data can include prompts; selected Room or thread history; related Work, Pages, files, resources, and instructions; Phlo, model, provider, runtime, and paired-device configuration; approved project folders and path or file metadata; tool inputs and outputs; approval requests and answers; operation events, changes, errors, omissions, truncation, provenance, usage, and response status; and connected-service identifiers, permissions, and state.
Billing and support data can include plan, offer, billing period, accepted human count, seat and entitlement state, trial and renewal dates, invoices, tax or billing details, provider customer or subscription references, payment handoff status, support communications, and dispute or refund records. Stripe handles hosted checkout and payment management; Neuphlo does not receive or store full payment-card details.
Technical data can include IP address, browser or app type, operating system and device information, cookies and local-storage identifiers, session and authentication events, sync and version data, timestamps, request and response metadata, performance and reliability diagnostics, and security or abuse-prevention logs.
03
Where information comes from
We receive information from you, other workspace members and administrators, your browser or app, paired devices, identity and OAuth providers, Stripe, AI or tool providers, and other connected services. We also create records when the service applies permissions, synchronises content, prepares context, routes an operation, processes billing, or records security and reliability events.
04
How we use information
We use personal data to authenticate people; create and operate accounts and workspaces; apply permissions and maintain shared history; synchronise content and support offline use; store and deliver files; route explicitly requested Phlo and tool operations; connect devices and providers; administer trials, subscriptions, tax, and billing; communicate about the service; provide support; measure and diagnose operation, reliability, and security; prevent abuse; enforce our terms; and meet legal obligations.
05
Legal bases
We process personal data where it is necessary to perform our contract with you, comply with legal obligations, or pursue legitimate interests in operating, securing, supporting, understanding, and improving the service. We rely on consent where applicable law requires it, including for an optional connection or processing choice where consent is the appropriate basis. You can withdraw consent at any time without affecting earlier lawful processing. If we process workspace content for an organisation as its processor, that organisation determines the relevant legal basis.
06
Workspace visibility
Room names, avatars, and archived state are visible to workspace members so Rooms can be discovered. A Room’s purpose, participant list, messages, threads, reactions, attachments, and Room-linked Work and Pages are visible only to current Room participants. Workspace owners and authorised managers may administer membership and review access requests without gaining content access unless they are added as participants. Work and Pages that are not restricted to a Room may have a broader workspace audience.
When an authorised Phlo or tool is invoked, the selected provider and, for a paired runtime, the owner or operator of the paired device may receive the prompt, instructions, selected context, files, approval answers, and operation results needed to perform the request. Other Room participants may see the resulting message and provenance.
08
Google Calendar
If you connect Google Calendar, Neuphlo receives the calendar list for the Google account you choose and reads events from calendars you select. We store an encrypted connection grant and the event data needed to display and synchronise those calendars. Your personal selection is private to you in each Neuphlo workspace.
You can separately choose to link a Google calendar to a shared Team calendar. A workspace manager must approve that link. Authorised Team members can then see event details from the linked calendar; events marked private by Google appear as Busy. People who already have access in Google may see more under Google's own sharing settings.
When you create, edit, delete, or publish an event through Neuphlo, we send the requested change to Google using a connected account authorised for that action. Publishing a shared Team event may use the Google connections of Team members who opted in. Neuphlo may require cleanup of published Google copies before disconnecting. When you disconnect, we clear cached Google events and revoke the grant where possible; some connections require you to revoke access in your Google Account settings. Neuphlo-owned events remain, and Google may retain events under your Google Calendar settings.
09
Google user data and Limited Use
Neuphlo's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements. Neuphlo's use and transfer of raw or derived user data received from Google Workspace APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Neuphlo uses Google Calendar data only to show your selected calendars and events in Neuphlo, to share linked calendars with Team members you and a workspace manager approve, and to create, change or delete events in Google when you ask. We do not sell Google user data or use it for advertising. Google user data is never used to develop, train or improve AI or machine learning models, whether ours or a third party's. Neuphlo staff do not access Google Calendar data except when you ask us for support, or when required for security or by law.
Google Calendar data is kept out of Neuphlo's agent, AI and MCP features, checked by automated tests in our codebase. It is never included in agent context, private agent conversations, Room agents, agent tools, MCP tools offered to external clients such as ChatGPT or Claude, Neuphlo Connect devices, or web search. Google user data is never sent to any AI model or AI provider, in raw, aggregated, anonymised or derived form.
AI providers. Neuphlo does not hold its own AI model account. AI features use providers that you or your workspace connect with your own API key: OpenAI, Anthropic, Groq, Together AI and OpenRouter, or OpenAI-compatible providers reviewed by Neuphlo. Requests go to the provider's API under the account owner's own terms. For OpenAI we send store: false; for Neuphlo's hosted chat/text adapter using OpenRouter, we request only endpoints that do not collect data for training (data_collection: "deny"). Workspace-configured OpenAI-compatible provider profiles use their own provider settings. Google user data is never part of these requests.
Local and self-hosted models. With Neuphlo Connect you can run agents on your own device, such as Codex, Claude Code, Hermes, OpenCode or local Ollama models. Ollama models run on your device, except Ollama cloud models, which run on Ollama's servers under your own Ollama account. Neuphlo's servers and the model vendor never contact local Ollama models. Where supported, Codex, Claude Code, Hermes and OpenCode run under your own account with that provider; their training settings are governed by your plan. These runtimes run on your device but may send prompts to a cloud provider (for example OpenAI or Anthropic). Local and self-hosted models used with Neuphlo never receive Google user data. Google user data is never sent to Connect devices or to any of these runtimes.
10
Connected AI, devices, and tools
Neuphlo Connect pairs a device and exposes configured cloud or local runtimes, such as Codex, Claude Code, or selected local models. A person or authorised workspace configures Phlo bindings, model consent, sharing, approved project folders, tools, and connected services.
For a cloud runtime, the selected prompt, context, instructions, files, and operation data are sent to the chosen provider. For a local runtime, model or tool execution occurs on the paired device, but Neuphlo-hosted infrastructure may relay prompts, selected context, instructions, outputs, approvals, questions, and operation events between the web app and the device. Workspace messages, files, outputs, and provenance that are shared through Neuphlo may still be stored and synchronised by Neuphlo. A local runtime therefore does not mean that all related data stays only on the paired device.
When tool use is enabled, providers and paired-device owners may receive project paths, file content, connected-service content, tool inputs and outputs, and approval decisions. Tool operations may change local or connected files and services according to the permission granted.
11
External content requests
When you view a link, resource, favicon, preview, image, or other externally hosted content, your browser or a connected service may automatically request it from the external origin. That origin may receive information ordinarily sent with a web request, such as your IP address, browser or device details, request time, and, depending on browser policy, a referring URL. The external origin handles that information under its own terms and privacy notice.
12
International transfers
Neuphlo, our service providers, paired devices, and providers selected by you or your workspace may process data in different countries. Processing locations can change and depend on the provider, deployment, account configuration, and operation. Where Neuphlo is responsible for transferring personal data from the European Economic Area to a country without an adequacy decision, we use standard contractual clauses or another lawful transfer mechanism as required. A provider or device you connect may process data in the locations and under the safeguards described in that provider’s own documentation.
13
Retention and deletion
We do not apply one fixed retention period to every category. We keep data for as long as reasonably needed for the purpose described above, while an account, workspace, connection, or subscription is active, and afterwards where needed for security, support, dispute resolution, legal claims, tax or accounting obligations, enforcement, and service integrity. We consider the nature and sensitivity of the data, the risk of harm, technical dependencies, contractual commitments, and legal requirements when deciding how long to retain it.
Account deletion is currently handled by request to help@neuphlo.com. We verify the requester and handle the request under applicable law. We may retain or restrict rather than delete data where an organisation controls the workspace, another person’s rights would be affected, the content forms part of shared history, a legal obligation or claim applies, security or fraud records are needed, or another legal exception permits retention. Shared messages, Room history, Work, Pages, files, outputs, and activity may remain available to authorised collaborators. We de-identify data only where appropriate and reasonably feasible; we do not promise that every retained record can be anonymised.
Backup copies may retain a record after deletion from active systems. They are not used as active service data and may remain until they are overwritten or deleted. We do not promise a universal backup period.
The web app and paired apps use local databases and browser storage, including SQLite-backed offline data and IndexedDB file staging where supported. Local copies can remain on a device after sign-out, account deletion, or removal from a workspace until the app or browser clears or overwrites them, or the device owner removes the app or site data. People and organisations that control those devices are responsible for managing those local copies.
14
Your data-protection rights
Subject to the GDPR and other applicable law, you may have rights to be informed, access personal data, correct inaccurate data, request erasure, restrict processing, receive portable data, object to certain processing, withdraw consent where consent is used, and complain to a competent supervisory authority. Pages offer direct export, but Neuphlo does not promise a complete self-service account export.
Requests can be sent to help@neuphlo.com. We verify requests as appropriate and respond within the periods and to the extent required by applicable law. We may ask for information needed to confirm identity or authority. Rights can be limited by legal exceptions, another person’s rights, an organisation’s instructions where it is the controller, or the need to retain data for legal obligations or claims. You may also complain to the Danish Data Protection Agency or the supervisory authority where you live or work.
15
Security
We use technical and organisational measures intended to protect personal data and proportionate to the relevant risk. Depending on the system and feature, these measures may include encrypted transport, authentication, access controls, scoped permissions, provider restrictions, and logging. No measure or service can guarantee absolute security. You should protect your sign-in links, connected accounts, approved project folders, and devices and contact us promptly if you suspect unauthorised access.
17
Changes to this notice
We may update this notice as the service, our providers, or applicable law changes. We will post the revised notice and update the date above. For material changes, we will provide reasonable notice by email, in the service, or both before they take effect where required by law.
18
Neuphlo Growth
The general notice applies. These sections add what is specific to each product.
Neuphlo Growth stores only what sign-in and the catch list need. When you sign in with Google, we store your email, your name, and your avatar.
For the conversations you keep, we store the link, the author, the excerpt, the draft, and whether you posted or skipped it.
Your API token is stored as a hash. We cannot show it again. Regenerating replaces it.
We do not sell your data. We do not post to X or Reddit for you.
Questions about Neuphlo Growth can be sent to hello@neuphlo.com.
19
Photos by Neuphlo
The general notice applies. These sections add what is specific to each product.
Photos by Neuphlo is guest photo and video sharing for events. Owners sign in with Google or an email magic link. There are no passwords. Guests do not need an account.
Photos and videos are stored in object storage or on our server. We read the EXIF capture time to order photos.
A gallery is deleted 30 days after its last upload. We email the owner 3 days before.
The paid plan is charged through Stripe Checkout. Card details never touch our servers.
Questions about Photos by Neuphlo can be sent to hello@neuphlo.com.