Privacy Policy
Updated September 17, 2026
Who operates Klearwerks
Klearwerks’s project owner operates the service. Contact trietpham@klearwerks.com for privacy questions or access and correction requests. Updated September 17, 2026.
Information you provide
Cloud accounts use your email address, account identifier, and authentication information. Apple or Google sign-in shares the identity information needed to authenticate you; Klearwerks does not receive your Apple or Google password. Business content can include customer names, service addresses, vehicle details, team names and emails, schedules, access instructions, checklists, notes, and photos. We also store invitation records, coupon access, and the versions and time of your agreement acceptance.
Your account and workspaces
You must sign in to use Klearwerks. The app retrieves your authorized businesses and reopens your last available workspace. Jobs, photos, services, and team records in that workspace sync through Supabase and are cached on your signed-in device for connection interruptions. Local libraries from earlier previews are preserved on their original device but are not automatically imported or assigned to an account.
How information is used and shared
Information is used to authenticate accounts, provide business workflows and syncing, control team access, manage tester offers, and operate and protect the service. Supabase provides authentication, database, private photo storage, and live updates; the development database is in US East, Northern Virginia. Apple and Google process sign-in under their own privacy policies. Authorized teammates see information according to their roles. Reports you export or share go to the recipients or services you choose. The current app has no advertising, analytics SDK, or AI processing, and we do not sell your personal information.
Permissions and security
Camera and photo/file access are requested when you choose to add an image. Klearwerks does not continuously track location. Cloud connections use HTTPS, database access checks are enforced on the server, and sessions use the platform Keychain. No system can guarantee protection against every attack. Use a protected device and secure account credentials.
Retention and deletion
Local records remain until you remove them or the app’s data. Cloud records are retained while needed to operate your business or resolve a deletion request. Deleting a job removes it from your team’s app; server photos and backups follow the retention cycle below. You can delete your account from Account in the app, and owners can delete a business from Settings; contact trietpham@klearwerks.com for an export. We will review the request, verify ownership, and explain any records that must be retained. Backup copies may remain until the provider’s retention cycle ends. Offline devices cannot be remotely erased immediately; they remove restricted caches after reconnecting. Copies of reports already shared with others remain under their control.
Your choices
You can choose which business records and photos to add, revoke camera/photo permissions in device settings, sign out, and ask the owner to remove team access. An internet connection is required to verify your account and reopen a workspace after restarting the app. You can manage Apple or Google authorization in that provider’s account settings. This preview is intended for adults conducting business, not children. Updated privacy terms will be available here and material changes will be presented for acceptance.