CDG Mitigation, LLC · Software Privacy Policy
This policy covers the CDG Mitigation apps and websites listed below.
This policy explains how information is handled when you use CDG Mitigation, our practice-management software for restoration and mitigation contractors, through:
The iOS app is not yet available on the App Store. This policy will cover it once Apple approves it.
The apps are operated by CDG Mitigation, LLC ("CDG," "we," "us"), which is responsible for this policy. Our affiliate CDG Hangar LLC (formerly Cerrito Development Group LLC), which is under common control with us, holds the software rights and our Apple developer account, so Apple's App Store may show the developer as "Cerrito Development Group LLC".
The apps are business tools. They are used by restoration contractors and their employees and other authorized users. They are not consumer apps. There is no sign-up or purchase inside the apps; an administrator creates user accounts.
This policy covers the apps only. Our company websites are covered by separate policies. See section 13.
There are two situations, and they are not the same. In the rest of this policy, "the customer" means the restoration company that operates the deployment you use (CDG Mitigation, LLC, for its own deployment).
Application data is held by the company that operates the deployment, together with the service providers it uses to host, back up and support that deployment, including CDG where CDG hosts it (section 6).
CDG Mitigation, LLC and CDG Hangar LLC are under common control. CDG Hangar LLC holds the software rights.
Two different roles apply, depending on the information.
| Information | Who decides what is collected and why | Our role |
|---|---|---|
| Customer Data: what the customer and its users enter into or capture with the apps about their own business. This includes jobs and claims, homeowner and property contact details, photos, documents and signatures, notes, financial records and canvassing data. | The customer. | Where CDG hosts the deployment for a customer other than CDG itself, we host and process Customer Data on the customer's behalf and on its instructions, to provide the service. The customer is responsible for having a right to collect and use the information about homeowners and others that it enters. |
| Sign-in and account data for the customer's users. | The customer's administrator decides who gets an account and what access they have. | We operate the sign-in system. Passwords are stored only as salted one-way hashes (Argon2id on our servers), never in readable form. Sign-in sessions and access keys are stored only as one-way digests. Sessions expire after 12 hours. After repeated failed sign-in attempts an account is temporarily locked, and repeated failures from one network address are refused. The customer's administrator can revoke a user's sessions and access keys at any time. |
| Service operation data: server and security logs, backups and support records that we need in order to run, protect and repair the service. | We do. | We are responsible for this information and use it only for the purposes in section 4. |
If your information is on CDG's own deployment, contact us (section 14). If your information is in another company's account on a deployment CDG hosts, for example because you are a homeowner or a property owner whose job that company recorded, that company is the organization to ask first about how your information is used, and CDG will pass your request on and help it respond. See section 9.
For each user account we store: full name, work email, phone number, employee reference, job title, professional certification and its expiry date, role assignments, account status, and the dates the account was created, last updated and last signed in to. For sign-in security we store a one-way hash of the password, one-way digests of sign-in sessions and access keys, the network (IP) address and time of sign-ins and of access-key use, a label for each access key, and a record of sign-in attempts, including failed ones. Activity records can also include the device's location when an entry is made.
The application records actions taken in the apps, tied to the user and access key used, including requests that were denied. We keep these records so that an organization can see who did what and so we can secure the service.
Names, phone numbers, email addresses and job-site or property addresses of a customer's clients, homeowners, leads and contacts. Also do-not-contact markers, dispatch details and records of doorstep or home-solicitation agreements, including the homeowner's signature and payment-timing details. This information is entered by the customer's users. We do not collect it directly from homeowners.
Claim and loss file details, project scopes, moisture and drying readings, equipment records, estimates, contracts, change orders, purchase orders, invoices and payments. If a customer imports an estimate from Xactimate, we store both the imported lines and the original file.
Job photos, generated documents such as carrier packages and client paperwork, and signatures drawn on screen. When you use the web or iOS app, job photos you upload are stored on our servers, and we remove location data (GPS coordinates) that your camera may have embedded before the photo is stored. When you use the Windows or macOS desktop app, photos you add are copied into a folder on your computer exactly as they are, including any location data your camera embedded. Photos uploaded before 25 September 2026 were stored before this location removal began and may still contain location data.
The apps include map and canvassing tools. Location is used only while the app is open and in use; we never collect it in the background. In the web office app, your location is captured only when you tap "Attach current position" while recording a canvassing visit. In the CDG Canvass field app, your device's location is captured automatically, for up to about 10 seconds, each time you record a door knock or add a new door, if you have allowed location access. Recorded coordinates are stored on your company's server with the visit, your user account and the time. If you are offline, they are held on your device until they can be sent. While you view the canvassing map, your location is used to show where you are; that map position is not sent to or stored on our servers. If the desktop app is not linked to our servers, canvassing coordinates are stored only in the app's local database on your computer. On iPhone and in web browsers, location is requested through a permission prompt; on the desktop apps, it follows your computer's privacy settings. You can decline or revoke it. See section 5. Maps are drawn using tiles from OpenStreetMap. See section 6. Satellite views load map images from Esri (section 6). The apps also include an optional address-lookup feature that is off by default. See section 6.
When you connect to our servers, our systems record technical information: your IP address, the date and time, the page or address requested, the response, the referring page, and your browser or app's user-agent string. We use it to run and secure the service. When you search in the web office app (including inside the iOS app), your search terms are sent to our servers as part of the page address requested. Our web server logs record that full address together with your IP address and your browser or app's user-agent string; these logs are kept for about 15 days and are used to operate and secure the service. The desktop app searches its own local data and does not send your searches to us. We do not use search terms for tracking. Separately, we keep a security and activity record of signed-in actions, sign-ins and access-key use, which also includes the IP address used. Our web server logs are deleted automatically after about 15 days (error logs after about one month). The sign-in and activity records that include an IP address have no automatic deletion; we keep them for as long as the account's data is kept, because they form part of the audit trail, and copies in backups are kept for up to 2 years.
The macOS and Windows desktop apps keep a local copy of data on your computer so they can work efficiently, plus a folder of photos. The app also makes an automatic backup of the local database once a day and keeps the 14 most recent backups, and an administrator can create an additional backup at any time. These files are stored as ordinary files in your user profile's application-data folder, protected by your computer's user account and any disk encryption you use, such as BitLocker or FileVault; the app does not add its own encryption to them, so backup files are unencrypted copies of the full local database. The key the desktop app uses to connect to our servers is stored encrypted by your operating system. Protect these files as you would any business records.
We and the customer that operates a deployment use information in the apps to:
We do not sell your personal information.
Depending on the app and your device, the apps may ask for permission to use:
On iPhone and in web browsers, you are asked before each one is used. On the desktop apps, access is controlled by your computer's privacy settings. You can change or revoke a permission at any time in your device settings (iOS Settings, macOS System Settings or Windows privacy settings), or in your browser's site settings for the web office app. You can decline location access and keep using the apps. Canvassing visits will be saved without a location, and the map will not show your own position. The web office app is permitted to use the camera and your location on its own pages, and is not permitted to use the microphone or browser payment features.
Before you photograph someone's property, make sure you have the right to do so. Do not use the apps to photograph or record people without their awareness.
We share information only as needed to run the service, and as described below.
| Recipient | What they receive | Why |
|---|---|---|
| Our hosting infrastructure. Our servers are hosted by Hostinger on a virtual private server located in the United States (Boston, Massachusetts). CDG administers the server, which runs the database, API and web office app. Where we host the service for another restoration company, that company's deployment runs on its own separate server and database. | All information in the apps. | To store and serve the data. |
| Backup copies. We back up the service database and uploaded files every six hours to storage on the same server, accessible only to system administrators. Each backup is checked by a test restore. Backups are compressed but not separately encrypted. Section 7 explains how long backups are kept. | A copy of the data. | Backups. |
| OpenStreetMap Foundation (map tiles). When a map is displayed, your device requests map images directly from OpenStreetMap's tile servers (tile.openstreetmap.org). OpenStreetMap receives your IP address, your browser or app's user-agent, the map area requested (which may be centred on the property being worked on), and our website's address (api.cdgcorp.net) as the referring site. We do not send OpenStreetMap your account or job data. | Standard web-request data from your device. | To draw maps. Their privacy policy applies: https://osmfoundation.org/wiki/Privacy_Policy |
| Address lookup (optional, off by default). The apps include an optional feature that converts a property address into a map position. No address-lookup provider is currently connected, so no address is sent to one. If we connect a provider, we will name it here before it is used. | ||
| Esri (satellite map images). When you choose the satellite view, your device requests map images directly from Esri's ArcGIS Online servers (server.arcgisonline.com). Esri receives your IP address, your browser or app's user-agent, the map area requested (which may be centred on the property being worked on), and our website's address (api.cdgcorp.net) as the referring site. We do not send Esri your account or job data. | IP address and map area from your device. | To draw satellite maps. Esri's privacy statement applies. |
U.S. National Weather Service and a university storm-report service (api.weather.gov and mesonet.agron.iastate.edu). No customer data is sent to either service. As those services ask, each request identifies our app and includes a CDG contact email address (a general CDG operations address or, for some requests, the work address of a CDG staff member). |
No customer, property or claim information. | Storm alerts and historical storm reports. |
| De-identified aggregated data recipients. | Aggregated information that cannot reasonably identify a customer, homeowner, carrier, claim or property. | Benchmarking and industry analytics. |
| Legal and safety. | Information that we are legally required to disclose, or need to disclose to protect rights, property or safety. | Legal process. |
| Business transfers. | Information may transfer to a successor if CDG is sold or reorganized, subject to the agreements that apply to that information. | Corporate transactions. |
The CDG Mitigation apps do not send email or text messages on your behalf and do not use an email or text-message service provider. Where the app shows an email address as a link, tapping it opens your own email app. If we add a messaging provider in the future, we will update this policy.
Each customer decides what to share from its own account. For example, a customer may send a carrier package to an insurance carrier. We do not control those disclosures.
There is no live connection to QuickBooks or Xactimate.
The customer controls what is kept in its account, and customer administrators can use the export tools that the apps provide.
When a customer's use of the service ends, we make the customer's data available for export for a reasonable period and give the customer notice before we permanently delete it. We then delete it from our production systems. Copies held in backups are not restored for operational use and expire on our backup schedule (see Backups below). We do not offer paid extended archiving. Customers may have their own legal duties to keep claim and business records.
We back up the service database and uploaded files every six hours to storage on the same server, accessible only to system administrators. Each backup is checked by a test restore. Backups are compressed but not separately encrypted. We keep every backup for 7 days, one per day for 90 days, and one per month for up to 2 years. A small number of manual safety copies made before system changes are kept longer. Information deleted from the service may remain in these backups until they expire.
The application records certain entries, such as moisture and drying readings, payment records, synchronization logs, signatures and activity logs, as new entries rather than by overwriting earlier ones, and the system does not currently provide a way to edit or redact them. Where such a record contains personal information, we work with the customer on how a request to delete it is handled.
Any user can ask us to delete their account at any time from Your Account in the app (tap your name at the top of the screen) by choosing Request account deletion, whichever way they sign in. We complete a request within 7 days and confirm when it is done (where another company operates the deployment, that company's administrator completes it). Most users who sign in with an email address and password can also close their account immediately themselves. You can also ask for deletion by emailing legal@cdgcorp.net. Deleting or closing an account removes your email address, phone number and password, and permanently revokes every sign-in session and access key issued to you. Some information is kept: your name, job title, employee reference and certification details; your organisation affiliation and support-access settings; your role assignments; records of your past sign-ins, access keys and sign-in attempts, including the network (IP) addresses and devices used; the activity log of what you did in the app; and the work you recorded, such as inspections, readings, photographs and signed customer paperwork. These are kept because they form part of claim and audit records. The desktop app and the online service keep separate accounts, so closing your account in one does not close it in the other. An administrator can deactivate a user. Deactivation immediately ends all of that user's sign-in sessions and revokes all of their access keys, and removes them from active user lists, while their work, job and audit records are preserved. Deactivation does not remove the user's contact details. To ask us to delete other information we control, contact us using section 14.
We use administrative and technical safeguards that are commercially reasonable, including:
When we delete or dispose of records containing personal information, we erase them or make them unreadable, or otherwise take steps we reasonably believe prevent unauthorized access. Deleted information may remain in backups until those backups expire (see section 7).
No method of storing or transmitting information is completely secure. We cannot guarantee absolute security.
If we learn that personal information we hold has been acquired without authorization, we will notify affected individuals and our business customers in the most expedient time possible and without unreasonable delay, consistent with the legitimate needs of law enforcement and with the steps needed to determine the scope of the incident and restore the reasonable integrity of our systems. We notify our business customers so that they can meet their own obligations. We follow this notice standard, which comes from the Georgia Personal Identity Protection Act (O.C.G.A. §§ 10-1-910 to 10-1-912), as our own commitment.
If your information is in a customer's account (for example, you are a homeowner or property owner, or an employee of the customer): contact that customer first. It decides what it collects and can access, correct, export or delete information in its account. Where the customer is CDG Mitigation, LLC (its own deployment), contact us using section 14. If you contact us about another company's account instead, we will forward your request to that company and help it respond, unless the law requires us to act on it ourselves.
If you are a user of the apps: ask your organization's administrator for access, corrections or account closure. You can control device permissions as described in section 5.
Information we control (service operation data and any account data for which we are independently responsible): you may ask us for access, correction or deletion. We may need to verify who you are, and we may keep information we are legally required or permitted to keep.
Additional rights. Privacy laws differ from state to state. This policy applies to everyone who uses the apps, wherever they live. If your state gives you additional rights, contact us and we will handle your request in line with applicable law.
Georgia law. CDG Mitigation, LLC is a Georgia company. Georgia has no general consumer-privacy statute. Our breach-notice commitment in section 8 follows the Georgia statute cited there.
The apps are business tools for adult staff. They are not intended for anyone under 18, and we do not knowingly collect personal information from children. If you believe a child's information has been entered, contact us and the customer whose account holds it.
Information is stored on servers that CDG administers. Our servers are hosted by Hostinger on a virtual private server located in the United States (Boston, Massachusetts). Where we host the service for another restoration company, that company's deployment runs on its own separate server and database. Desktop apps also store a copy on the computer where they are installed.
If we change this policy, we will post the updated policy on this page with a new effective date.
Our company websites are covered by their own privacy notices.