Draft version 2026-09-30 · Prepared September 12, 2026 · Revised September 30, 2026 (fonts are self-hosted)
Terms of Service
1. Scope and permitted use
FourierWorks provides maintenance planning, equipment information, work records, commissioning, reporting and analysis tools for business users. Use the service only for lawful purposes and for organizations, facilities and equipment you are authorized to represent. An organization providing access may impose additional workplace policies.
2. Accounts and access
Provide accurate account information, keep credentials confidential, and report suspected unauthorized access to the workspace administrator. Do not share credentials or access another user's records without authorization. The acting-role selector is a prototype preview; selecting a role does not grant organizational authority or establish production access controls.
3. Your records and permissions
You retain your rights in the records, documents and datasets you provide. You must have permission to enter and process them, including information about coworkers, contractors and other people. Provide only information necessary for the work. Do not upload passwords, secret keys, unnecessary medical information or material you are not authorized to disclose.
Operating the service requires processing your records to provide the features you request, such as saving, displaying, analyzing and exporting them. This draft does not grant ownership of your records or permission to sell them.
4. Industrial use and human review
Qualified personnel remain responsible for equipment operation, maintenance decisions, isolation, permits, safety checks and commissioning approval. FourierWorks is not an emergency notification service, safety interlock, certified control system or substitute for site procedures. Do not use a dashboard indication as authorization to start or service machinery.
Sample values and simulators are illustrative. Forecasts, trained models, estimated intervals and narrative reports depend on their inputs and may be incomplete or inaccurate. Validate results against equipment documentation and actual operating conditions. A saved acknowledgment or approval records an entry; it does not independently verify a person's identity, competence or legal authority.
Government forms and authority links are references. FourierWorks does not issue government permits or guarantee that a selected form satisfies the requirements for a location or activity.
5. Storage, availability and backups
Many operational records are currently stored in this browser on this device. They are not automatically shared with colleagues or synchronized across devices. Clearing site data, changing browsers or losing the device may remove access to these records. Export available records and follow your organization's backup and retention procedures.
The prototype may change, contain errors or become unavailable. No uptime, response-time, notification-delivery or recovery commitment is included in this draft. Separate signed service terms would be needed for a service-level commitment.
6. Acceptable use
Do not use the service to distribute malware, disrupt systems, bypass access controls, misrepresent approvals, falsify safety or maintenance records, or violate privacy or intellectual-property rights. Connect a gateway only with authorization from its operator. Security testing requires the operator's permission.
7. Third-party services and content
Authentication, infrastructure, external gateways and linked government or supplier resources may be provided by third parties under their own terms. You are responsible for evaluating external material and maintaining any required licenses. Third-party names and links do not imply endorsement.
8. Software rights and commercial terms
Access to the application does not transfer ownership of its software or branding. Third-party components remain subject to their respective licenses. This prototype has no checkout or subscription billing flow; this draft does not establish a price, automatic renewal or refund policy.
9. Stopping use, changes and legal terms
You may stop using the application and sign out. Signing out does not delete local records or your hosted account. See the Privacy Policy for current deletion limitations. Future service terms should explain access termination, notice of material changes and data return before they take effect.
Warranty exclusions, liability allocation, governing law and dispute procedures require review for the operator, deployment and customer contracts. This draft does not select arbitration, a liability cap or a governing jurisdiction. Nothing here is intended to remove rights that cannot lawfully be excluded.
Privacy Policy
This draft describes the data flows implemented in the current application. The operator must confirm hosting, service-provider arrangements, retention and applicable privacy obligations before public release.
Information processed and why
Information
Purpose and current location
Account email, authentication credentials and session information
Supabase handles authentication and account recovery. Session information is persisted in browser storage. Passwords are submitted to the authentication service; they are not saved as plaintext operational records.
Display name, email, sign-in timestamp, selected state and city
Account profile and authentication metadata support display, account access and state-based permit references. These are sent to the configured Supabase project.
Work orders, personnel names, contractor contacts, assessments, incidents, documents and other operational records
These support the workflows you use. The local OperationsStore saves them under your account identifier in this browser. Uploaded document content and model-training datasets may be included in these saved records.
SCADA configuration, readings and analysis data
Configuration is saved locally. Configured gateways receive browser requests and return readings. Captured readings may be retained in work records. Training in Model Studio runs in the browser; the current training feature does not send datasets to an external AI training service.
Maintenance membership, shift assignments, alerts and acknowledgments
The connected maintenance-alert feature reads and updates the configured Supabase backend. Email routing, when deployed and configured, also involves the selected delivery provider and recipients.
Chat assistant questions and a summary of saved records
When the optional AI chat is deployed and you are signed in, your question and a capped summary (up to about 12,000 characters) of saved records for the selected plant and area — work orders, production jobs, parts, incidents, downtime, commissioning projects and KPI observations — are sent through the configured Supabase function to Google's Gemini API to generate an answer. If the chat function is not deployed or configured, answers come from the built-in feature guide and nothing is sent.
Appearance and notification preferences
Browser storage remembers your appearance settings. Notification preferences are currently shown as unavailable and no notification delivery is controlled by them.
Service providers and external requests
The application uses Supabase for authentication and configured backend features (its authentication library and the application's fonts are served from this site, not a third-party CDN or font service), and— only when the optional AI chat function is deployed — Google's Gemini API to answer chat questions from the record summary described above. Those network requests disclose connection information, such as your IP address and browser request details, to the receiving services. Hosting services and connected gateways may also receive request logs. External links send you to the destination provider when opened.
Exports are downloaded to your device; people or systems you subsequently share them with receive the exported information. If your organization activates alert emails, intended recipients and the email delivery service receive the alert content needed for delivery. The deployment administrator must verify active providers and processing locations.
The reviewed application code does not include advertising pixels, behavioral-advertising features, data-sale functionality or a product analytics SDK. This is a description of the current implementation, not a statement about unverified hosting additions or future integrations.
Retention and security
Local saved records generally remain until site data is cleared or the relevant feature removes them. Signing out does not erase those records. Downloaded exports remain wherever you save them. Hosted account and alert retention, logs, backups and deletion periods must be established by the operator; no automatic retention schedule is promised here.
Browser account separation is not a substitute for server authorization or device security. Use a trusted device and follow your organization's access and backup practices. No service can promise absolute security.
Access, correction and deletion
You can edit supported profile fields in Account settings and correct records through their available workflows. Several features provide exports. Clearing this site's browser storage removes local records and session information, but does not delete hosted records or previously downloaded files; export needed records first.
There is currently no self-service hosted-account deletion or complete privacy-request portal. Contact your workspace administrator about hosted access, correction, export or deletion requests. A public request contact must be supplied before release. Depending on location and circumstances, applicable law may provide additional rights; the operator must establish the appropriate request and verification process.
Workplace use and policy changes
The application is intended for workplace use, not a service directed to children. Do not enter information about children unless an authorized, legally reviewed deployment supports that use. Material changes to data practices should be reflected in a revised policy, with notice and any required permission before the new practices apply.
Cookies & browser storage
The current client primarily uses local storage rather than application-set cookies. Local storage can persist after the browser closes.
Authentication: the Supabase session supports staying signed in and refreshing access.
Operational records: account-scoped work, training, permit, commissioning and other records support saved workflows.
Configuration: SCADA configuration and preventive-maintenance plans support equipment and planning features.
Preferences: theme, density, motion and notification choices customize the interface.
No optional advertising or analytics consent controls are currently implemented. The app does not display a consent banner that claims to disable services it cannot control. An administrator adding cookies, analytics or other optional tracking must assess consent requirements and implement working controls before enabling them.
Use your browser's site-data settings to inspect or clear storage for this site. Clearing it can sign you out and permanently remove local work. It does not request deletion from Supabase or other providers.
For this prototype, contact the administrator who provided your workspace access. Do not send passwords or sensitive industrial records in a general support request.