HEPNER SYNC PRIVACY POLICY
Business Platform | Version 1.7 | Last updated January 26, 2026
Hepner Sync respects the privacy of the people and organizations that use our software. This Privacy Policy explains the personal information we collect, receive, use, disclose, secure, retain and make available for review when providing the Hepner Sync portal at https://app.hepnersync.com, its Marketplace, and the applications and integrations made available through that portal (together, the "Services").
The Services are designed for business and organizational use. They may contain information about individuals who do not personally use the portal, such as a customer's employees, prospective customers, suppliers or other contacts.
This Privacy Policy is a notice about our information practices. It is not a transfer of ownership of Customer Data or a replacement for a signed data processing agreement. Use of the Services is governed by the Hepner Sync Terms of Service and any applicable signed agreement.
1. Who we are and what this policy covers
Hepner Sync LLC, a Wisconsin limited liability company ("Hepner Sync," "we," "us" or "our"), is identified as the portal operator in the Hepner Sync Terms of Service. Hepner Sync is distinct from Hepner Consulting LLC, Hepner Studios LLC and Hepner Corp, although affiliated personnel and systems may help provide authorized services.
This Policy covers personal information handled in connection with portal accounts, workspaces, Marketplace subscriptions, the Designer module, Time Tracking, customer-authorized integrations, and ERPSync or QMS applications made accessible through the portal. It does not automatically govern other products or unrelated services offered by Hepner-affiliated businesses, or a third party's independent website or product. Those services may provide separate privacy notices.
2. When we act for customers and when we act for ourselves
Customer-controlled business information. The business or organization that controls a workspace (the "Customer") generally decides what employee, client, lead, supplier, document and operational information to enter, who may access it, how it is used and how long it is needed. For that information, the Customer ordinarily acts as the data controller or business, and Hepner Sync acts as a processor or service provider on its behalf, subject to the applicable agreement and law. Customer Data remains the Customer's data.
Information we manage for our own operations. Hepner Sync generally determines how it handles account registration, authentication, workspace membership records, commercial communications, billing, subscriptions, portal security logs, Terms acceptance records, support inquiries and service administration. For those purposes, we may act as an independent controller or business.
A separately executed master services agreement, data processing agreement or other signed agreement may provide more specific roles, instructions or protections and will control where applicable. Individuals seeking access to business records entered by an employer or another Customer should normally contact that Customer first; we will assist the Customer as required by applicable law or agreement.
3. Information we collect and receive
3.1 Account, access and workspace information
We process information such as names, email addresses, account identifiers, workspace names and settings, roles, membership, invitations, access permissions, sign-in events and account recovery activity. Our authentication provider handles password authentication and optional authenticator-based two-factor enrollment. We also record evidence of acceptance of the Terms, such as the user and workspace identifiers, time, policy URLs, Internet Protocol (IP) address and browser information.
3.2 Subscription, payment and business relationship information
We process business contact details, workspace and billing identifiers, modules purchased, subscription status, rates, charges, invoices, payment status, approved design hours, staff service descriptions and support or sales communications. Our payment processor, Stripe, processes payment details through its own payment pages. Hepner Sync does not intentionally collect or store complete payment-card numbers or card security codes in the portal.
3.3 Information that Customers enter into modules
Depending on which modules are enabled, a Customer or its authorized users may provide:
· Designer: software ideas, written questions and answers, chat history, workspace context, generated specifications, briefs and review notes.
· Time Tracking: employee or contractor names, jobs, crews, cost codes, work hours, schedules, timesheets, breaks, approvals, adjustments, pay rates, overtime configurations, time-off requests, balances and job costs.
· ERPSync / Quality Management (QMS): company procedures, policies, controlled documents, revisions, supplier and contact records, quality and food-safety records, audits, corrective actions, tasks, approvals and signatures. Where electronic signing is enabled, records may include the signer's printed name, role, IP address, browser information, approval meaning and a hash associated with the signed revision.
· Integrations: credentials for customer-authorized external accounts, incoming sales leads, client contact information, homeowner names, telephone numbers, addresses, email addresses, status updates and integration event records.
· Files and reports: documents, spreadsheets, attachments, imports, exported reports and other materials uploaded or generated in a workspace.
Some worker records and third-party contacts have no portal login. Their information may still be processed because a Customer chooses to use the Services to manage its operations.
3.4 Technical, usage and communication information
We process session and security information, IP addresses, browser and device details, event timestamps, application activity, access and permission changes, technical error diagnostics, notification delivery information and support correspondence. Technical logs are used to operate, troubleshoot and protect the Services. Error reports may incidentally contain personal information relevant to a malfunction.
3.5 Optional device location
The Time Tracking module contains an optional clock-in and clock-out location feature. If a Customer enables it and location access is technically available, the service may request device location at the moment of a time punch. The feature is not designed for continuous location tracking. When a position is successfully obtained, the application is designed to store latitude and longitude rounded to approximately 35 feet (11 meters), an accuracy value and a status such as saved, declined or unavailable.
A Customer may configure location as off, requested or required. In a requested mode, a worker may decline a position; in a required mode, a time punch may not proceed without an available position. Browser or device settings may prevent location collection. Location records are subject to workspace permissions, and authorized Hepner personnel may access relevant records when needed to provide support or investigate an issue. Customers are responsible for providing any required worker notice, consent and lawful alternatives.
4. How information reaches us
We receive information directly when someone creates an account, purchases a module, contacts support or enters information. We also receive information from workspace administrators, other authorized users, customer-provided imports, and external services that a Customer deliberately connects. Technical information is generated when a device interacts with the Services, when jobs or notifications run, or when a transaction or support action is recorded.
Where a Customer imports information concerning other people, that Customer is responsible for having a lawful basis to collect and supply it and for giving required notices to those people.
5. Why we use personal information
We use personal information for the following purposes, as appropriate to the type of information and our role:
· Providing and maintaining accounts, workspaces, subscriptions, modules, authentication, permissions, imports, exports and customer-requested integrations.
· Processing purchases, invoices, billing adjustments and payment or subscription inquiries.
· Delivering transactional emails, invitations, password resets, relevant service notifications and responses to support requests.
· Reviewing Designer specifications and performing requested configuration, implementation, development and other authorized work.
· Monitoring reliability, diagnosing errors, preventing fraud and misuse, enforcing access restrictions, maintaining audit records and protecting customers and the Services.
· Meeting applicable legal and accounting requirements, resolving disputes, responding to lawful requests and enforcing agreements.
· Improving reliability, workflows and software using operational diagnostics, feedback and appropriately generalized or de-identified information, subject to confidentiality and contractual limitations.
We do not obtain ownership of Customer Data by processing it, and we do not use identifiable Customer Data to develop products for unrelated customers in a manner that discloses the original Customer's confidential information. Where laws require a particular legal basis for our own processing, that basis may include providing a requested service, meeting legal duties, our legitimate business interests or consent where required. The Customer determines the appropriate legal basis for the information it controls.
6. Artificial intelligence and Designer information
The active Designer feature uses an Anthropic AI service to help collect requirements, create a workspace briefing and draft software specifications. To perform a request, relevant chat messages and contextual information, such as the workspace name, available module names, prior specifications and related conversation context, may be transmitted to Anthropic for model processing. The generated response is returned to the Services and may be kept with the related conversation or specification.
Hepner personnel may review Designer conversations and outputs to provide requested support or custom-development services. Generated specifications and other AI outputs may be incomplete or inaccurate and should be reviewed before operational reliance. The Designer feature is intended to generate text and specifications, not independently modify the Customer's outside systems.
We do not authorize the use of Customer confidential information to train publicly available or unrelated third-party AI models without separate Customer authorization. The specific processing and retention practices of an AI provider are also governed by that provider's applicable contractual arrangements and service settings. We do not claim a particular zero-retention or no-training configuration unless it is separately documented and verified. Other proposed AI capabilities, including QMS AI functions, are not necessarily enabled.
7. Time Tracking, pay details and employment information
The Time Tracking module allows a Customer to record worker time and administer business attendance and labor-cost workflows. It may hold information that workers reasonably regard as sensitive, including compensation, working patterns, leave requests and optional clock-in or clock-out positions. A time-off reason may reveal health or family circumstances even though the module is not intended to collect medical records.
The Customer controls the people entered into the module, its use of location settings, its personnel permissions and its employment and recordkeeping policies. Access to pay information is permission-restricted within the module. We process these records to provide the service, support it and meet the Customer's documented instructions and our applicable obligations. The module is not a mechanism for us to continuously monitor workers, and Hepner Sync is not the employer of the workers recorded by the Customer.
8. ERPSync / QMS records, documents and signatures
Customers given access to ERPSync or QMS through the portal may use an application with separate account permissions and a separate underlying database and storage environment. When a user launches that application, the portal may transmit the user's identifier, name, email address, workspace identity and assigned role, along with limited support-session information where applicable, to enable authorized sign-in.
QMS records can include business-sensitive documentation, supplier details, audit findings, corrective actions, approvals, version histories, electronic-signature evidence and related files. As designed, certain signed and historical records are preserved, archived or protected from ordinary deletion to maintain traceability and an audit history. Features identified as prototypes or not enabled are not represented here as functioning data-collection processes.
Customers decide which records to upload and are responsible for determining any specific regulatory, employment, record-retention or data-protection requirements that apply to those records. A separate written arrangement may be required before using the Services for specially regulated information.
9. Integrations and third-party services selected by Customers
When a Customer enables the Home Depot / ICONX to Builder Prime integration, the Services may retrieve leads and related contact details from the Customer's Home Depot account, transmit them to the Customer's Builder Prime account, and exchange status changes. Integration credentials are stored for that authorized purpose. The Customer determines which external accounts to connect and must comply with the relevant third parties' agreements and privacy obligations.
Some actions open third-party services, such as Microsoft Bookings for meetings or Stripe for payment management. Information entered directly into their pages may be processed under those providers' own privacy terms. We do not control independent privacy practices of customer-selected integrations.
10. Who may receive information
We disclose information only as reasonably needed for the Services, legitimate administration or applicable legal obligations, including to:
· Customer-authorized users: owners, administrators, managers and members according to the Customer's permissions and the enabled module.
· Authorized Hepner personnel and supporting affiliated operations: staff working on support, security, billing, diagnostics or approved development, using available access controls and auditing.
· Hosting and service providers: the vendors described in Appendix A that provide infrastructure, authentication, billing, email, background processing, AI, diagnostic monitoring and scheduling.
· Customer-selected external platforms: such as Home Depot and Builder Prime, when the Customer enables the relevant integration.
· Authorities or transaction parties: where disclosure is required by law, necessary to protect rights and security, or appropriate for a legitimate business reorganization subject to applicable confidentiality and privacy protections.
We do not sell Customer Data or disclose it to advertisers for third-party targeted advertising. The portal's documented implementation does not include advertising pixels or session replay. We will update this Policy and provide any legally required choices if those practices materially change.
11. Cookies and similar technology
The portal uses authentication and session technology needed to recognize signed-in users and protect access. A temporary session indicator may also support authorized diagnostic "View as" functionality. Such cookies and similar mechanisms support essential login, account security and application operation.
Separate public websites or third-party booking or payment pages may have different cookie practices. Browser settings may allow you to block or clear cookies, but disabling essential session cookies can prevent the portal from operating as intended. We do not currently identify a nonessential advertising-cookie program in the portal that requires an advertising opt-out interface.
12. Security and authorized support access
We use administrative and technical measures designed to protect information appropriate to the Services. These include workspace-based access controls, restricted database access, optional authenticator-based two-factor authentication, private file storage, time-limited links or codes for certain actions, encrypted storage of external integration credentials, and logging of sensitive events. A workspace setting can require a second factor to open certain external applications.
Authorized Hepner personnel may need to access workspace information to solve incidents, carry out approved work, investigate security events or help with billing and administration. The portal supports time-limited, labeled support access and an audited diagnostic viewing mode. The viewing mode restricts certain write operations and certain sensitive views; support access may provide broader administrative permissions when required for an authorized task.
No software system can guarantee absolute security. We do not represent that the Services hold any particular security certification, audited control report or guaranteed recovery objective unless expressly provided in a separate signed agreement. Where a security incident triggers a notice requirement, we will provide notices as required by applicable law or an applicable agreement.
13. Retention, archiving, exports and deletion
We retain information for periods appropriate to delivering active Services, supporting the Customer's operations, maintaining business and audit records, meeting legal obligations and protecting legitimate interests. The period depends on the record type and applicable agreement. Canceling a subscription or removing a user's access does not automatically erase the associated workspace data.
Certain time records, revisions, audit events, integration history, stored files and QMS signatures may be archived or preserved for integrity, recordkeeping, backup, security or legal reasons. The Services currently do not provide a universal self-service deletion function or a single complete export of every data category.
Customers may use the export capabilities available in the modules. Under the Terms of Service, after effective termination of all relevant paid access, a Customer may request a commercially reasonable export of accessible business data within 30 days. The format and scope will depend on technical feasibility, legal restrictions and any signed agreement. Additional migration or transformation work may require a separately agreed fee.
Requests for access, correction or deletion may be directed to us as described below. We will evaluate them under the applicable law, Customer instructions and legitimate retention requirements. If information must be removed under applicable law, we will take the steps required by that law; some audit, backup or preservation records may remain restricted for as long as a lawful exception applies. We do not promise immediate physical erasure of every record upon a cancellation request.
14. Your privacy rights and choices
The privacy rights available to an individual depend on where the individual lives, the information involved and whether Hepner Sync or a Customer controls it. Where applicable, these rights may include requesting access or a copy, correcting inaccurate personal information, requesting deletion, objecting to or restricting certain processing, or receiving a portable copy. Applicable law may also provide rights to appeal a denied request or to contact a supervisory authority.
For data supplied by your employer or another Customer: Contact that organization first, since it normally determines the purposes of processing, access permissions, data accuracy and lawful retention. We will assist the Customer in responding where required. We may forward a request to the relevant Customer or ask the requester for enough information to identify the proper organization.
For information we control directly: Contact info@hepnerconsulting.com with the subject "Hepner Sync Privacy Request". Please describe the relevant account, workspace or information and the action requested. We may verify identity and authority before responding and will apply any legally required response or appeal process. We will not discriminate against a person for exercising privacy rights protected by law.
You may also review certain workspace details, manage access with your organization, configure optional authentication features, adjust available notification settings, or control device location permissions through the relevant browser or device. Employees should address workplace tracking or timekeeping choices with their employer.
15. International processing and location of information
Hepner Sync is operated from the United States. Infrastructure and other service providers may process information in the United States and other places where they operate or provide support. We do not promise that all information stays in a specific country or state unless a signed agreement expressly provides that commitment.
If data protection law applicable to an international Customer requires particular transfer safeguards, processing instructions or a data processing agreement, the parties should arrange those terms before submitting the affected data. Nothing in this Policy limits rights that individuals have under applicable mandatory data protection law.
16. Information the Services are not intended to receive
The currently described portal modules are not intended as repositories for full payment-card details, card security codes, government identity numbers, protected health records or children's personal information. Customers should not upload those categories, or other information subject to specialized processing requirements, unless the applicable module expressly supports it and the required contractual, compliance and security arrangements have been completed.
The Services are intended for business use by adults and are not designed for children to create accounts. A Customer remains responsible for lawful handling of any information about other people that it provides through its business records.
17. Changes to this Policy
We may update this Policy to reflect changes to the Services, vendors, data uses, legal obligations or privacy practices. The public version will state its last-updated date and version. If a material change affects how personal information is used, we will provide additional notice or obtain consent where applicable law requires it. Changes to this privacy notice do not, by themselves, amend a separately signed agreement or replace the clickwrap acceptance procedures for the Terms of Service.
18. Contact and related agreement
For questions about this Policy, security or privacy matters, or requests concerning personal information, contact:
Hepner Sync LLC
Privacy inquiries: info@hepnerconsulting.com
Subject line: Hepner Sync Privacy Request
Portal: https://app.hepnersync.com
Terms of Service: https://www.hepnercorp.com/hs-tos
Appendix A. Service providers and data recipients
The following providers are used in the portal architecture described by this Policy as of the stated update date. The information categories depend on which modules a Customer enables. A provider's role may vary between processing on our behalf, independent payment or scheduling functions, and
Customer-enabled integrations: Home Depot / ICONX and Builder Prime receive or supply information based on the Customer's instructions and its own accounts. They are not represented here as Hepner Sync's general-purpose hosting subprocessors. Other vendor or module arrangements may be covered in a signed data processing agreement or module-specific notice.
