Privacy Policy

FieldMosaic is a web application for documenting field work — customers, sites and areas, jobs, visits, observations, checklists and photographic evidence — and for generating Word (.docx) reports from that information. FieldMosaic is provided by CloudFM Solutions, Lda, with registered office at Rua Cimo da Vinha, 40-C, 7300-658 Fortios, registration number PT510123864 and VAT number PT510123864 (“FieldMosaic”, “we”, “us”).

For the personal data needed to run FieldMosaic itself — accounts, sign-in, access requests, billing, security, support and our website — we are the controller.

For the information that a subscribing organization and its users record in FieldMosaic about their own work (“Customer Data”), the organization is the controller and we process that data on its behalf as a processor. If you are a member of an organization, or a person whose information appears in an organization's records or photographs, please contact that organization first about that information. We will help it respond.

You can contact us about privacy at support@cloudfmsolutions.com.

Account and sign-in data

FieldMosaic does not use passwords. You sign in with a Google or Microsoft account. When you do, we receive and store your name, your email address and the unique account identifier issued by Google or Microsoft (for Microsoft, also the identifier of your organization's directory, known as the tenant). We also store your preferred language, the organizations you belong to, your role in each one and the status of your access.

We never receive your Google or Microsoft password, and we do not store your profile photo.

Organization data

When an organization is created we store its name, country and language and, if an Owner or Administrator adds them, its address, postal code, city, email, phone, website and logo, which can appear in the reports it generates. We also store the organization's settings, Word report templates, checklist templates, team members and roles, and its plan and subscription status.

Access and trial requests

Access to a FieldMosaic workspace is reviewed before it is granted. If you request a trial on our website we collect your name, email address, company, team size and language and, if you provide them, your phone number and a message. If you sign in without access to a workspace, we record an access request with your sign-in details. We keep the status of each request and the outcome of our review.

If you send an Enterprise enquiry through our contact form, your name, email address, company, team size and message are sent to our team by email. They are not stored in the FieldMosaic application database.

Customer Data recorded in FieldMosaic

Depending on how the organization uses FieldMosaic, its users may record:

• Customers: name, email, phone, business identifier, address and notes;
• Sites and areas: names, addresses, optional coordinates, descriptions and notes;
• Jobs: reference, title, description, status, schedule and assigned users;
• Visits: dates, status, general notes, weather and the technicians involved;
• Observations: title, description, category, severity, status, location and recommendation;
• Checklists: templates, answers and notes;
• Evidence: photographs (JPEG, PNG or WebP) and PDF documents, with their original filename, size, an integrity fingerprint (SHA-256), who uploaded them and when;
• Reports: every generated Word report version, with a snapshot of the data it was generated from.

Customer Data can include personal data about people who are not FieldMosaic users — for example a customer's contact person, the occupants of a building or anyone visible in a photograph. The organization is responsible for having a lawful basis to record that information (see our Terms of Service).

We keep each original evidence file exactly as uploaded, so that its integrity can be verified. Photographs can contain metadata written by the camera or phone, such as the capture date, the device model and, if location tagging is enabled on the device, GPS coordinates. The native mobile camera and photo-library components may read image metadata while preparing the selected file. FieldMosaic does not display GPS coordinates or request location-service access for this flow; embedded metadata can remain inside the stored original file. The smaller preview image created by the client for display does not keep it. If you do not want location data inside your photographs, turn off location tagging in your camera settings.

Storage connection data

If an Owner or Administrator connects Google Drive, Microsoft OneDrive or SharePoint, we store the connected account's email address and identifier, the identifiers and names of the destination folder, site or library, and the authorization tokens needed to keep the connection working. Tokens are stored encrypted. The Google and Microsoft sections explain these connections in detail.

Billing data

Paid subscriptions are processed by Stripe. When an Owner starts a subscription, we send Stripe the organization's name, the Owner's email address and our internal organization identifier. We store the Stripe customer and subscription identifiers, the plan, price, currency, billing interval, subscription status and the related dates. Payment card details are entered directly with Stripe; we do not receive or store card numbers.

Technical, security and usage data

• Session records: when a session was created, when it was last used, when it expires and which organization is active;
• An activity history (audit log) of actions in each organization — for example records created or deleted, evidence uploaded, reports generated or storage connected — with the user and time;
• Internal product events, such as the first job or visit created by an organization, linked to the organization and user, which we use to understand how the product is adopted only after analytics acceptance; operational audit logs remain independent of this choice;
• Operational logs generated by our hosting platform, which may include technical request information such as IP address, browser type, the requested page and errors;
• For trial requests, a daily value derived from your IP address in a non-reversible form (a keyed hash), used to limit abuse and valid for 24 hours;
• Aggregate statistics about our public website: how many times a named event (for example “pricing page visited”) occurred on a given page and day. These statistics contain no IP addresses, cookies, user identifiers or browser details. Browser events, form-completion counts and optional internal product events are recorded only after your analytics acceptance. When configured and accepted, Cloudflare Web Analytics also receives page and referrer information and browser performance measurements, such as loading times and Core Web Vitals, on allowlisted public pages. Cloudflare Web Analytics is excluded from account and operational pages and private evidence links; pages with query strings or fragments are not measured.

Communications

We keep the emails we exchange with you, for example about an access request or a support question.

The native iOS application can keep photographs saved on the device, upload-operation metadata and cached data used by visited work screens in its own encrypted storage. Its encryption key and sign-in credential are held in the iOS Keychain. These are separate from the browser's cookies. Access is scoped to the application, backend, account and organization; the application does not automatically import another application's sessions or upload queue.

A photograph saved on the device is not sent merely because it was captured. After you choose to send it, the existing queue may process it, retry an eligible interrupted transfer or check its outcome when connectivity returns. Until upload is confirmed, a photograph stored only on the device is not a server backup. Removing the application or losing access to the device or its key can make unsent data unavailable; we do not guarantee recovery of the Keychain from a backup.

The local queue diagnostic shows the current operation state, timestamps, attempts, a random operation identifier and limited error categories. It is not a complete history. This diagnostic has no automatic remote exporter in the current application. An operation identifier can be linked to a server operation if the diagnostic is later shared; it must not be treated as anonymous. Platform-level diagnostics and security validation performed by iOS are separate and depend on Apple's services and your device settings.

An authorized manager of a customer organization can create an Evidence Request associated with its work, optionally storing the recipient's name and email and sending a transactional email or sharing the link directly. The recipient does not need a FieldMosaic account. The link grants access to anyone who has it; it is not proof of identity. Its expiry is shown on the form, normally 30 days after creation. Resending rotates the link; cancellation or acceptance invalidates it.

Opening records the first-open time. Submissions contain checklist answers, photographs and previews, optional submitter name/email, timestamps and version history. Original photographs can retain camera metadata, including location. The requesting organization receives the submission for review before acceptance. Earlier submissions can be superseded; media awaits review and, when accepted and linked to an existing work context, becomes operational evidence available for reports. Requests for changes permit resubmission within the displayed limits.

For abuse prevention, daily keyed hashes derived from IP addresses and the request token are held in rate-limit records. Read windows expire after one minute and write windows after one hour; expired records are removed during later requests, rather than exactly at expiry. Application error logs redact tokens and identifying details, while infrastructure security logs remain subject to provider settings. Optional website analytics never runs on these private links.

The organization that requested the evidence is the controller for its content and determines the purpose, legal basis and retention. Please contact it about that processing or your rights; CloudFM processes the content on its behalf and assists it. A short notice identifying the requesting organization and linking to this policy is shown before upload.

We use personal data only for the following purposes:

• to provide FieldMosaic: create and manage workspaces, store records and evidence and show them to authorized users;
• to authenticate you, keep you signed in and apply your role and your organization's permissions;
• to review access and trial requests and set up approved organizations;
• to store files in the storage provider connected by your organization or, where CloudFM has activated it for your organization, in CloudFM Managed Storage;
• to generate Word reports from the visits, jobs and information that users select;
• to manage plans, subscriptions and plan limits, such as the number of users and monthly reports;
• to send transactional emails, such as a notice that your access request was approved, and to answer enquiries;
• to provide support when you ask for it;
• to protect the service, our users and their data: checking that public forms are submitted by people, limiting abuse, investigating incidents and keeping an activity history;
• to understand, in aggregate, how the website and the product are used, so that we can improve them;
• to comply with legal obligations, such as accounting and tax rules, and to establish or defend legal claims.

We do not sell personal data. We do not use personal data or Customer Data for advertising, and FieldMosaic does not send marketing emails from the application. If we want to use personal data for a new purpose that is not compatible with these, we will update this policy first and, where required, ask for your consent.

Under the General Data Protection Regulation (GDPR) we rely on the following legal bases:

• Performance of a contract (Article 6(1)(b)): providing the account, sign-in, workspace, storage, reports, billing, transactional emails and support, and taking the steps you ask for before a contract, such as reviewing a trial request;
• Legitimate interests (Article 6(1)(f)): keeping the service secure and preventing abuse, keeping an activity history, understanding aggregate use of the website and the product, communicating with business contacts about the service, and establishing or defending legal claims. We balance these interests against your rights, and you can object (Your rights);
• Legal obligation (Article 6(1)(c)): keeping billing and accounting records and responding to lawful requests from authorities.

Optional website and authenticated-product statistics, including Cloudflare Web Analytics when configured, run only after your acceptance; where personal data is processed for that purpose, we rely on consent (Article 6(1)(a)). You can withdraw it in Cookie settings without affecting earlier processing. Necessary product records and security processing have the separate bases described above. Connecting storage requires authorization on the provider's screen, which you can withdraw; that permission is separate from these legal bases.

For Customer Data, the organization, as controller, determines the legal basis for recording information about its own customers, contacts and other people. We process that data on the organization's behalf to provide the service.

FieldMosaic uses Google in two separate, optional ways: signing in with Google, and connecting Google Drive as the storage destination for an organization's files. Each requires its own consent on Google's screen.

Sign in with Google

When you choose “Continue with Google”, FieldMosaic requests the openid, email and profile scopes. From Google we receive your Google account identifier, your email address, whether that address is verified and your name. We use this data to identify you, check whether you have workspace access and keep you signed in. Existing Google identities are recognized by the Google provider and stable account identifier (sub). When that identity is new, FieldMosaic creates a user or activates an account prepared through the organization’s invitation process using the verified email. The same email address does not merge existing Google or Microsoft identities. Sign-in does not give FieldMosaic access to your Gmail, Calendar, Contacts, Drive or other Google data, and we do not keep the Google access token issued at sign-in.

An Owner or Administrator can connect Google Drive in Settings. FieldMosaic then requests the scope https://www.googleapis.com/auth/drive.file, which only gives access to files and folders that FieldMosaic creates or that you explicitly open with FieldMosaic. It does not give FieldMosaic access to your other Drive files.

When the connection is made and while it is in use, FieldMosaic:

• receives the connected Google account’s email address, display name and Drive permission identifier. The email and permission identifier are stored to show the connected account and avoid linking files to the wrong account; the Drive display name is not stored in the connection record;
• creates a FieldMosaic folder in that Drive and, inside it, subfolders organized by job, visit, area and observation. Folder names can include the job reference, the customer and site names, the visit date and the area and observation names;
• when Google Drive is the organization's active destination, uploads the organization's evidence files (originals and previews), generated Word reports, Word templates and logos to that folder; reads them back to show them in FieldMosaic and to build reports; and deletes them when an authorized user deletes them and the organization's settings ask for files to be removed immediately;
• stores a Google refresh token encrypted with AES-GCM, with a fresh random initialization value and a key configured separately from the database, so that the connection keeps working without asking for consent each time. Access tokens obtained on refresh are used by the server for Drive requests.

FieldMosaic accesses Google Drive only to carry out actions that a user of the organization starts or configures, such as uploading evidence, generating a report or opening a file. It locates its managed folders and files within that permission; it does not index the rest of your Drive or request full-Drive access.

When the integration is used, file contents and folder/file names are sent to Google to store, retrieve or remove those files. Files remain subject to the connected account's sharing settings and Google's terms. FieldMosaic does not make them public automatically. In Cloudflare D1 we retain the connection identifier, connected account email and Drive permission identifier, folder/file identifiers and names, logical storage keys, MIME type, size, integrity hash, uploader/time and report snapshots. Google Drive also receives private appProperties marking managed files and their organization, connection and logical key; these are application metadata, not a search index of your Drive.

Disconnecting and revoking access

An Owner or Administrator can disconnect Google Drive in Settings. FieldMosaic then asks Google to revoke the authorization, removes its stored authorization tokens and stops storing new files through that connection. The remote revocation is best effort: if Google cannot confirm it, the local disconnect still completes, and you should remove the permission in your Google Account. Connection and file metadata remain with the organization records until their authorized deletion. New files are not moved to any other storage automatically: until an Owner or Administrator configures another destination, actions that need to store files are unavailable. Files already in Drive stay there. You can also check or remove the permission yourself at any time on your Google Account permissions page. While access is revoked, files previously stored in Drive are not available in FieldMosaic.

• The application uses Google user data for the visible sign-in and connected-storage features described above, not for unrelated profiling;
• We do not sell Google user data;
• We do not use Google user data for advertising, including personalized, retargeted or interest-based advertising;
• We do not transfer Google user data to third parties, except where necessary for these visible features with your consent (including the hosting providers identified under Service providers), for security, where required by law, or for a merger, acquisition or sale of assets after your explicit prior consent;
• Our staff do not read Google user data unless you explicitly agree to access to the specific files or data concerned (for example, to resolve a support request), it is necessary for security purposes such as investigating abuse, or it is required by law;
• We do not use Google user data to develop, improve or train generalized artificial intelligence or machine learning models.

These restrictions describe the permitted use of Google API data in FieldMosaic, including the Limited Use restrictions in the Google API Services User Data Policy. Connecting Drive does not grant consent to use its data for other purposes. To withdraw access or request deletion of the data held by FieldMosaic, see Google Drive Integration, Account and data deletion and Your rights.

FieldMosaic can also use Microsoft in two separate, optional ways: signing in with Microsoft, and connecting Microsoft OneDrive or SharePoint as the storage destination.

Sign in with Microsoft

FieldMosaic requests the openid, profile, email and User.Read permissions. From Microsoft we receive your account identifier, the identifier of your organization's directory (tenant), your name and your email address or user principal name. We use them only to identify you, check your access and keep you signed in. Personal and work or school Microsoft accounts are accepted.

OneDrive and SharePoint connection

An Owner or Administrator can connect OneDrive or SharePoint in Settings. In addition to the sign-in permissions, FieldMosaic then requests offline_access, so that the connection keeps working. For OneDrive, FieldMosaic requests Files.ReadWrite, which is limited to the connected account's own files, so that it can create and write files in that account's OneDrive. For SharePoint, which requires a work or school account, FieldMosaic requests Sites.Read.All, used to find the SharePoint site whose address you enter and to list its document libraries and folders so that you can choose a destination, and Files.ReadWrite.All, the permission FieldMosaic has adopted so that it can carry out the storage operations it needs in the SharePoint document library you configure: creating the destination folder and its subfolders, and uploading, reading and deleting the files FieldMosaic manages there. Your Microsoft administrator may need to approve these permissions, in particular Files.ReadWrite.All and Sites.Read.All.

Files.ReadWrite and Files.ReadWrite.All are broad Microsoft permissions. Both are delegated: FieldMosaic acts only on behalf of the connected account and can never open more than that account can already open. Within that limit, Microsoft does not restrict Files.ReadWrite.All to one site or folder: it covers every file the connected account can access in OneDrive and SharePoint. FieldMosaic restricts its own use, for OneDrive and SharePoint alike, to creating or locating the destination folder you configure and its subfolders, and to uploading, reading and deleting the files FieldMosaic manages there: evidence files, previews, Word reports, templates and logos, organized in subfolders named after, for example, the job reference, customer and site, visit date, area and observation. When you configure a SharePoint destination, FieldMosaic also lists the document libraries and top-level folders of the site you indicate, so that you can choose one. Before reading or deleting a file, FieldMosaic checks that it is still inside the configured destination folder. FieldMosaic does not browse, index or analyze other files, and it does not use Microsoft application permissions, which would work without a signed-in account.

We store the connected account's identifier and email, the tenant, drive, site, library and folder identifiers and names, and encrypted access and refresh tokens.

Disconnecting and revoking access

An Owner or Administrator can disconnect OneDrive or SharePoint in Settings, which deletes the stored tokens. New files are not moved to any other storage automatically: until another destination is configured, actions that need to store files are unavailable. Files already stored remain in your Microsoft account. You can also remove FieldMosaic's access from your Microsoft account (personal accounts) or My Apps (work or school accounts), or ask your Microsoft administrator.

We apply the same commitments to Microsoft data as to Google user data: we do not sell it, we do not use it for advertising and we use it only to provide the features described above.

Records — such as customers, sites, jobs, visits, observations, checklist answers, file metadata and report snapshots — are stored in FieldMosaic's Cloudflare D1 database.

Files — evidence, previews, Word reports, templates and logos — are stored in the organization's active storage destination:

• the organization's Google Drive;
• the organization's Microsoft OneDrive;
• a SharePoint document library chosen by the organization; or
• CloudFM Managed Storage (file storage hosted on Cloudflare R2), an optional service that is not active by default, cannot be activated by the organization itself and is available on request, subject to CloudFM's approval and specific contractual terms.

Google Drive, OneDrive and SharePoint are the standard providers and use accounts connected by the organization itself. There is no default destination: until the organization configures a valid one, actions that need to store files — such as uploading evidence, receiving Evidence Request submissions or generating reports — are unavailable. FieldMosaic never falls back automatically to CloudFM storage.

Only an Owner or Administrator can connect a provider or change the active destination. A change applies to new files; existing files stay where they were stored. Files kept in Google Drive, OneDrive or SharePoint are held in the organization's own account, under its settings and its agreement with that provider, and remain there if the connection is removed.

We use the following providers to run FieldMosaic. They process personal data only as needed for the service they provide:

• Cloudflare: application hosting, database and, for organizations using CloudFM Managed Storage, file storage; transactional email delivery, bot protection on public forms (Turnstile), operational logs and optional public-page Web Analytics when configured and accepted;
• Google: sign-in with Google and, when an organization connects it, Google Drive storage;
• Microsoft: sign-in with Microsoft and, when an organization connects them, OneDrive or SharePoint storage;
• Stripe: payment processing and subscription management for paid plans.

The role of each provider depends on the service. Cloudflare processes hosted Customer Data on our instructions. Under its Turnstile Privacy Addendum, it also acts as an independent controller for improving bot detection; this is separate from optional audience measurement. When an organization connects its own Google Drive, OneDrive or SharePoint, the provider holds those files under the organization's own account and agreement. Stripe may act as an independent controller for some payment data, under its own privacy policy. We will provide more details on request at support@cloudfmsolutions.com.

We may also disclose personal data to professional advisers bound by confidentiality, to authorities when the law requires it, or to a successor in a merger, acquisition or sale of assets, in which case we will inform you. Google API data additionally follows the explicit prior-consent restriction in Google API data and Limited Use.

Cloudflare and the other providers listed above operate global infrastructure. Hosting and storage locations depend on the service configuration and, for connected storage, on the organization's provider account. Some processing — for example request handling on Cloudflare's network, email delivery, sign-in, payments, or files an organization keeps in Google or Microsoft — may take place outside the European Economic Area (EEA), including in the United States.

When personal data is transferred outside the EEA, the applicable GDPR safeguard depends on the provider, service and agreement: a European Commission adequacy decision where applicable, or standard contractual clauses and any required supplementary measures. Cloudflare publishes its Data Processing Addendum and standard contractual clauses. These provider documents do not mean all processing occurs in the EU. Files in an organization’s own Google or Microsoft account additionally follow its provider agreement and chosen location settings. You can ask us for more information about these safeguards at support@cloudfmsolutions.com.

We keep personal data only for as long as it is needed for the purposes in this policy:

• Account data: while you have access to a FieldMosaic organization and afterwards for as long as needed to keep the organization's records accurate, for example to show who created a record or a report;
• Customer Data: while the organization is active or retains access after a subscription ends, until authorized deletion. Trial expiry stops new report generation but does not itself erase data. Automatic cleanup of expired unpaid trials is currently disabled; no automatic deletion exactly 30 days after trial expiry is promised. We will notify the Owner before any cleanup is activated. There is no automatic deletion deadline configured for cancelled paid organizations; contact us about return or deletion.
• Deleted records and files: when a user deletes a record or an evidence file, it is removed from the application. The organization's settings determine whether the stored file is kept for audit purposes (the default) or removed from storage immediately;
• Files in Google Drive, OneDrive or SharePoint: under the organization's control in its own account; they are not deleted when the connection is removed;
• Sessions: sign-in permission ends when you sign out. Web sessions expire up to 30 days after sign-in; current native mobile sessions expire after 7 days and are renewed through OAuth sign-in, without a dedicated mobile refresh token. Expiry prevents access; this is not a promise that the expired session record is erased at that instant. Account or organization deletion removes related session records;
• Local mobile data: cached work data has a 24-hour validity and expired copies are removed when read, or when the workspace cache is cleared. Offline workspace access is limited to a lease of at most 12 hours, bounded by session expiry; expiry of access does not itself erase every local file. After backend confirmation the queue removes photo bytes from that operation, but completed-operation metadata has no automatic deletion deadline. Temporary sharing files are removed after the share action and cleanup is attempted at startup; if cleanup fails, no fixed deletion time is guaranteed.
• Access and trial requests: for as long as needed to review the request and keep a record of the decision;
• Billing and accounting records held separately by Stripe or our accounting systems: according to applicable legal requirements; internal subscription records are deleted with the organization;
• Abuse-prevention values derived from IP addresses: trial limits use a daily keyed hash and 24-hour validity; expiry of a limit is distinct from removal of its stored record during maintenance;
• Operational logs: for the retention period applied by our hosting provider; this policy does not promise a fixed number of days. Diagnostic records may contain user, organization, operation or storage identifiers and integrity hashes and are not necessarily anonymous. Deleting application records does not by itself demonstrate erasure from independent provider logs;
• Public statistics and performance measurements: according to their purpose and the provider's retention settings; consent choices are stored for 180 days. No fixed analytics retention deadline is represented as configured.

We use technical and organizational measures appropriate to the nature of the data, including encrypted connections (HTTPS), access restricted by organization and role, server-side sessions, encryption of stored authorization tokens, integrity fingerprints for evidence files, an activity history and bot protection on public forms. Access to production systems is limited to the people who need it.

No online service can be completely secure. If a personal data breach is likely to affect your rights, we will notify the competent authority and, where required, the affected people and organizations, as the GDPR requires.

Under the GDPR you have the right to:

• access the personal data we hold about you;
• have inaccurate data corrected (rectification);
• have your data erased when there is no longer a reason to keep it;
• restrict processing in certain circumstances;
• receive the data you provided in a structured, machine-readable format and have it transmitted to another controller (portability);
• object to processing based on legitimate interests;
• withdraw consent at any time where processing is based on consent, without affecting earlier processing.

To exercise these rights, write to support@cloudfmsolutions.com. We may need to confirm your identity first. We will reply within one month, which may be extended in the cases allowed by the GDPR. If your request concerns Customer Data held by an organization, we will pass it on to that organization or help it respond, because it decides on that data.

You also have the right to lodge a complaint with a supervisory authority. In Portugal, this is the Comissão Nacional de Proteção de Dados (CNPD), www.cnpd.pt. You may also contact the authority of the EU country where you live or work.

Authorized users can delete many records directly in FieldMosaic — customers, sites, areas, jobs, visits, observations, evidence and reports — according to their role and to protections such as the lock on completed visits. Owners and Administrators can suspend team members and disconnect storage providers.

Owners can delete their organization at any time in Settings → Delete organization. The deletion is immediate and permanent: all of the organization's records and the files held in CloudFM Managed Storage are erased, and the members who belong to no other organization have their accounts anonymized. Files the organization keeps in its own Google Drive, OneDrive or SharePoint are not deleted by FieldMosaic and remain under its control. Deletion is blocked while a Stripe subscription is still active, including a cancellation scheduled for a future date. Internal subscription and webhook records are also deleted with the organization. This does not delete records held separately by Stripe or in accounting systems under their applicable retention rules. Download available reports and evidence before deletion; there is no whole-workspace export or promised recovery window.

Owners can also delete a user in Team. The user's access is removed and, if the person belongs to no other organization, the account is anonymized: name, email address and sign-in identifiers are erased. Records the person created stay in the organization — which is responsible for them — attributed to a deleted account; names that already appear as text in generated reports are not rewritten. Any person can also ask us to delete or anonymize their data at support@cloudfmsolutions.com; we will confirm your identity and respond within the legal deadlines.

With analytics consent, we use first-party session storage to attribute Trial requests to public landing pages, solutions, language, acquisition channels and validated UTM campaign labels. Only the referring hostname is kept; URL queries, fragments, click IDs, IP addresses and visitor identifiers are not recorded in attribution. The first and last acquisition touches are kept for a session with 30 minutes of inactivity, at most 24 hours, ending when the tab closes. On submission, attribution is optionally associated with the access request for 90 days; expired attribution is hidden immediately and removed by daily maintenance. Refusing analytics does not block a Trial or access request. Withdrawing analytics clears browser attribution and requests deletion of submitted attribution using a random deletion-only receipt held in the tab; this receipt cannot track visits. If that tab has closed, storage is unavailable or the deletion request fails, contact our privacy address to delete submitted attribution. Platform administrators can delete it without changing the request or approval. Deleting the account or organization also deletes associated attribution. We add no analytics provider, advertising cookie, fingerprint or cross-site identifier. Existing aggregate measurements already received are not erased by this withdrawal.

The Cookie Policy explains necessary session, OAuth, language and security technologies and optional public-page measurement and product usage statistics. Cloudflare Web Analytics does not use analytics cookies according to its documentation, but we still ask for your choice before executing optional statistics. Accept, Reject and granular Cookie settings are available, with withdrawal at any time. We do not use advertising cookies or browser local storage.

The trial and contact forms use Cloudflare Turnstile for security. Its script processes technical signals about the browser and device, such as IP address, user agent and connection characteristics. Under the provider's addendum, Cloudflare also uses signals to improve bot detection as an independent controller. Challenge cookies depend on infrastructure settings; we do not infer their existence or lifetime from the widget mode. This security flow is separate from optional analytics.

Our public website statistics are counted without cookies (section 2).

We will update this policy when FieldMosaic or the way we handle personal data changes. The “Last updated” date at the top shows the current version. If a change is significant, we will inform the Owners of active organizations by email or in the application before it takes effect.

Entity

CloudFM Solutions, Lda

Registered office

Rua Cimo da Vinha, 40-C, 7300-658 Fortios

Registration number

PT510123864

VAT number

PT510123864

Privacy

support@cloudfmsolutions.com

Support

support@cloudfmsolutions.com

For privacy questions and requests, write to support@cloudfmsolutions.com. For product support, write to support@cloudfmsolutions.com.