Privacy policy
Who processes the data
Producciones Multimedia Anfibic, S.L., whose contact details appear in the legal notice, is the controller of the data needed to manage its direct relationship with customers, answer enquiries and suggestions and meet its own legal obligations.
Where an organisation uses Mopux to manage data on its own behalf, that organisation determines the purposes and Anfibic provides the service under the applicable data processing agreement. Requests concerning that content will be handled with the relevant organisation. This distinction depends on actual use and does not make Anfibic responsible for every decision made by the customer.
Free trial and beta installations
New installations have a 15-day trial without a payment card or automatic charge. Without a subscription, operations are blocked at expiry and data is retained for 15 additional days to allow subscribing and restoring access; it is then deleted from the active environment. Earlier backups follow the retention cycle described in this document. Existing beta installations keep their configuration free of charge until their owner expressly chooses a paid plan.
Shared public demo
The demo lets visitors explore Mopux without registering, using shared administrator, internal team and external collaborator accounts. It does not create a personal installation or start the 15-day free trial. The template contains fictional data. Do not enter personal, confidential or customer data: other visitors using these accounts can view or change content available to their profile, and activity is attributed to the shared account, not reliably to an individual.
The demo is configured to block file uploads, outgoing email, account management, billing and API, MCP or OAuth access. Sample documents are provided from a private template. Working content is reset nightly from that template; visitor changes are not retained in the active environment after a successful reset. The notice shows the next reset when reliable information is available; a failure may temporarily put the demo into maintenance. A reset does not immediately erase technical logs or earlier backups: the cycles described in this policy apply.
Anfibic is the controller of demo access, session, security and diagnostic data needed to provide the requested demonstration and protect the service, under the legal bases described in this policy. The session, security and preference cookies described in the cookies section apply. The demo is not a private workspace for processing data on a visitor's behalf; to work with your own data, create an installation and complete the applicable registration and agreements.
Data, sources and purposes
Mopux processes information supplied by users and entered by other authorised users of their installation: identification and contact details, profiles, project membership, tasks, assignments, comments, mentions and files. Technical access, operational and diagnostic data are also generated.
Data are used to provide the service, manage accounts and permissions, send service notifications, provide support and maintain security. Mopux emails are not used for advertising campaigns.
Anfibic does not reuse the content of customer installations for advertising, training artificial intelligence models, commercial analysis or purposes unrelated to providing, maintaining and supporting Mopux. This statement describes Anfibic's use; the optional ChatGPT connection is addressed separately below.
Paid plans and billing
When a paid plan is contracted, Anfibic processes the contact and billing details provided, selected plan, additional users, amounts, invoices and payment status to manage the contract, collect fees, issue invoices and meet accounting and tax obligations. The legal basis is performance of the contract and, for tax and accounting obligations, compliance with legal obligations. Stripe is used to process payments, and the data necessary for that purpose is shared with it. Depending on the specific service, Stripe and its affiliated entities may process data as controllers or processors, under their applicable terms and privacy documentation.
Improvement suggestions
Submitting a suggestion through the feedback system creates a task in the feedback project of Mopux's internal installation. The suggestion and information identifying its sender and installation are collected so that clarification can be requested.
Acknowledgements in release notes will be generic, without naming the person who suggested the improvement; for example, “Thank you for the suggestion”.
Contact details and the installation reference are retained for as long as needed to assess the proposal and resolve questions. Once that follow-up ends, identifying references are removed from the task and its comments. The functional description of an accepted or deferred improvement may be kept for product planning without information identifying its sender. If a task is rejected and deleted, earlier copies follow their expiry cycle. Deleting the originating installation does not itself delete the feedback task in Mopux's internal installation.
Grounds for processing
| Purpose | Ground and scope |
|---|---|
| Managing registration, service and cancellation contracted directly by an individual | Performance of the service relationship or pre-contractual steps requested by that individual. This ground does not automatically extend to all invited users. |
| Maintaining relationships with representatives and professional contacts of customer organisations | Legitimate interest in managing that professional relationship, using necessary contact details. |
| Answering support enquiries and improvement suggestions | Performance of the service relationship where the enquiry comes from the individual who holds it; otherwise, legitimate interest in answering enquiries and improving the service, limited to necessary data. Access to installation content is on the customer's behalf and under its instructions. |
| Handling rights and Anfibic's own legal obligations | Compliance with applicable obligations. |
| Protecting shared infrastructure and detecting service faults | Legitimate interest in service security and continuity, with limited technical data and restricted access. Security and diagnostic operations on data managed on the customer's behalf fall within the processing engagement. |
| Managing invited accounts, permissions, projects, members, tasks, files and installation notifications | Anfibic acts on the customer's behalf; the customer determines the purposes and legal grounds of its processing and informs data subjects. |
You may object to processing based on legitimate interests on grounds relating to your particular situation, using the channel in the rights section.
Required and optional information
Creating an installation by invitation requires a name, email address, password and installation name, from which its subdomain is derived. Registration cannot be completed without the required fields.
When joining an installation by invitation, the email address comes from an invitation sent by an authorised user; the invitee supplies their name and sets their password. The login form requires an email address and password. A profile picture is optional and is not required to use the account.
Members' data and permissions, and project and task content, are managed within each installation according to the customer's chosen use. The customer must explain the data it requests for that use.
Support and rights requests require enough information to identify the request and respond. Essential missing information will be requested; identity documents are not routinely required.
Support and access to content
Support is provided at support@mopux.com using Google Workspace. Depending on the issue, a follow-up task may be opened in Mopux, transferring only necessary information.
Before viewing installation content for support, Anfibic will request the owner's authorisation. The email exchange will retain that authorisation, its date and a brief description of the intervention, without copying customer content. Access is limited to what was authorised. This procedure is distinct from ordinary technical operations needed to provide the service.
Providers
| Provider or service | Purpose and data involved |
|---|---|
| DigitalOcean | Server hosting in Frankfurt and automatic weekly backups in the same data centre, according to the provider's documentation. Attachments are stored separately in DigitalOcean Spaces, Frankfurt region (fra1). This location does not mean that all associated processing takes place exclusively in Europe. |
| Stripe | Payment processing and management of the information needed to handle recurring fees and payment status. Stripe and its affiliated entities may act as controllers or processors depending on the specific service. International processing and subprocessors may apply under Stripe's contractual and privacy documentation. |
| Scaleway SAS (Transactional Email, France) | Notification delivery: recipients, subject and content, which may include names and project and task titles, and delivery metadata. Its documentation states that TEM is hosted and processed in the EU; this does not cover recipients' email providers. According to Scaleway’s clarifications, each message’s body and attachments are deleted from active systems upon successful delivery or the definitive outcome applicable to a failure (for example, a hard bounce, final spam classification or blocklist purge). Residual copies are deleted within seven days of that deletion, even while the account and domain remain active; this period does not necessarily start at sending. Recipient addresses, delivery and activity logs and sending metadata are retained while the TEM domain or account is active; deleting the domain or closing the account starts the deletion process for these categories. Closing a Mopux installation does not close the shared TEM account. Blocklist entries are purged 15 days after the block is lifted or resolved. Individual content-deletion requests are handled manually through privacy@scaleway.com; the provider states that delivery or activity logs and blocklist entries cannot be deleted individually. |
| Google Cloud EMEA Limited (Google Workspace, Ireland) | Receiving and retaining support emails, contact details, authorisations and attachments sent to support. A private Google Sheets spreadsheet also maintains a minimal cancellation register (installation ID and date) to prevent deleted installations from reappearing after a restore. Europe is selected for covered Google Workspace data at rest; this does not imply exclusively European processing. |
Mopux installations and the shared demo do not include Google Analytics. The public website may use it only after analytics cookies are accepted, as explained below. Providers may retain operational service records and historical data from previous messages.
These providers may process data outside the European Economic Area. The Mopux server's location does not determine that of every service. Transfers must be covered by an adequacy decision or applicable safeguards, such as standard contractual clauses and necessary supplementary measures. You can request information about safeguards applicable to your data at support@mopux.com.
Optional connection to ChatGPT
Users choose their installation, authenticate in Mopux and authorise permissions through OAuth. ChatGPT may receive user, project, task, group and member information according to the tools and permissions used. Authorised write actions make real changes in Mopux.
The connection is available only on plans that include it; Esencial includes no access to connectors or AI features, while Equipo includes the AI plugin. A medida is governed by its offer. The internal AI chat is not offered at this stage.
Passwords are entered in Mopux. Access can be withdrawn through “Connected applications” in the user menu. Revocation prevents use of revoked credentials, but does not delete information already included in conversations or undo completed operations.
The connection uses the ChatGPT account or workspace chosen by the user. Before enabling it, users must review that product's terms and data controls and, when working for an organisation, the authorisations it requires for sharing its information. Technical OAuth authorisation does not replace those checks.
Anfibic does not determine conversation retention or data-use settings in the ChatGPT account. There is no general guarantee against training or of exclusively European storage for every account that can connect.
For EEA users, including Spain, the European terms for individuals identify OpenAI Ireland Ltd as the provider. Its European privacy policy identifies it as controller for the processing described there and distinguishes business content processed on customers' behalf.
ChatGPT Business and Enterprise accounts are governed by the services agreement and, for personal data processed on the customer's behalf, its data processing agreement, which provides for OpenAI as processor of that data. The contract and configuration of the workspace used must be checked.
According to OpenAI's connected-app information, information obtained through apps in Free, Go, Plus and Pro may be used to train models when the option to improve the model for everyone is enabled. Business, Enterprise and Edu do not use it for training by default. Disabling that option does not delete conversations or establish European residency.
Anfibic operates the Mopux integration; OpenAI provides ChatGPT under its relationship with the user or organisation. The app developer terms distinguish those relationships and do not establish a controller–processor relationship between the parties merely through developing the app. Anfibic retains its obligations regarding access and processing in Mopux.
Retention and cancellation
Attachments are stored in DigitalOcean Spaces, separately from the server disk. The four-week cycle below applies to server backups, not automatically to Spaces. Anfibic confirms that these objects have no versioning or additional backups. Cancellation includes deletion of the installation's attachments.
Cancellation is requested through support and requires verification of the owner's identity and confirmation. If someone else requests it, the owner is contacted before proceeding. It is processed within one to two working days of verification and confirmation.
The installation, database and files are deleted from the active environment. They may remain in earlier backups until expiry under the four-week weekly-backup cycle. This retention does not guarantee recovery of an individual installation.
A minimal register of installation IDs and cancellation dates prevents a restore from recovering deleted installations. Each entry is removed only after checking that no recoverable copy remains, including any manual snapshots.
Administrators and managers with project access can export it as JSON, including project details, groups, tasks, comments, mentions and members. Comment attachments are represented by references and metadata: files must be downloaded separately before cancellation. The export is not a complete installation backup.
Emails and tasks for ordinary support enquiries are retained for 12 months after closure and then deleted. Access authorisations, security incidents and claims are handled separately. Only what is necessary to handle the case is kept while it is open. On closure, unnecessary supporting material is deleted and access is restricted to evidence needed to demonstrate actions, meet obligations or address liabilities. Expiry depends on the specific obligation or liability and its applicable period, considering open proceedings and possible interruptions of limitation periods. Retention is not indefinite, nor does the ordinary support period apply automatically.
Minimum evidence of handling rights requests is retained for three years after closure, accessible only to Anfibic's authorised person. It includes necessary requester identification, request scope, receipt and response dates, the response and proof of sending or forwarding to the relevant controller. Exported files and supporting identity documents are not retained by default: they are deleted when no longer needed to handle the request. Where a claim is open, necessary evidence is retained until resolution and for the applicable period for resulting liabilities, with the exception documented.
Project activity history is retained throughout the installation's life as part of its work history. It is deleted from the active environment with the database on cancellation; previous copies follow the backup cycle above. Technical-log rotation does not apply to it.
Laravel is configured to retain up to 14 daily diagnostic files through rotation. Nginx rotates daily and retains 14 rotated files plus the active file, without rotating empty files. These file limits do not guarantee deletion after 14 calendar days: this depends on activity and rotation execution. Earlier server backups may contain those files until the stated backup cycle expires.
Cookies and preferences
Mopux uses first-party cookies to maintain sessions, protect requests and retain browser interface settings.
| Cookie | Purpose | Duration |
|---|---|---|
| mopux_session_host_v1 | Maintaining the login session. | Session configured for 120 minutes of inactivity. |
| XSRF-TOKEN | Protecting against forged requests. | Expiry configured in line with the 120-minute session period. |
| mopux_app | Remembering the chosen language, theme saved from the profile and comment display setting. | 365 days from issue or update. |
| “Remember me” cookie (technical name prefixed remember_) | Remembering access on the device when selected at login. | Up to 400 days; access may be invalidated earlier. |
The default language is applied without creating a preference cookie. Choosing another language saves that choice. The theme is saved when submitting the profile form with a valid selection; comment display is saved when changed. Viewed-news status is stored in account preferences on the server and shared across the same user's devices. A cookie is no longer used for this status.
“Remember me” is initially unchecked. Its purpose, duration and deactivation are explained alongside the option. Choose “Log out” in the user menu to disable remembered access. This option does not change the ordinary session period.
Cookies can be deleted in browser settings, which may log you out and reset settings stored in that browser. Old preference cookies retain their expiry until replaced, deleted or expired. Their former viewed-news indicator is no longer used.
The public maintenance page serves fonts from Mopux. Libraries for task, project and focus screens are also served from Mopux.
Rights
Where applicable, you may exercise rights of access, rectification, erasure, objection, restriction and portability by emailing support@mopux.com. State your request and, where relevant, the Mopux installation concerned; no specific form is required. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing.
Exercising rights is generally free. An identity-document copy is not routinely requested: if there are reasonable doubts about identity, only additional information necessary to confirm it will be requested.
Where Anfibic acts as controller, it will respond without undue delay and within one month of receipt. Complexity or the number of requests may justify an extension of up to two further months; the extension and reasons will be communicated within the first month. If a request is not fulfilled, reasons and available complaint and challenge procedures will be provided.
Where a request concerns data processed on the installation customer's behalf, Anfibic will forward it to the relevant controller and assist under the processing agreement. You may lodge a complaint with the Spanish Data Protection Agency.
Cancelling an entire installation and exercising individual rights are separate procedures. Exercising rights over your own data does not require ownership of the installation and does not entail deleting other users' data.
Optional analytics on the public website
When enabled, Google Analytics 4 (Google Ireland Limited) measures visits, pages, general referral sources, “Try free” clicks and completed signups. Consent is the legal basis: Google code does not load before acceptance or after rejection. Advertising and Google Signals are disabled. Names, email addresses, installation content and account IDs are not sent; measured URLs exclude query parameters and private signup references. Google receives technical connection and browser data and uses cookie identifiers; this does not mean the data is anonymous.
The first-party analytics cookies _ga and _ga_* are restricted to the public website host and configured for 180 days without automatic renewal on each visit. Your choice is saved in browser local storage as mopux.analytics.v1 for 180 days. A local session-storage marker prevents repeating a completed signup and is not sent to Google. You can accept or reject with equal ease and change or withdraw consent through “Cookie settings”. Withdrawal stops measurement and deletes that host’s analytics cookies; it does not delete previously transmitted data.
Google may process data outside the EEA under the terms and safeguards applicable to its service. See Google’s Analytics information and data processing terms. Google retention depends on property settings; cookie expiry does not determine report retention. The intended setting before activation is two months for event and user data, without resetting on new activity; aggregated reports follow their own rules.