Privacy Policy
Effective October 15, 2026
FieldQuo is software a contracting company runs its business on: quotes, invoices, scheduling, and — for companies that turn it on — an AI phone receptionist and AI drafting tools. This page explains what personal information passes through it, who else sees it, and what say you have over it. It applies to FieldQuo staff, to the contractors ("companies") who subscribe to FieldQuo, and to the clients and callers of those companies (their "homeowners" or "clients") whose information reaches us because a company they hired uses FieldQuo.
1. Who this policy covers, and a word about who controls what
FieldQuo is multi-tenant software: each subscribing company (a painter, a cabinet maker, a plumber, and so on) has its own account, its own clients, and its own data. For most of the personal information described here — a homeowner's name, address, phone number, quote and invoice history, photos of their property, and any recorded phone calls — the company is the data controller and FieldQuo is its processor. We hold this information because a company we serve put it into the product to run its business; we do not decide to collect it, and we do not use it for our own purposes beyond running and improving the product itself. If you are a homeowner or client with a question about your own information, the fastest route is usually the company you hired — see Section 6.
Separately, FieldQuo is the data controller for information about the companies and staff who subscribe to FieldQuo itself — account details, billing contacts, and how staff use the product.
2. What we collect
From a subscribing company and its staff
- Account and contact details: name, email, phone, company name and address.
- If you start the signup form and do not finish it, what you had typed so far (your name, email, phone, company name, trades and language) is kept so that we can follow up with you about the signup — by email, or by a call from our sales team if you gave a phone number. You can ask us to delete it at any time (see Section 6).
- Billing information, handled by Stripe (see Section 4) — FieldQuo does not store card numbers.
- Everything the company enters to run its business: clients, quotes, invoices, jobs, pricing, photos, and staff activity within the product.
From a client, homeowner, or caller
- Name, address, phone number and email, when a company adds them as a client, or when they submit a self-quote form, a booking request, or call a company's AI receptionist.
- Photos of their property, when they or a company's staff attach them to a quote or job.
- On a company’s instant-estimate page or lead funnel: how far the visit got and which link or ad it arrived from (counted without a cookie), and — under a notice beside the fields saying so — the name, email and phone typed into the contact step even if the request is never sent, kept for that company to follow up and hidden after 30 days. If the company has added its own advertising pixel (Meta, Google or TikTok), that platform receives page views and a “lead” event from the visitor’s browser, with no name, email, phone or address; a company can require the visitor’s consent before any pixel loads.
- Payment details, when they pay an invoice or a booking fee online — handled by Stripe; FieldQuo does not store card numbers.
- The content of quotes, invoices, and messages sent to them.
- If a company uses the AI phone receptionist: the audio, recording, and transcript of calls to that company's number.
- If a company offers automatically-recurring payments (a "service plan"): their saved payment method, and the IP address and browser user agent present when they authorised it — recorded because Stripe's rules for charging a saved payment method later require us to be able to show that authorisation happened.
- When they approve a quote by signing it online: the drawn signature itself, the name they typed, the time, and the IP address and browser user agent the signature came from. That last part is what makes the signature worth anything — a signature nobody can place at a time and a connection is a picture, not evidence, and if the approval is later disputed it is the contractor who needs to be able to show it happened.
Page views
FieldQuo measures which of its own pages are viewed — the marketing site, the help centre, the back office and the pages a company's clients open — itself, with no tracking cookie or advertising pixel. What is recorded is the page's route (never the specific quote, booking or client it showed), the interface language, a screen-size bucket, the referring site's domain and any campaign tags in the link, plus a random identifier kept in the browser's own storage so that one reader is counted once. No IP address is stored. Raw entries are kept for 30 days and then reduced to daily totals.
Separately, back-office page loads (never a page a company's clients see) report performance timings to Vercel Speed Insights so we can find slow pages: the page path without its query string, the device and browser type, and how long the page took to load. It is listed in Section 4.
On FieldQuo's own website (fieldquo.com) and inside the back office, and nowhere else, we also use HeyCatch, a product analytics service, to understand how contractors find FieldQuo and use it: the pages viewed and the buttons and links clicked, with on-screen text and link addresses masked so a client's name, address or document link is never sent. A signed-in contractor is identified to it only by their FieldQuo user id, their company's id, their role and their plan — never by name, email address or phone number. It is never loaded on a quote, invoice, booking page, client portal or a contractor's website, so a company's clients are never measured by it. It is listed in Section 4.
We do not knowingly collect information from anyone we know to be a minor, and FieldQuo is built for business-to-business and business-to-homeowner transactions, not for use by children.
3. How we use AI
FieldQuo uses AI in specific, narrow places — never to build a general profile of a person, and never to compare one company's data against another's. What follows is what each AI feature is for; it does not describe how any figure is calculated, because that is not a privacy question.
- Reviewing a quote before it's sent. The photos attached to a quote are read by an AI model to surface things worth double-checking on site, and to help write plain-language descriptions of the work. A company can also pay for a deeper photo review of the same photos.
- Recovering and drafting from phone calls. For companies using the AI phone receptionist, call transcripts are used to reconstruct a lead from a call that wasn't captured any other way, to draft a quote from what a caller described, and to build a monthly digest summarising a company's call activity.
- The FieldQuo AI assistant. Built into the product for a company's own staff to ask questions about their own business — cash flow, quotes, invoices, jobs. It answers only from that company's own data, refuses requests unrelated to running the business, and never sees another company's information. Where it needs to reference a client to answer a question, it is given that client's name only — never their address, phone number, email, or financial history — enforced in code, not left to the model's judgement.
- Generating marketing images. A company can generate or edit marketing images (for ads and its website) using AI, from a reference photo it supplies.
- Drafting and translation. AI drafts website copy and translates text a company writes, working from that company's own data — it does not invent services, prices, or layouts.
- Reading client conversations. When a company uses the paid conversation read, the conversation coach or the monthly conversation review, the text of its own client conversations (texts, chats, and emails filed from a connected mailbox) is read by an AI model to tell that company how an enquiry is going and what its won and lost enquiries had in common. Surnames, phone numbers, email addresses, street addresses and postcodes are removed before the model sees a word.
AI processing for these features is performed by OpenAI, and — for phone calls — by Retell; see the table in Section 4.
4. Who else sees this information
We use the following third-party services to run FieldQuo. Each receives only the categories of information its role requires.
| Service | What it does | What reaches it |
|---|---|---|
| Neon | Database hosting | Every table FieldQuo writes to — companies, staff accounts, clients, quotes, invoices, jobs, call and message logs, everything. This is the single database behind the whole product. |
| Stripe (Connect) | Payment processing — a homeowner paying a contractor | A homeowner's card details, when they pay an invoice or a booking fee. The charge is created on FieldQuo's platform Stripe account and the funds are transferred to the contracting company's own connected Stripe account — FieldQuo's servers never store the card number itself; Stripe does. |
| Stripe (Billing) | Payment processing — a contractor paying FieldQuo | A contracting company's own card details and billing contact, for their FieldQuo subscription. Separate from Stripe Connect above — this is FieldQuo getting paid, not a homeowner. |
| Stripe (saved payment methods) | Payment processing — automatic recurring payments a homeowner authorises | A homeowner's saved payment method, for a recurring service plan they've agreed to (e.g. a seasonal maintenance contract billed automatically). We also record the IP address and browser user agent present when they authorise it, because Stripe's rules for charging a saved payment method without the cardholder present require us to be able to show that authorisation happened. |
| Resend | Outbound email delivery | Every email FieldQuo sends on a company's behalf passes through Resend to be delivered — the recipient's address and the full content of whatever was sent: a quote, an invoice, a booking confirmation, a marketing message. |
| Twilio | SMS delivery | A homeowner's phone number and the content of text messages sent to or received from them — appointment reminders, booking confirmations, and STOP/START opt-out replies. |
| Cloudinary | Image and video storage and delivery | Photos uploaded into the product — job-site photos, photos a homeowner attaches to a quote request, and images used on a company's generated website — and the video clips a company uploads to post to its own social accounts, which Cloudinary also converts to the vertical format those platforms take. |
| OpenAI | AI features | Property photos (when a quote is reviewed, and on the paid deep photo review), call transcripts (to recover a lead from a missed call, draft a quote from a call, and build the monthly activity digest), and — for the FieldQuo AI assistant built into the product — a client's NAME ONLY, never their contact details, address, or financial history. When a company uses the paid conversation read, the conversation coach or the monthly conversation review: the text of its client conversations (texts, chats, and emails filed from a connected mailbox), with surnames, phone numbers, email addresses, street addresses and postcodes removed first. See "How we use AI" below for what each of these is for. |
| Retell | AI phone answering | For companies using the AI phone receptionist: the live call audio, the recording, and the transcript of every call it takes. |
| Vercel | Hosting | FieldQuo runs on Vercel's infrastructure — all traffic to the product passes through it. |
| Vercel Speed Insights | Performance measurement of the FieldQuo back office | For a sample of page loads inside the contractor back office only: the page path with the query string removed, the device and browser type, and performance timings (how long the page took to load and respond). No names, contact details, or customer records are sent. It is never loaded on anything a homeowner sees — quotes, invoices, booking pages, client portals, or a contractor's website. |
| HeyCatch | Product analytics for fieldquo.com and the FieldQuo back office | On FieldQuo's own website and inside the contractor back office only: the pages viewed and the buttons and links clicked (with on-screen text and element attributes masked, so client names, addresses and links are not sent), the device and browser type, the referring site and campaign tags, and a random identifier kept in the browser's local storage. For a signed-in contractor, their FieldQuo user id together with their company's id, their role and their plan — never their name, email address or phone number. A few business events are sent from our servers (a company created, a subscription started or changed, a company's first quote sent) with the same ids. It is never loaded on anything a homeowner sees — quotes, invoices, booking pages, client portals, or a contractor's website. |
| Meta (Facebook/Instagram Ads) — spend import | Ad-spend import — a contracting company's own Meta ad account, read only | For companies who connect their own Meta ad account (Settings → Meta Ads, an owner/admin-only action): an OAuth access token scoped to ads_read, and which ad account id is connected. In return FieldQuo receives that company's own ad spend, campaign names, and performance figures — impressions, clicks, and Meta's own reported conversions. This never includes a homeowner's information: no client name, contact detail, or quote/job data is sent to Meta, and FieldQuo does not use Meta's Conversions API. See docs/META-ADS-BUILD.md. |
| Google Maps | Address autocomplete and mapping | An address as a homeowner or contractor types it, for autocomplete, and the address on a job for map display. |
| Unsplash | Stock photography, loaded from Unsplash's own servers | No personal information is SENT to Unsplash by us. But a new company website starts with stock photos in its decorative slots, and those are hotlinked rather than copied — so a homeowner visiting a contractor's site makes a request to Unsplash's image servers, which sees their IP address and browser. The same applies to stock photos placed in the Marketing Designer. Uploading real photos replaces them. |
| YouTube (Google) | Video embedded on FieldQuo's own marketing pages | A visitor's IP address and browser, when a FieldQuo marketing page with a video on it loads. We use YouTube's no-cookie embed domain, which does not set a tracking cookie before the visitor presses play — but the request to Google still happens. This is FieldQuo's own website, not a contractor's. |
| Google Calendar | A staff member's own calendar, connected by that member from Settings → My calendar | Only when a staff member connects their own Google account. FieldQuo writes its own events to that member's calendar — the visits assigned to them, with the client's name, the site address and a link back, and a Google Meet link on a video-call booking — and reads back only whether the member is busy at a given time, never the titles or details of their own events. When the member disconnects, the access is revoked and the FieldQuo events still being kept in step are removed. Nothing from Google Calendar is used for advertising or sold, and busy time is shown only as untitled blocks, to that member and to colleagues allowed to see the team's schedule. See Section 9. |
| Google Business Profile | A company's own Google listing, connected from Settings → Reviews | Only when someone allowed to manage the company's team (an owner, admin, manager or dispatcher) connects the company's Google account. FieldQuo reads the listings that account manages (to pick one) and that listing's reviews — the reviewer's display name, rating, text, any reply, and dates — and keeps a copy for at most 30 days. When asked to from Settings → Booking Page, it adds or removes one "Book" button on the listing pointing at the company's booking page, and changes nothing else. Disconnecting revokes the access and deletes the stored token and every copied review. See Section 9. |
| Gmail | A connected work mailbox, from Settings → Work email | Only when someone at a company connects a Gmail or Google Workspace mailbox. FieldQuo reads the headers of new mail to find messages to or from the company's clients and leads, downloads and files only those into that client's conversation, and never downloads the body of any other message. If an owner or admin turns on sending for the company mailbox, the company's client emails (quotes, invoices, payment requests, booking confirmations and inbox replies) are sent through it. Disconnecting revokes the access and deletes the stored credential; emails already filed stay with the client's record. See Section 9. |
| Google Solar | Roof measurement | A property's address, sent to estimate roof area and shape for a self-serve roofing quote. |
| Meta (Facebook & Instagram) — publishing | Social media publishing — posting a company's own ad to its own Page or Instagram account | Only when a company chooses to publish a Marketing Designer ad or video: the rendered image or the video clip (fetched by Meta from a public, unlisted Cloudinary URL — see lib/social/metaSpecs.js and lib/marketing/videoPost.js), the caption text, and the company's own connected Page/Instagram account id and access token. No homeowner data is involved — the asset published is the company's own advertisement, not a client record. Separate from the ad-spend import below, which reads FROM Meta rather than posting TO it. |
| TikTok — publishing | Social media publishing — posting a company's own ad to its own TikTok account | Only when a company connects its TikTok account and chooses to post a Marketing Designer ad or video: the rendered image or the video clip (which TikTok downloads from a short-lived, unguessable FieldQuo link), the caption, and the visibility, comment and commercial-content settings the person chose. To connect, TikTok returns the account's id, display name, picture and access tokens, which FieldQuo stores encrypted and deletes on disconnect. No homeowner data is involved — the post is the company's own advertisement, not a client record. |
We do not sell personal information, and we do not share a company's client data with any other company on FieldQuo. The one exception is described in Section 7: the pooled industry benchmark, on by default and switchable off in Settings, which takes only a company's own anonymised, aggregate figures (never its client-level data).
Where data is hosted:FieldQuo's database and application servers are in the United States, in the northern Virginia / Washington, D.C. area (Neon on AWS us-east-1 and Vercel's iad1 region). The other services listed above run on their own infrastructure and may process the information they receive in other countries, under their own terms.
Requests from public authorities
If a government agency, regulator, or law-enforcement authority asks FieldQuo for personal information, we:
- review every request to confirm it is lawful and properly made before we respond;
- challenge a request we consider unlawful, overly broad, or not properly made, and do not disclose anything while that challenge is open unless the law requires us to;
- disclose only the minimum information the request legally requires; and
- keep a record of each request, our response, the legal basis for it, and who handled it.
Where the law allows, we tell the affected company before disclosing its information, so it can respond itself.
5. How long we keep information
We want to state this plainly rather than promise a retention schedule the product doesn't implement: FieldQuo does not currently delete data on a schedule, and there is no way for a company to delete its FieldQuo account today. If a company's subscription lapses, its account becomes inaccessible — nobody can sign in and use it — but the underlying records are not erased.
- A client record can only be deleted by a company's own staff, and only if that client has no quotes and no invoices on file. A client with any billing history cannot be deleted through the product.
- Call recordings and transcripts have no automatic expiry — they are kept until a company's staff removes what they can, subject to the limits above.
- Email unsubscribe and SMS opt-out records are kept permanently, by design — an opt-out is a standing instruction, and honouring it later depends on still having the record that it was given.
We are telling you this directly because we think a retention policy that describes a deletion schedule the product doesn't have would be worse than one that says plainly what happens today. We intend to build account and data deletion; this policy will be updated, with a new effective date, when that ships.
In the meantime, deletion is a request handled by a person. Data Deletion sets out exactly what to send, where, and what we can and cannot erase.
6. Your rights, and how to reach us
Depending on where you are, you may have rights to access, correct, export, or request deletion of your personal information. We want to be direct about where the product stands today: there is currently no self-service way for a homeowner or client to see, correct, export, or delete their own information through FieldQuo. The client account area a company's client can reach shows their own quotes and invoices with that company and lets them pay a balance — it is not a data-access tool.
If you want to exercise a privacy right, the most direct route is the company you dealt with — they hold your primary relationship and can act on your request. If you'd rather contact FieldQuo directly, email hello@fieldquo.com and tell us which company's records your request concerns; we will act on it directly where we are able to, and otherwise route it to that company on your behalf. For a deletion request specifically, Data Deletion lists what to include so we can act without a round trip.
7. Aggregate industry benchmarking (on by default, switch off in Settings)
A company's anonymised pricing and conversion figures are pooled into a benchmark that shows companies like them how their numbers compare — for example, a median win rate across similar trades. This ison by defaultunder the Terms of Service (Section 7) a company accepts when its account is created, is never shown broken out by individual company, is only published where enough companies contribute that no single company's figures can be worked out, and can be switched off at any time in Settings › Company. No client-level data — no client name, address, or contact information — is included in this pool, only aggregate figures about the company's own business.
Information about a business, as opposed to an identifiable individual, is generally not "personal information" under Canadian privacy law (PIPEDA) — which is part of why this is offered as a product setting rather than treated as a personal-data consent flow. The one case that doesn't fit that reasoning is a sole proprietor, whose business figures can be inseparable from them as an individual. If that describes your business, treat this setting as covering your own personal information too, and decide accordingly.
8. Marketing email and text messages
Commercial emails from a company using FieldQuo — marketing campaigns, review requests, and similar outreach — carry a working, one-click unsubscribe link, and unsubscribing takes effect immediately. Transactional messages (a quote, an invoice, a payment receipt, a password reset) do not carry an unsubscribe link, because they are not marketing and CASL does not require one on them.
For text messages, replying STOP to a message from a company's own dedicated number opts that number out of future texts from that company; replying START opts back in. One current gap, stated plainly: a company that hasn't been assigned its own dedicated texting number and is using FieldQuo's shared fallback number does not yet have a working STOP reply on that shared number — see the Security page for more detail.
9. Google user data
FieldQuo can connect to three Google services: Google Calendar, Google Business Profile and Gmail. Each connects only when someone at a company chooses to, on Google's own consent screen, and each can be disconnected at any time. This section sets out exactly what FieldQuo reads from and writes to each one, what it keeps and for how long, and how to undo it. “Google user data” here means the information FieldQuo receives from Google through those connections.
Google Calendar — a staff member's own calendar
Connected by a staff member, for themselves, from Settings › My calendar. FieldQuo asks Google for calendar.events and calendar.readonly, and for the connected account's email address.
- What it writes.FieldQuo creates, updates and deletes events on your primary calendar for the site visits, appointments and bookings assigned to you in FieldQuo. Each event carries the kind of visit, the client's name, the site address (none for a phone or video call), the time, and a link back to FieldQuo. For a video-call booking, Google creates a Google Meet link with the event, and FieldQuo saves that link on the booking so the client can be sent it.
- What it reads.When your calendar is busy: start and end times only, through Google's free/busy query, which returns no titles, attendees, locations or descriptions. It is used so that a time you are busy is not offered on the company's booking page, by its AI receptionist, or to the office when it moves a visit. FieldQuo also reads back the events it created itself — each one carries a private FieldQuo mark — to keep them up to date, and checks that mark before changing or deleting anything, so it never edits or deletes an event of your own.
- Who sees it.Your busy times appear on FieldQuo's calendar as grey “busy” blocks with no detail, to you and to colleagues whose role lets them see the team's schedule.
- What is stored, and for how long.An encrypted refresh token, your Google email address (to show “Connected as”), and the Google ID of each event FieldQuo created — until you disconnect. Busy times are held in server memory for at most five minutes and are never saved to the database. A Meet link stays on the booking it belongs to, because the client was sent it.
- Reading busy times and writing visits can each be switched off separately, on the same screen, without disconnecting.
Google Business Profile — the company's listing
Connected for the company, from Settings › Reviews, by someone allowed to manage the company's team in FieldQuo (an owner or admin, or a manager or dispatcher). FieldQuo asks Google for business.manage, and for the connected account's email address.
- What it reads.The Business Profile accounts and listings the Google account manages (each listing's name, title and address), so you can pick which listing to connect; only the one you pick is kept. Then that listing's reviews: the reviewer's display name (or “A Google user” when the review is anonymous), the star rating, the review text, the reply already posted, if any, and the dates. They are shown to the company in Settings › Reviews. A review appears publicly only if the company switches it on: it is then shown unedited and credited to Google on the company's FieldQuo website, and can be used in marketing graphics the company makes in FieldQuo. FieldQuo does not reply to, edit or remove reviews.
- What it writes.Only when the company asks, from Settings › Booking Page: it adds a “Book” button to the listing that links to the company's FieldQuo booking page, or removes that one button. It never changes any other link or any other part of the listing.
- What is stored, and for how long.An encrypted refresh token, the Google email address, the chosen account and listing names, and a copy of the listing's reviews. The copy is refreshed nightly; a review Google no longer returns is deleted at that refresh, and no review is kept longer than 30 days without being fetched again.
Gmail — a connected work mailbox
Connected from Settings › Work email: by any staff member for their own work mailbox, or by an owner or admin for the company mailbox. FieldQuo asks Google for gmail.readonlyand for the account's email address. It asks for gmail.send only when an owner or admin sets up the company mailbox to send client email.
- What it reads.About every ten minutes — and, when the mailbox is first connected, for the previous 90 days — FieldQuo reads the headers of new mail (sender, recipients, subject, date and message IDs), skipping spam, trash, drafts and chats, and compares the addresses with the company's clients and leads.
- What it keeps.Only a message to or from one of the company's clients or leads is downloaded in full and filed into that client's conversation in FieldQuo: its headers, its text, and its attachments (up to ten files of up to 10 MB each, stored with Cloudinary). For every other message the body is never downloaded and nothing is stored but a count of skipped messages. A filed email is part of the client's conversation like a text or a chat: the company's staff see it in the inbox, it counts towards that conversation's score, and it is included when the company uses the paid AI conversation features described in Section 3 — with surnames, phone numbers, email addresses, street addresses and postcodes removed before an AI model sees it.
- What it sends.When sending is switched on, the company's client emails — quotes, invoices, payment requests, booking confirmations and replies written in FieldQuo's inbox — are sent through the mailbox, so they come from its real address and sit in its Sent folder. FieldQuo sends nothing else through it, and never marketing campaigns.
- What is stored, and for how long.The encrypted credential and the mailbox address, until you disconnect. Filed emails stay with the client's record until they are deleted on request (below).
How Google user data is used, and what it is never used for
- It is used only to provide the features described above to the company and the person who connected it.
- It is never sold.
- It is never used for advertising — not to serve, target or personalise ads, and not to build a profile of anyone.
- It is never used to develop, improve or train generalised AI or machine-learning models.
- It is not transferred to anyone except the service providers listed in Section 4 that FieldQuo needs to run these features (its database and hosting, Cloudinary for email attachments, and OpenAI for the AI features described in Section 3), or where the law requires it (Section 4, “Requests from public authorities”).
- No one at FieldQuo reads it unless you have given us permission to for specific data (for example, by asking support to look into a problem), it is necessary for security purposes such as investigating abuse or a security incident, it is necessary to comply with the law, or it has been aggregated and anonymised for FieldQuo's internal operations. Staff at your own company see what FieldQuo shows them in the product, under the permissions your company sets.
FieldQuo's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Disconnecting, revoking access, and deletion
- Google Calendar:Settings › My calendar › Disconnect. FieldQuo deletes the events it is still keeping in step on your calendar — upcoming visits and those from the past 30 days — revokes its access at Google, and deletes the stored token, email address and event IDs. Visits further in the past stay on your calendar as your own history; delete them in Google Calendar if you want them gone.
- Google Business Profile:Settings › Reviews › Disconnect (the same people who can connect it). FieldQuo revokes its access at Google and deletes the stored token, the listing details and every copied review at once — which also takes them off the company's website. A “Book” button FieldQuo added stays on the listing, because it is part of your public profile: remove it first from Settings › Booking Page, or afterwards from your Business Profile on Google.
- Gmail:Settings › Work email › Disconnect (the person who connected the mailbox, or an owner or admin). FieldQuo revokes its access at Google, deletes the stored credential, stops reading the mailbox and stops sending through it. Emails already filed into client conversations stay, as the company's record of what was said to its clients; the screen says so before you confirm.
- At Google, at any time:remove FieldQuo's access at myaccount.google.com/permissions. FieldQuo can then no longer read or write anything through that connection. What it already stored stays until you also disconnect in FieldQuo, or ask us to delete it.
- Deletion on request:to have Google user data FieldQuo holds deleted — filed emails included — email hello@fieldquo.com or use Data Deletion. It is carried out by a person within 30 business days, and you are told when it is done.
10. Quebec — Law 25
Emilio Boves, Chief Executive Officer, and Person in Charge of the Protection of Personal Information, is responsible for the protection of personal information at FieldQuo and can be reached at 819-238-7263.
11. Changes to this policy
If we change this policy in a way that matters, we'll update the effective date at the top and, where the change is material, tell subscribing companies directly.
12. Contact
Questions about this policy: hello@fieldquo.com.
