Technology built with purpose and precision.

This site collects information you voluntarily send through email or inquiries, such as your name, contact details, project requirements, and correspondence. Website delivery providers may process routine technical requests and security logs under their own terms. We use inquiry information to respond, prepare quotes, communicate about requested services, and maintain necessary business records. We do not sell personal information. We do not request payroll documents, employer credentials, or government IDs through this informational website. Information may be shared with service providers only as needed to operate the site or fulfill a requested service, or when legally required. Contact us to request access, correction, or deletion, subject to legal recordkeeping obligations. Product-specific notices will explain any additional data before launch.

This temporary site provides informational descriptions and nonbinding starting prices. Quotes, payment schedules, scope, ownership transfer, revisions, and delivery terms are governed by a separately accepted written agreement. Domain pricing applies to eligible standard registrations; third-party and premium-domain costs may differ. Do not misuse the website or submit confidential credentials or payroll records. Content and product plans may change. Third-party product names are informational and do not imply partnership or endorsement. Nothing here guarantees service availability, API access, product release dates, or specific results. Contact us regarding accessibility, corrections, or service concerns.

For website inquiries, retain correspondence only as reasonably necessary to respond, manage the business relationship, resolve disputes, and satisfy applicable legal or accounting duties. There is no promised universal fixed deletion period for emails or legally required records. To request access, correction, or deletion, email connect@jonthuemichel.com with the subject “Privacy Request”; do not include sensitive documents in the initial email. We will verify the request as appropriate, review applicable obligations, and respond with the outcome. Deletion from third-party backups or legally required records may be limited. Before product launch, each app will publish its retention schedule, export and deletion options, and processor-specific practices.

Security principles for development include least-privilege access, separate business and private environments, authenticated administrative access, encrypted transport, secrets kept out of source code, restricted logging of personal data, software updates, and review of third-party access. These are policy requirements and implementation objectives; this public page is not evidence that every control has been deployed or independently audited. Sensitive payroll data should be minimized, processed locally when practical, and not saved in cloud databases by default without user choice. Do not send credentials or pay statements through the public contact email. No security certification is claimed.

Suspected unauthorized access, exposed credentials, data loss, or service compromise should be reported to connect@jonthuemichel.com with the subject “Security Incident”; do not include secrets. Our response procedure is to record the report, assess affected systems and information, contain access or suspend affected integrations as appropriate, preserve relevant evidence, rotate exposed secrets, investigate root cause, restore safely, and notify affected parties or authorities when legally or contractually required. Response timing depends on incident severity and verified facts; no guaranteed response time is offered. Before processing live sensitive data, this procedure must be assigned, tested, and supported by actual monitoring and recovery controls.

Integrations are optional and subject to provider approval, permitted API scopes, applicable contracts, and explicit user authorization. PayCheck may explore user-authorized payroll data access, including ADP, but has no represented ADP partnership or active connection. Request only data needed for the user-selected feature; disclose the provider, purpose, categories of data, retention, and revocation method before connecting. Do not ask users for employer-portal passwords. Use approved authorization flows and protect tokens; disconnect and revoke access when supported. Private Mode must not silently transmit financial information to cloud AI. Cloud AI requires a separate opt-in, and zero-data-retention claims require written provider confirmation and verification. AI Off and bring-your-own-AI options are planned, not live features. Product integration notices will be updated when implementations are verified.