Privacy Policy
Last updated October 16, 2026
CodeCheck Pro LLC, a Florida limited liability company (CodeCheck Pro, we, us), provides document review tools for construction and insurance claims. This Privacy Policy explains how we handle information about website visitors, web and mobile account users, organizations, and people whose information appears in submitted documents.
The Service means the CodeCheck Pro website at codecheckpro.com, web application at app.codecheckpro.com, CodeCheck Pro mobile applications for iOS and Android when available, document processing, findings, reports, account features, and related support. This Privacy Policy applies across these channels.
We store and process original adjuster summaries to provide the Service. Where permitted by law, source restrictions, and applicable platform rules, we may create, retain, sell, and license qualifying Commercial Data and keep the revenue. We do not sell personal information or personal and sensitive data obtained through our mobile apps. Account deletion, case deletion, and how long we keep information are explained in Section 6.
The EULA governs access, report use, and payment obligations. This Policy describes information practices and available privacy rights. A use must satisfy both documents. If their privacy or data-use provisions cannot be reconciled, the provision permitting the narrower use or providing greater protection for the information controls. Mandatory law and binding customer-specific confidentiality or processing restrictions remain controlling; neither document removes another person's rights. This Policy does not create charges. Acknowledging it does not replace separate permission required for an optional use or third-party AI sharing.
1 Information we collect
Personal information means information relating to an identified or reasonably identifiable person or household, as defined by applicable law. It can appear in account records, documents, results, billing records, and usage data.
User Content means documents and information submitted to the Service, including original adjuster summaries, estimates, attachments, case details, corrections, and customer review decisions.
Account and contact information. We receive names, email addresses, organization names where applicable, account and role information, sign-in information, invitations, and communications from users, administrators, and people who contact us, along with optional profile details you choose to add. Support requests may include case references, claim numbers, insured names, property addresses, and information about a reported problem.
Documents and results. User Content may contain insured and claimant names, property addresses, claim and policy numbers, insurer and adjuster details, dates, estimate line items, photographs, document metadata, and other personal or business information. We also create extracted text, classifications, findings, reports, review histories, and customer decision records.
Property addresses. We process property addresses entered or extracted from documents, including addresses checked for eligibility before a purchase, to identify the applicable jurisdiction.
Billing information. We receive plan selections, purchases, invoices, payment and refund status, transaction references, billing address and tax details, and limited payment-method details from our payment provider. The payment provider collects and processes payment credentials under its own terms and notices; we do not receive a full payment-card number. Do not put payment credentials in claim documents or support messages.
Usage and authorization records. We record account activity needed to operate, meter, and secure the Service, and records of agreement acceptance, order approvals, deletion requests, and privacy choices, to document authorized actions. These records and our service providers' operational logs may include technical information such as device and browser information, IP addresses, and timestamps.
Files and device permissions. When you select a document or image for upload, we receive the selected content and associated file information. If a feature offers camera capture, photo access, notifications, or another device permission, the permission request identifies the function before access. You can manage permissions through device settings. Denying a permission may prevent its associated feature. A device permission does not itself authorize unrelated collection, model training, or data sales.
2 Why we use information
We use information to create and secure accounts; manage authorized organization access; validate and process documents; identify the relevant jurisdiction and scope; generate findings and reports; record customer review decisions; and provide report history, downloads, and support.
We also use information to process subscriptions, purchases, approved additional reports, cancellation, refunds, and payment recovery; send service notices; investigate errors, misuse, or unauthorized uploads; maintain and test Service quality; protect security; meet legal duties; and establish or defend legal claims. Marketing communications include available unsubscribe choices.
Where we hold sufficient rights, we may process information to create qualifying Commercial Data for the purposes in Section 4. Ordinary Service improvement remains subject to the model-training restrictions in Section 5 and does not authorize unrestricted document resale. We limit sensitive information to necessary, permitted purposes and do not use incidentally received sensitive content to infer sensitive traits for marketing.
Where a law requires a legal basis, we use the applicable basis, such as performance of a contract with you, compliance with legal duties, legitimate interests where permitted and appropriately balanced, or consent where required. A contract with an uploader does not make everyone named in a document a party to that contract.
3 When information is disclosed
Service providers. We use service providers to operate the Service. The categories of providers, and the information they may receive, are:
- Hosting, operations, and storage providers: account, case, document, report, support, and operational information, to host and operate the Service and store information, including retained document copies described in Section 6.
- Communications providers: contact details and the content of service emails, which can include case details such as a property address or claim number.
- Payment processors: contact, billing, and transaction information, including the property a purchase relates to, to process payments, subscriptions, refunds, and taxes.
- Address and location services: property addresses, to identify the applicable jurisdiction.
- Productivity and AI-enabled tools used by our personnel: account and case information needed when our personnel administer and support the Service.
Providers handling user information for us are contractually restricted to authorized purposes and must provide protection at least equivalent to this Policy and applicable platform requirements.
App stores and sign-in. If you purchase through an app store or use an outside sign-in service where offered, that provider handles its own account and transaction information under its notices. Deleting a CodeCheck Pro account does not delete your Apple Account or Google Account.
Your organization and chosen recipients. Authorized people in your organization, including Office Managers and other administrators, may access account information, cases, uploaded documents, findings, review decisions, and reports according to their roles. Users should submit organization work through the correct account. We do not automatically send a report to an insurer or other claim participant merely because someone uploads a document.
You may download and share reports with authorized participants in a claim or project. If you direct us to disclose information through an available feature, we do so as instructed, subject to authority and applicable restrictions. The recipient's subsequent independent use may be subject to its own duties and practices.
Legal and business matters. We may disclose information to professional advisers or as required by law, or when reasonably necessary to investigate misuse, protect rights and security, or establish or defend claims. In a financing, merger, reorganization, or sale of the relevant business, information may be disclosed under appropriate confidentiality protections; a successor must assume applicable obligations. Such a transaction does not itself authorize broader data use.
Customer-directed processing. Our role depends on the activity and applicable law. For account administration and our own permitted purposes, we act as the responsible business or controller where those concepts apply.
When we process information solely as a processor or service provider for a customer, customer instructions and applicable processing restrictions govern. We do not use that information for our own commercial purposes unless a separate lawful arrangement expressly permits the use and all required notices, rights, and permissions are in place. Accepting standard terms does not override an existing processing restriction.
4 Commercial Data and data sales
Commercial Data means statistics, aggregated information, and deidentified datasets lawfully derived from User Content, reports, or Service activity that cannot reasonably be linked to an individual, household, device, property, claim, or uploading customer, either alone or together with reasonably available information. It must not reveal confidential business information and must meet applicable legal standards for deidentified or aggregate information. Removing names, masking an address, or hashing an identifier is not enough by itself.
Where we hold the necessary rights and applicable platform rules permit it, we may create, retain, combine with lawfully obtained information, analyze, publish, distribute, license, sublicense, sell, and otherwise commercialize qualifying Commercial Data. Uses include industry research, benchmarking, market trends, analytics, product development, and software or model development. CodeCheck Pro may retain all proceeds without paying users or providing attribution, subject to applicable law and source restrictions.
Examples include broad regional material trends, scope frequencies, and patterns in code-related findings. Recipients may include manufacturers, distributors, construction and insurance businesses, researchers, and software and analytics providers. Property-level lead lists, identifiable claim files, and confidential customer strategies do not qualify.
We assess identification risks before release, including reasonably available outside information, small groups, exact locations, dates, images, and metadata. We maintain qualifying data in deidentified form and do not attempt to reidentify it. We do not provide source documents or keys that would defeat deidentification.
Recipients of nonpublic Commercial Data must agree to maintain deidentification, prohibit reidentification, avoid contacting people or targeting identifiable claims or customers through the data, and apply equivalent restrictions to permitted onward transfers. Public releases are limited to aggregate statistics meeting these standards without reliance on recipient contracts; where law requires such contracts, we do not make that public release. We restrict further release and take reasonable corrective steps if data is found not to qualify.
We do not sell personal information or share it for cross-context behavioral or targeted advertising. A qualifying Commercial Data sale does not authorize selling original adjuster summaries, identifiable reports, or other identifiable information. Deidentification must actually meet applicable legal and platform standards; a label or the removal of names alone is insufficient.
Commercial Data permissions apply only where the collection, transformation, and intended use are permitted by applicable law, binding source restrictions, and the rules of the platform through which the information was obtained. We do not use a transfer to our servers, another service, or a different account to avoid those restrictions. Information that remains personal or sensitive data under an applicable platform rule is not eligible for a prohibited sale, even if it has been labeled deidentified. Consent does not override a platform prohibition.
Any proposed new personal-data use requires accurate notice, sufficient legal authority, any required separate permission, and compliance with platform restrictions. Ordinary uploads and EULA acceptance do not activate an identifiable-data sale program. An uploader's acceptance cannot replace another person's required consent.
5 Automated processing and AI
The Service uses optical character recognition, rules, and automated analysis to extract information and produce findings. These tools can make mistakes. Customers verify case details, review sources, resolve items requiring human judgment, and inspect reports. A manual-review label does not mean CodeCheck Pro has performed a human review. The Service does not decide insurance coverage, claim payment, or legal entitlement.
We do not send your documents to third-party AI providers to produce your results. Our personnel may use AI-enabled tools, under provider restrictions, when administering and supporting the Service, as described in Section 3.
We do not use identifiable User Content to train, fine-tune, or improve general-purpose or shared AI models, and we do not permit our providers to do so through ordinary Service use. Any such use requires separate, specific lawful authorization, appropriate provider restrictions, and compliance with platform rules. Processing a document for its requested analysis, investigating a reported error, or performing necessary security checks is distinct from model training. Qualifying Commercial Data may be used for model development within Section 4 and the EULA.
Before our mobile apps share personal data with a third-party AI provider, and in other cases where applicable law or platform rules require it, we disclose the provider, the information involved, and the purpose and obtain explicit permission. Permission is distinct from general acceptance of the EULA or Privacy Policy. Declining may make the affected feature unavailable; it does not authorize unrelated use of your information.
6 Account deletion and data retention
We keep original adjuster summaries, other User Content, extracted content, findings, customer decisions, and reports while your account or organization is open, so that you have your case and report history. Information is removed as described below. Keep your own originals and downloaded reports; the Service is not a permanent archive.
6A How to delete your account
In the app, use the Delete account option in your account profile and confirm. You may also email info@codecheckpro.com with Account Deletion in the subject line and enough information to identify your account. The email route is available without signing in or reinstalling the app. We verify identity and authority only as reasonably necessary, and an email request has the same result as the in-app route.
When a deletion is confirmed, your access ends immediately and your sign-in and profile are deleted. We email you a confirmation.
6B What happens to your information
A member of an organization. If you belong to an organization that continues, deleting your account removes your sign-in and profile immediately. The cases, documents, and reports you worked on are the organization's business records and stay with the organization, and your name or email address may remain on records you created. The organization's subscription continues.
The last manager of an organization. If you are your organization's only manager, you can delete your account only by closing the organization (or by first arranging a management transfer). Closing it:
- ends every member's access and deletes their sign-ins and profiles immediately;
- cancels future renewals of the organization's subscription; and
- keeps the organization's case information for 365 days in restricted storage, during which it is not accessible to the organization and you may ask us to restore it, and then deletes it. The confirmation email states the date.
A homeowner account. Deleting a homeowner account deletes your sign-in, profile, and saved payment methods immediately. Your case information is kept for 365 days in restricted storage, during which you may ask us to restore it, and is then deleted. The confirmation email states the date.
Deleting a case. Deleting a case removes it from the Service immediately.
Retained document copies. We retain copies of submitted documents and generated reports in restricted storage to support customers, investigate disputes and errors, and keep records of what was submitted. These copies are not removed when a case is deleted or an account is closed. You may request their deletion by emailing info@codecheckpro.com with Privacy Request in the subject line; we delete them unless an exception in Section 6D applies.
Copies you or another authorized recipient independently downloaded are controlled by that recipient; we cannot erase files outside our control.
6C Cancellation and export access
Ordinary subscription cancellation stops future renewals and leaves paid access in place until the billing period ends. An account that remains open then has 30 days of read-only access to download existing reports under EULA Section 11D. After that, cases cannot be accessed until a plan is chosen again, but the organization's information remains stored while the account stays open. To have it deleted, close the organization under Section 6A or contact us.
Closing an organization or deleting a homeowner account ends access immediately, including export access, even if a paid period has time remaining. Download needed reports before confirming deletion. We do not delay a deletion request until a paid period ends.
6D Records we keep
We keep the following records after the deletions above, because they are needed for legal, accounting, security, or dispute purposes, or to operate the Service:
- Billing, tax, and transaction records, including the property a purchase relates to.
- Agreement acceptance and authorization records.
- Basic account and organization records to which those records refer, and records that a deletion was carried out.
- Usage, security, and communication records.
- Retained document copies under Section 6B.
These records are access-restricted. Evidence subject to a legal hold is kept until the hold and applicable proceedings end. You may ask us to delete particular records; we explain any exception that applies when responding, unless law prohibits that notice. Operational logs are kept for a short period and then deleted.
6E Backups
Residual copies in our hosting providers' disaster-recovery backups are removed through their backup-rotation cycle, subject to applicable law and platform requirements. Pending removal, these copies are restricted from ordinary use, customer restoration, analysis, and training. If a backup is restored for disaster recovery, we reapply deletion instructions before the affected records return to ordinary use. Retained document copies under Section 6B are not disaster-recovery backups.
6F Commercial Data after deletion
Subject to applicable law, platform requirements, and binding source restrictions, qualifying Commercial Data lawfully created before the relevant case deletion request, account deletion request, organization closure, or end of paid access, whichever applies first to the source information, may be retained and commercialized afterward while it continues to qualify. Scheduling ordinary cancellation for the end of a paid period does not by itself end authorized processing during that period. An export period, the 365-day restricted period, a legal hold, a backup, retained document copies, or another limited retention does not authorize creating new Commercial Data from retained identifiable source documents. We do not reidentify Commercial Data or keep a linking key to defeat a privacy request.
7 Cookies, analytics, and communications
The Service stores sign-in and preference information on your device. We do not use advertising cookies. Browser and device settings can manage storage and permissions; blocking essential storage may prevent sign-in. Uninstalling an app may remove its local data but does not itself submit an account-deletion request or erase server records.
We do not use the practices described here for advertising based on activity across unrelated businesses. We honor legally recognized opt-out preference signals, including Global Privacy Control, where applicable. A general Do Not Track browser setting is different; we do not treat it as a separate standardized instruction.
To stop marketing emails, use the unsubscribe option or contact info@codecheckpro.com. Essential account, invitation, password, billing, processing, security, deletion-confirmation, and requested support emails may continue while relevant.
8 Your privacy requests and rights
Use the Delete account option in your account profile, or contact info@codecheckpro.com for account deletion, access or a copy, correction, deletion of particular information (including retained document copies), or a privacy concern. You do not need an account to email us. Describe the request and provide enough information to locate the relevant record; do not send unnecessary sensitive documents. Section 6 explains account deletion and retention.
Depending on your location, the information, and whether a law applies to us, you may have rights to know what information is collected, used, and disclosed; receive a portable copy; correct or delete information; opt out of sale or advertising-related sharing; limit certain sensitive-information uses; withdraw consent; or challenge qualifying automated decisions. You may also have a right to appeal a denial or complain to a regulator. We do not unlawfully discriminate or retaliate for exercising privacy rights.
We verify identity and authority when appropriate to the request and law, using no more information than reasonably necessary. Opt-outs are not subject to identity verification where law prohibits it. An authorized agent may submit a request with evidence of authority as legally permitted. We respond within applicable deadlines and explain a permitted extension or denial.
To appeal a decision, email the same address with Privacy Appeal in the subject line and identify the request. We review the appeal and explain the result and available further complaint options within applicable time limits.
If a contractor, adjuster, or other business uploaded your information, you may contact that business or us. We coordinate requests according to our role and legal duties. An uploader's contract does not eliminate your rights. Deletion may prevent a feature that requires the deleted information, and lawful retention exceptions may apply. We do not reidentify qualifying Commercial Data solely to answer a request.
The EULA's liability limits and uploader indemnity do not waive the independent rights of people who did not accept that Agreement or excuse our own legal duties.
9 Upload authority and unauthorized documents
Upload only documents you have authority to submit for the permitted uses. Remove unnecessary Social Security numbers, full financial account details, medical information, passwords, and unrelated personal data. Account authentication information belongs in the sign-in process, not in uploaded claim documents.
A document can contain information belonging to people who do not use CodeCheck Pro. The uploader must have sufficient authority and provide required notices or permissions. An upload by an authorized user does not establish that every person named has consented to every possible use.
Report suspected unauthorized content to info@codecheckpro.com with Unauthorized Upload in the subject line, enough information to locate it, and an explanation of the concern. We may request evidence, restrict access, pause processing, preserve required evidence, or remove affected content. We pause new commercial releases derived from disputed source content while assessing a credible authorization concern and notify affected parties when appropriate or required.
10 Security
We use reasonable administrative, technical, and organizational safeguards appropriate to the information. Access to nonpublic documents is limited to authorized personnel and providers for permitted purposes. No system is completely secure. If an incident requires notice, we provide it as applicable law requires. Protect your credentials and promptly report suspected unauthorized access.
11 Children and processing locations
The Service is intended for adults age 18 or older with authority to use the relevant account and documents. It is not directed to children. Do not intentionally submit unnecessary information about children. If you believe we received a child's information without appropriate authority, contact us so we can assess and address it. We do not knowingly sell children's personal information or share it for targeted advertising.
CodeCheck Pro is based in the United States. Information may be processed where we and our providers operate. Where cross-border transfers require legal safeguards, we use those safeguards. Use of the Service does not waive rights that apply in your jurisdiction.
12 External services and links
The Service may link to code publishers, public records, payment providers, app stores, or other external services. Those services have their own privacy practices. This Policy governs information we handle, including disclosures we make; it does not govern another service's independent handling of information you provide directly to it. Our processing providers remain subject to our applicable contractual requirements.
13 Changes to this Policy
We display the last updated date and provide additional notice when required or appropriate for material changes. A Policy update alone does not broaden rights over information subject to existing commitments, authorize a new identifiable-data sale or shared-model training use, or change subscription terms.
Before a broader use, we obtain any additional authority or consent required by the EULA, existing commitments, and applicable law. Continued use is not a substitute for required consent. Binding customer-specific restrictions remain unless validly amended.
14 Contact us
CodeCheck Pro LLC Email: info@codecheckpro.com Website: codecheckpro.com Web application: app.codecheckpro.com Mobile applications: CodeCheck Pro for iOS and Android when available
Use Account Deletion, Privacy Request, Privacy Appeal, or Unauthorized Upload in the subject line when relevant. You may also request this Policy in an accessible format.