DialQC privacy policy
What we collect and why
DialQC processes watch photographs to inspect visible geometry, let you adjust points and export annotated results. We process original images, filenames, image metadata, measurements, results and edits. Photos may contain personal information, including reflections or embedded location data. Remove information you do not want to share and upload only images you may use.
Browsing does not require sign-in. Guest access provides dial-center setup; your current allowance appears in the app. Google and Amazon Cognito process basic identity information; DialQC stores your verified email and account identifier to provide account access, saved inspections, usage allowances, support and manual paid activation. Sign-in requests basic identity permissions, not access to your mail, files, contacts or calendars. DialQC does not receive your Google password.
For guest allowances and abuse prevention, we process your IP address, a guest cookie and browser information, including language, timezone, screen and device characteristics. Quota records store keyed hashes of IP and browser information. This browser fingerprint can recognize returning visitors; hashing does not make it anonymous. Shared networks or similar browsers may affect allowances.
We also keep usage, session, sign-in, error and administrative records to operate, secure and troubleshoot the service. Support emails are used to handle your request.
Providers, analytics and cookies
Amazon Web Services hosts the service, authentication, storage and operational records. Google processes sign-in and production website analytics. When AI identification is enabled, OpenAI receives a prepared photo thumbnail and dial crop. Signing in with an active guest QC saves it and starts its automatic marker identification; upgrading an already identified QC recalculates scores without another AI request. Account identity and guest fingerprints are not included in that image-identification request.
Google Analytics measures visits and feature use using cookies and browser/network information. Our custom events exclude photos, filenames, inspection content, account identity and guest fingerprints. Analytics is separate from guest allowance tracking. Providers may process information outside your country and have their own retention arrangements. OpenAI may retain data for abuse monitoring and other applicable purposes; AI processing is not a zero-retention service.
Session cookies last up to seven days from sign-in; activity does not extend this deadline, and signing out immediately invalidates the current session. Guest cookies last up to 365 days and temporary sign-in cookies up to ten minutes. Analytics cookies have separate settings. Browser cookie controls may affect service operation; deleting cookies does not delete server records.
How long information stays
Signed-in inspections initially remain accessible for 72 hours from the original analysis start. Editing, reopening or paid activation does not extend that expiry. Guests have no saved inspection history until they sign in with an active inspection. Its original photo and edited frame are then saved privately, with retention starting at that save. Guest uploads are still processed on servers.
Expiry ends access to a saved inspection; it does not erase every copy immediately. Uploads and temporary processing files have separate deletion schedules. Cleanup can be delayed, and backups or provider copies may remain longer. Exported files on your device remain under your control.
Account, usage, audit and expired session/sign-in records do not currently expire automatically and may remain until the operator removes them. Saved-inspection expiry does not delete these records or your Google connection.
Operator review of uploads
When upload monitoring is enabled, each photo submitted for analysis is copied privately and emailed to the DialQC operator with available automatic findings or a failure status, the upload time, and your verified account email and identifier or a keyed guest identifier. Guests do not provide an email address. Larger files use temporary private download links. This review helps monitor service quality. PNG exports are not collected by this feature.
Monitoring files in server storage are scheduled for deletion after seven days; deletion may be delayed. Email attachments and operator-downloaded copies are separate from saved-inspection history and remain until the operator deletes them. Amazon Web Services processes notification delivery, and Google Gmail stores the operator emails. Contact us about deletion of these copies using the address below.
Service reliability monitoring
When monitoring is enabled, Grafana Cloud receives technical performance measurements, sanitized error types and code locations, request timings and status codes, timestamps, client IP addresses, browser family and version, verified account identifiers or keyed guest identifiers, and randomly generated session and trace identifiers. This helps us investigate failures and slow requests. Grafana monitoring does not include photographs, request bodies, sign-in credentials, email addresses or names, URL query strings or raw error messages. The monitoring service necessarily receives your network address when your browser connects to it.
Your choices and requests
You may use guest access, choose whether to sign in, sign out and manage browser cookies. Disconnecting Google does not itself delete DialQC records.
For privacy questions or access, correction or deletion requests, email info@dialqc.com, preferably from your sign-in address. We may need to verify ownership. Do not send passwords or tokens. Account deletion is not self-service; requests need individual handling, including any retained records or backups. No automatic deletion or completion deadline is promised.