Privacy policy
DailyLogsPro Privacy Policy
Effective and last updated August 11, 2026. This policy explains how Morton Technologies LLC ("Morton Technologies," "DailyLogsPro," "we," "us," or "our") collects, uses, discloses, and protects personal information through DailyLogsPro websites, mobile applications, web applications, support channels, and related services (collectively, the "Service").
1. Scope and customer-controlled information
This policy applies when DailyLogsPro determines why and how personal information is processed. Business customers also submit and control project information through the Service. For that customer-controlled information, Morton Technologies generally processes the information on the customer's behalf and according to its instructions. The customer is responsible for its own privacy notices, permissions, employment practices, contracts, and lawful collection and use of information about employees, subcontractors, clients, signers, and other project participants.
This policy does not govern third-party websites or services linked from DailyLogsPro, including PayAppPro, LienWaiverPro, app stores, payment providers, or customer systems. Their policies govern their independent processing.
2. Information we collect
Information you or your organization provide
- Account and organization information: name, email address, password credential, company, trade, role, organization membership, invitation status, and account settings.
- Subscription and transaction information: plan, billing status, subscription dates, and transaction identifiers. Payment card details are handled by our payment processor and are not intended to be stored by DailyLogsPro.
- Project content: project and client details, addresses, daily logs, work descriptions, labor and crew information, weather, site conditions, equipment, deliveries, inspections, delays, notes, potential changes, change-order scope and pricing, approvals, signatures, uploaded photos, captions, and generated reports.
- Communications: contact-form entries, support requests, emails, feedback, and product-alert preferences.
Information collected through use of the Service
- Device and technical information: IP address, browser, operating system, app and device identifiers, device-session information, timestamps, referring page, error data, and security or diagnostic logs.
- Usage information: pages and features used, actions taken, record status changes, approvals, uploads, exports, and integration activity.
- Location: jobsite or device location when a user grants device permission and uses a feature that records geographic context. Users can control permission through device settings, but disabling it may limit verification features.
- Offline information: project information, logs, and photos may be temporarily stored on a user's device so the Service can work without a connection and synchronize later.
- Website analytics: DailyLogsPro uses Google Analytics to understand visits and site performance. Analytics technologies may receive device, browser, approximate location derived from IP address, page, referral, and interaction information.
Information from other sources
We may receive information from organization administrators, invited users, connected services such as PayAppPro, payment processors, email providers, app stores, security providers, and publicly available business sources.
3. How we use information
- Provide, authenticate, synchronize, maintain, and support the Service
- Create accounts, manage organizations, roles, devices, projects, subscriptions, and integrations
- Store customer content and generate reports, exports, change orders, and related records
- Process requested transactions and send operational messages
- Respond to contacts, support requests, demonstrations, and product inquiries
- Send product news or marketing when permitted and honor opt-out requests
- Monitor performance, troubleshoot, analyze usage, and improve product usability
- Protect accounts, detect fraud or abuse, enforce agreements, and investigate security incidents
- Comply with law, legal process, and legitimate regulatory requests
- Establish, exercise, or defend legal claims
We do not use customer project content to train public or general-purpose artificial intelligence models.
4. How we disclose information
We may disclose information in the following circumstances:
- Within the customer's organization: according to roles, permissions, project access, and administrator instructions.
- Service providers: hosting, cloud storage, encryption and key management, databases, email delivery, payment processing, analytics, customer support, security, logging, and professional services.
- Connected services: when an authorized administrator enables an integration or directs a transfer.
- Legal and safety reasons: when reasonably necessary to comply with law or legal process, protect rights or safety, investigate misconduct, or secure the Service.
- Business transactions: in connection with a financing, merger, acquisition, reorganization, sale of assets, or similar transaction, subject to appropriate confidentiality protections.
- With direction or consent: when the customer or affected person asks us to disclose information.
We do not sell customer project records as a data product. We do not sell personal information for money or use customer project content for cross-context behavioral advertising. Website analytics providers may process website interaction information as described above; browser privacy controls and provider opt-out tools may limit some analytics collection.
5. Cookies, analytics, and communications
We use session cookies and similar technologies for authentication, security, preferences, and form protection. We use Google Analytics on the public website. Browser settings may block cookies, but doing so can affect functionality.
Operational email may include invitations, security notices, subscription information, support responses, and service changes. Marketing and product-alert messages will include an available opt-out method. An opt-out from marketing does not stop necessary account or service communications.
6. Security
We use administrative, technical, and organizational safeguards designed for the nature of the Service. Published controls include individual accounts, role-based access, revocable sessions, password hashing, encrypted transport, and encrypted storage for photos and generated documents. More information appears on our Security page.
No transmission, device, storage system, or security control is completely secure. Customers and users must protect credentials, use individual accounts, manage membership and devices, maintain appropriate exports or backups, and notify us promptly of suspected unauthorized access.
7. Retention and deletion
We retain information for as long as reasonably necessary to provide the Service, maintain account and project history, comply with customer instructions and contractual commitments, meet tax, accounting, security, and legal obligations, resolve disputes, and enforce agreements. Retention varies by information type, account status, customer configuration, legal hold, and backup cycle.
Organization administrators may control project access and certain deletion or export actions. When an account ends, customers should export records they must retain before access expires. Deletion requests may not immediately remove information from encrypted backups, security logs, transaction records, or records we must preserve by law or for legitimate claims. Residual copies are isolated from ordinary use and expire under applicable retention processes.
8. Privacy choices and requests
Depending on where a person lives and applicable law, they may have rights to request access, correction, deletion, or a portable copy of personal information; object to or restrict certain processing; withdraw consent; or appeal a denied request. Applicable laws may provide exceptions, particularly when information is controlled by an employer or business customer, needed for security or legal claims, or contained in records another party must retain.
For information controlled by a DailyLogsPro customer, contact that organization first. We will assist customers with verified requests as appropriate. For website, account, or direct relationship requests, email support@dailylogspro.com. We may verify identity and authority before acting. Authorized agents may be required to provide proof of authorization. We will not unlawfully discriminate against a person for exercising applicable privacy rights.
California residents may have rights to know, correct, delete, and obtain information, and to opt out of sale or sharing and limit certain uses of sensitive personal information when those activities occur and the law applies. As described above, DailyLogsPro does not sell personal information for money and does not use customer project content for cross-context behavioral advertising.
9. Children's privacy
The Service is designed for businesses and construction professionals, not children. We do not knowingly collect personal information directly from children under 13. If you believe a child provided personal information without appropriate authorization, contact us so we can investigate and take appropriate action.
10. United States processing and international users
DailyLogsPro is operated from the United States, and information may be processed and stored in the United States and other locations where authorized providers operate. Customers using the Service from another country are responsible for determining whether additional notices, contracts, transfer mechanisms, or local requirements apply.
11. Changes to this policy
We may update this policy to reflect changes in the Service, law, or business practices. We will post the updated policy with a revised date and provide additional notice when required. Continued use after an update is subject to the revised policy, except where applicable law requires another form of notice or consent.
12. Contact us
Morton Technologies LLC
DailyLogsPro Privacy
support@dailylogspro.com
For account-specific requests, include the organization name and email address associated with the account. Do not send passwords, payment card numbers, or sensitive project attachments by ordinary email.
