Legal / Privacy

Preece SystemsPrivacy Policy

Preece Systems builds custom software, automates workflows, connects business tools, and creates websites, including our free basic website offer. This Privacy Policy explains how we collect, use, share, and protect information through our website, inquiries, and related business services.

This policy covers information Preece Systems handles for its own website and business activities. Client-specific software and customer-owned websites may have separate privacy notices and service agreements, as explained below.

1. Information We Collect

The information we collect depends on how you contact us and the service you request.

Inquiries and free website requests

Our free website request form asks for your name, email address, business name, and a description of your business and website needs. You may also provide your current website address and indicate interest in optional paid support. A random request identifier and a hidden spam-prevention field help us process requests reliably.

This public form is for business inquiries. Please do not submit passwords, payment card details, patient records, confidential legal matter records, or other sensitive client information.

Client project information

Depending on the project, we may handle business records, workflow details, form responses, files, customer information, account permissions, and other information needed to build or support software, automations, integrations, or websites. The service agreement and any project-specific privacy notice describe the relevant scope.

Usage and technical information

We and our hosting and analytics providers may process IP addresses, browser and device information, pages visited, referring pages, approximate location, timestamps, and operational or security information. Our request endpoint also uses an IP-derived identifier to limit abuse, as described below.

Communications

If you email us, book a call, or otherwise contact us, we may receive your contact details, the content of your message, scheduling information, and related correspondence.

Payment and billing information

For Preece Systems clients, we may collect billing contact information and payment-related records. Payment processing may be handled by third-party providers.

2. How We Use Information

We use information to:

  • Respond to inquiries, evaluate requests, and agree on project scope.
  • Build, operate, and support custom software, automations, integrations, and websites.
  • Manage project access and support client workflows as agreed.
  • Troubleshoot issues and improve service performance.
  • Provide support, maintenance, updates, and security.
  • Communicate with clients and users.
  • Send administrative notices, service updates, and billing communications.
  • Send marketing, promotional, and sales communications about Preece Systems services, updates, offers, and related content, where permitted by law.
  • Understand website use and measure inquiry, booking, and demo link activity.
  • Measure the performance of our Google Ads and ChatGPT ads when you opt in to the relevant measurement.
  • Protect against fraud, misuse, unauthorized access, and security incidents.
  • Comply with legal obligations and enforce agreements.

We try to collect only the information needed to provide and support the requested service.

We use free website request details to assess the request, discuss the basic website scope, and follow up using the email address provided. Selecting interest in optional paid support does not purchase support or constitute general marketing consent. Any separate promotional communications remain subject to applicable law and your communication choices.

3. Client Data and User Data

We build software, automations, and integrations for clients' particular workflows. The client may decide what information its systems collect, who can access it, and how long it should be kept.

When Preece Systems processes information on behalf of a client, we generally act as a service provider or processor for that client, as set out in the applicable agreement. If you use a system provided by your employer, vendor, customer, or another organization, consult that organization's privacy notice for its handling of your information.

We do not use information entered into client-specific software or workflows for Preece Systems marketing unless the client agreement, a project-specific notice, or the user's separate permission allows that use.

Customers own the website files and domain for websites built under our free basic website offer. A customer's website is separate from this Preece Systems website. The customer is responsible for its own privacy notice and lawful collection and use of visitor information; its hosting provider and any tools added to that website also have their own practices. If we provide ongoing support or process visitor information on the customer's behalf, the service agreement governs that work.

4. How We Share Information

We do not sell personal information.

We may share information with the following parties when needed.

The client responsible for a project

For client-specific systems, information processed through the system may be available to the client and its authorized users.

Service providers

Our public website and request endpoint are hosted on Vercel. Free website requests are sent through that endpoint to Asana, where the submitted contact and business details, support interest, and request identifier are recorded in a task for our team to review.

We use Upstash Redis for short-lived duplicate-prevention and abuse-protection records. These records contain a hash of the submitted information, request identifiers, processing status, and IP-derived rate-limit counters, rather than the raw form fields or plain IP address. Providers may also process their own technical and operational information to deliver and protect their services.

Depending on the service, we may also use providers for email, authentication, file storage, payment processing, security, support, and related business operations.

Advertising measurement providers

Google and OpenAI receive measurement information as described in Cookies and Analytics.

Integration partners

If a project connects to tools such as Google Workspace, QuickBooks, CRM systems, email platforms, spreadsheets, or other business tools, information may be exchanged with those systems as needed for the integration to work.

