This privacy policy explains how Synoviq, Inc. handles personal information for ServeLume. It covers the public marketing website at https://www.servelume.com, the product at https://app.servelume.com, the ServeLume Field app (bundle identifier com.servelume.app), and support messages sent to developers@synoviq.com. It is effective 30 October 2026. Read it with the Terms of Service, the account deletion page, and the data safety summary.
Who operates ServeLume
Synoviq, Inc. operates the ServeLume software. The marketing site, the business workspace, and ServeLume Field are parts of that software. ServeLume Field is a technician companion for a company that already uses ServeLume. It is not a public consumer signup app. A person signs in with a company account. Features, message channels, and payment tools depend on the workspace plan and on how that business has configured the product.
Privacy and support questions about this policy go to developers@synoviq.com. The support and marketing address published for the field app is https://www.servelume.com.
Who controls workspace information
Two roles apply. Synoviq, Inc. decides why and how the marketing website, account sign-in, platform security, and product support are run. For that activity, Synoviq is the controller.
The service business is the customer. It decides which customers, sites, jobs, photos, signatures, materials, and staff records to put into its workspace. That business is the controller for that workspace data. Synoviq operates the software the business uses to store and share it. Using ServeLume does not make every tenant compliant with the GDPR, the CCPA, or any other privacy law. Each business remains responsible for its own notices, lawful basis, and responses about its records.
If a request is about a job, an invoice, a customer, a photograph, or another record inside a business workspace, contact that business. Synoviq can help identify which workspace holds a ServeLume login, and it does not treat every stored record as its own customer relationship.
Accounts and the field app
A workspace owner can register a business account at the product site. Registration collects the company name, the owner’s name, email, password, and a mobile number. The product can send a verification code by WhatsApp or by SMS. Technicians and other staff use accounts the business creates. The field app then shows work that business has assigned.
Account information can include the name, email address, phone number, role, workspace identifier, and sign-in tokens. The app can also send a leave request to the business, share location with that business’s dispatch while a job is active, and collect a customer signature and job photos for the job record.
Information used to provide the service
The workspace holds the operational records the business chooses to keep. Depending on the plan and the person’s role, those records can include job details, customer and site contacts, checklists, photos, signatures, materials, equipment servicing, quotes, labour, invoices, and payments the business has already received.
ServeLume uses this information to show assigned work, record what happened on site, and let the office review it. The field app does not open a separate consumer profile for the household or business being visited. Those people are the service business’s customers.
Location
Location is permission-based and limited to the job workflow. The technician can continue without location. If location is allowed, ServeLume collects precise location to share the technician’s position with that company’s dispatch during travel and while a job is in progress, including when the app is minimized or the screen is off. Location also supports the job map, navigation, and check-in or check-out.
On iPhone, background location updates can continue while that job is on the way or in progress, and the system location indicator is shown. On Android, the same sharing runs as a foreground service with a persistent notification that location is being shared until the job ends. The Android app does not request the always-on background location permission.
Sharing stops when the job ends, the technician signs out, or location sharing is turned off in Account. ServeLume does not track every technician all day, and it does not use job location for the marketing site’s analytics.
Camera, photos, and Bluetooth
The camera and photo library are used when a technician chooses to capture or attach job photos, or to scan an equipment label. Photos are part of the job record the business keeps. The app does not require the camera for sign-in.
On iPhone, Bluetooth is requested only to connect to a supported card reader. Tap to Pay, where the merchant, the phone, and the region allow it, uses Stripe Terminal for an on-site payment. The regions named for review are Australia, the United States, and the United Kingdom. This policy does not mean Apple has approved the Tap to Pay entitlement. Android devices that take a contactless tap use NFC for that reader. A card charge is sent to Stripe at the time of the tap. It is not stored on the phone as an offline command.
Information stored on the device
If the network is unavailable, the field app can keep pending job commands on the device and retry them. Those commands can include job status, checklist answers, photos, a signature, materials, equipment servicing, a quote, labour, and a record that a payment was already received. A record of money already received does not charge a card.
The phone stores those pending commands so the technician can retry them for the same signed-in account. Leaving the account removes the local retry copies. Some of those entries may already be on the server. The office should check the job history before recording them again.
Payments
Workspace subscription charges, when a payment is required, are collected by Stripe Checkout if Stripe is configured for the product. On-site card payments use Stripe Terminal. Stripe processes the card data for that charge. ServeLume receives the payment result the provider returns, such as whether the charge succeeded and a reference the business can reconcile. Do not send a full card number, a card security code, or a one-time password to developers@synoviq.com.
How long information is kept
Synoviq keeps account and security records for as long as the workspace account is active and for as long as needed to secure the service, resolve a support request, or meet a legal duty that applies to Synoviq. Closing a technician login deactivates that account and revokes its tokens. It does not erase the business’s jobs, invoices, or other records the business must keep. The account deletion page explains that path.
The service business sets how long it needs its own customer and job records. A request to delete a customer’s job history is handled by that business. Synoviq does not promise instant deletion of another customer’s history when a technician closes a login.
Service providers
Synoviq uses providers that perform a named function. Stripe processes subscription checkout and Tap to Pay charges when those features are configured. WhatsApp verification codes go through Meta’s Cloud API. SMS verification codes go through Twilio. Optional website measurement uses Google Analytics and Meta Pixel only after consent. Each provider receives the information needed for that function, such as a phone number for a verification code or a payment reference for a charge.
Regions
The product is offered to businesses, and the field-app review regions named for location and Tap to Pay are Australia, the United States, and the United Kingdom. Availability of a feature still depends on the workspace plan, the device, and the payment configuration. Regional privacy requests are described on the GDPR and CCPA pages. Those pages do not mean every tenant is subject to those laws.
Contact
Email privacy questions to developers@synoviq.com. Include the business name and the account email, and describe the request. Do not include passwords, one-time codes, or complete payment card details. Synoviq may need to confirm that the sender is the account holder or is authorised by the service business before it discloses or changes account information.