Review edition. Published for review on 22 November 2026. These are proposed policies, not accepted terms. Final wording and operational readiness remain under review. The private application remains protected.
FIELDWORK privacy notice — draft for review
Published review draft — not a final policy. Operator: Oliver James Poignand, sole trader. Prepared 22 November 2026; effective date will be set when approved for publication. Privacy contact: olipoignand@gmail.com.
FIELDWORK helps independent creatives manage projects, tasks, contacts, scheduling, business records and connected tools. This notice explains the information handled by the service and the choices available to its users.
Information handled
We handle the name, email and account identifiers used to sign in; workspace settings; and information you add to your workspace. Depending on your use, this can include client and supplier contact details, briefs, dates, notes, agreements, invoices, expenses, payment evidence, time entries and uploaded receipts. You are responsible for having an appropriate basis to add another person's information.
When you connect a provider, FIELDWORK receives authorisation tokens and an account identifier from that provider. It records the connection status and relevant checks. It does not ask for your provider password. The provider's consent screen explains the permission you grant. A provider account can have a different email from your FIELDWORK account.
Technical information can include authentication and security events, request information handled by our hosting provider, mutation and workflow audit records, and optional notification subscriptions. The current deployment records Worker invocation logs and sampled request traces; URL query strings are redacted. Hosting and authentication logs have their own provider retention periods. These are separate from workspace history and recovery backups; a short request-log period does not mean that your workspace records are erased.
How information is used
Information is used to provide your workspace, process actions you request, maintain record history, authenticate access, operate the selected integrations, diagnose failures and protect the service. Support or engineering work may require authorised access to relevant records; access should be limited to the work needed.
Existing native integrations can synchronise the project or task fields described in their permission screens. New account-only connections verify account access and, where offered, display a small read preview on request. Those previews are not automatically imported into FIELDWORK. File links do not by themselves copy the linked file into FIELDWORK.
We do not sell personal information, use it for advertising or behavioural profiling, or use customer content to train AI models. We do not authorise our AI providers to use that content for model training. These commitments also apply to information received through connected providers.
Service providers and optional features
Cloudflare supplies hosting, database infrastructure and the current Access sign-in. Uploaded receipt files may be sent to Cloudflare Workers AI when you request receipt extraction. If you request an AI project draft, the notes you submit are sent to OpenAI to generate suggestions. These are review tools; their outputs can be wrong and do not verify an agreement, tax treatment or payment.
When enabled and selected, connected services receive the information needed for the specific authorised action. Their terms and privacy notices also apply. Optional browser notifications use the browser's push service. User-configured automation endpoints or private feeds can disclose the fields shown in their separate approval step.
Email sending is not enabled in the current private build. If it is enabled later, this notice and the sending flow must explain which provider receives recipient details, message contents and attachments.
Our service providers operate internationally, and information may be processed or stored outside Australia. FIELDWORK does not promise Australia-only processing or storage. OpenAI may retain API content for abuse monitoring under its published data controls; the application’s request to disable response storage does not remove those separate controls. Cloudflare’s standard Workers AI inference policy excludes model training and generally ends content retention after processing, subject to its stated safety, security and legal exceptions. Separate workspace storage, backups and operational metadata still apply. See OpenAI’s API data controls and Cloudflare’s Workers AI data policy.
Storage and security
FIELDWORK restricts workspace requests to authenticated accounts and encrypts saved provider tokens and original receipt files using server-side keys. Workspace business records are stored in the hosted database. This is not end-to-end encryption: the service must process relevant data to provide its features.
The browser caches application assets for loading and an offline notice; the service worker is designed not to cache private API responses. Optional interface and notification preferences may be kept in browser storage. Cloudflare sign-in uses authentication cookies. Avoid shared browser sessions when handling private work.
Your choices and requests
Connections are optional. Disconnecting clears FIELDWORK's saved authorisation and stops new requests from that connection; an in-flight request may finish. You can also revoke the grant in the provider's account settings. Disconnecting does not delete your FIELDWORK records or copies already held by the provider.
Settings provides a workspace export. Original-file downloads need a signed-in session. You can correct editable workspace information in the application. Contact olipoignand@gmail.com for access, correction, account closure, deletion requests or privacy concerns that cannot be handled in the interface.
Requests for account closure and full erasure are reviewed manually; they are not currently self-service features. We will verify that a request comes from the person entitled to make it and explain the proposed handling, any records that must be retained and the reason. Removing an item from an active view may leave audit or recovery copies. Recovery backups are separate from the live database and are not erased by disconnecting an integration.
The retention purposes are providing your workspace, maintaining necessary business and security records, resolving requests or disputes, recovery and applicable legal obligations. Information should not be retained after it is no longer needed for those purposes. The beta’s automatic backup-expiry and complete erasure procedures are still being established; we do not promise immediate deletion or a fixed deletion deadline.
Complaints and changes
Contact olipoignand@gmail.com with a description of your concern and the outcome you seek. We will acknowledge the request, investigate the relevant handling and respond with our findings and available next steps. If more information or time is needed, we will explain why. If your concern is unresolved, you can seek guidance from the Office of the Australian Information Commissioner; its jurisdiction and complaint process apply.
We will date updates to this notice and explain material changes before applying a materially different use of personal information. Where new consent is required, we will ask for it. The operator will handle notifications directly during the invitation-only beta; the application does not currently send automated policy notices.