Legal and safety purposes

We may disclose information if required by law, legal process, court order, government request, or to protect rights, safety, security, and property.

Business transfers

If Preece Systems is involved in a merger, acquisition, financing, reorganization, or sale of assets, information may be transferred as part of that transaction.

5. Cookies and Analytics

Our public website uses Vercel Web Analytics to understand aggregate page views and website use. Analytics may include the page URL, referring page, approximate location, browser, operating system, device type, and event time. Vercel describes this service as using request-derived visitor hashes rather than third-party cookies, with visitor identifiers discarded after 24 hours. This identifier lifetime is separate from retention of analytics reports.

We also measure clicks on email inquiry, booking, and demo links. These custom events include the page path, destination category, and published link label. Our event code does not include the contents of your form submission. See Vercel's analytics privacy information for details.

The OpenAI pixel is separate from Google Ads. Before you opt in to ChatGPT Ads measurement, its script can load, use browser storage for consent status, and send diagnostics that include that status. Global Privacy Control prevents the pixel from loading.

If you allow ad measurement on the free website form, we use the OpenAI Ads Measurement Pixel to send a lead completion event and a randomly generated event ID after your request is confirmed. The pixel can associate that event with ads in ChatGPT using an available ad click reference and browser reference. Our event code does not attach your name, email, or business description. We temporarily keep your measurement choice and event ID in your browser session to report the confirmed event. You can submit the form with ad measurement unchecked, and we honor Global Privacy Control.

After you allow measurement, the OpenAI pixel uses first-party attribution and browser-reference cookies. It requests a lifetime of up to 30 days for the attribution cookie after an ad click reference is captured, and up to 365 days for the browser-reference cookie after creation. Browser restrictions or clearing cookies may shorten these lifetimes. Unchecking measurement disables future pixel events and removes these cookies. See OpenAI's measurement pixel information for details.

Our public website code does not currently use cookies or persistent browser storage to save form entries. Hosting and security services, external destinations, and client-specific systems may have their own technologies and privacy notices. Client projects that use account sessions, preferences, analytics, or other tracking should explain those practices in their own notice.

6. Data Security

We use reasonable administrative, technical, and organizational safeguards designed to protect information from unauthorized access, loss, misuse, alteration, or disclosure.

Our public request form uses HTTPS transmission, server-side validation, abuse limits, and duplicate checks. Service access tokens remain on the server rather than in the public form code.

However, no system can be guaranteed to be completely secure. Users and clients are responsible for using strong passwords, limiting account access, and following reasonable security practices.

7. Data Retention

We keep information for as long as needed to respond to inquiries, provide and support services, comply with legal obligations, resolve disputes, enforce agreements, and maintain business records.

The request endpoint's technical duplicate-prevention records are configured to expire after approximately 24 hours, with that period refreshed when processing completes. IP-derived abuse counters expire after 15 minutes. These limits apply to the technical records in Redis, not to the full inquiry stored in Asana, our correspondence, or related business records, which may be kept longer for the purposes above. The form does not automatically delete Asana inquiries after 24 hours.

For client-specific systems, retention may also depend on the client's instructions, the service agreement, or the nature of the workflow.

8. Your Privacy Choices

Depending on where you live and the type of information involved, you may have the right to request access, correction, deletion, portability, restriction, or objection to certain uses of your personal information.

You can opt out of Preece Systems marketing emails at any time by using the unsubscribe instructions included in the email or by contacting us at the email address below. Opting out of marketing communications does not stop administrative, transactional, billing, security, support, or service-related messages.

To make a privacy request, contact us at:

Preece Systems Email: info@preecesystems.com Website: preecesystems.com

If your information is controlled by one of our clients, we may refer your request to that client or assist the client in responding.

9. State and International Privacy Rights

Some privacy laws provide additional rights to residents of certain states, countries, or regions. If a specific privacy law applies to a Preece Systems project, we will handle applicable requests as required and may provide a project-specific privacy notice.

10. Children's Privacy

Our services are intended for business use and are not directed to children under 13. We do not knowingly collect personal information from children under 13. If we learn that we have collected personal information from a child under 13 without appropriate consent, we will take appropriate steps to delete it.

Projects involving minors, schools, childcare, youth programs, or child-related data should use a separate project-specific privacy notice.

12. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we make changes, we will update the "Last updated" date above. If changes are material, we may provide additional notice through the website, app, email, or client communication.