RuufLink™ is a lead marketplace operated by ASNGS Group Holdings LLC.

1. Information we collect

From homeowners: project details (project type, ZIP code, city, timeline, roof age and roofing material) and contact details (full name, property address, mobile number and email).

From roofing companies: business name, contact information, service areas, CSLB license number, license holder name, license classification, license expiration date, and purchase history.

Automatically: when you visit the Site we may collect your IP address, browser type, device information, pages viewed, and the dates and times of your visits. We also collect first-touch marketing attribution data such as UTM source, UTM campaign, UTM medium and landing page, linked to a persistent visitor identifier stored in a cookie.

2. Cookies and first-touch attribution

We use cookies and similar technologies to recognize returning visitors, preserve first-touch marketing attribution (for example, which ad or link brought you to the Site), and support marketplace analytics. The visitor identifier persists until you clear your browser cookies. You can remove or block cookies through your browser settings; doing so may affect attribution tracking but will not prevent you from submitting a roofing request.

We use advertising measurement tags from Google, Meta and OpenAI to measure whether our ads lead to completed roofing requests or contractor applications. These tags may set or read a first-party cookie and report a conversion event (for example, a completed contractor registration) to the advertising platform, linked to the ad click or view that brought you to the Site. We do not send your name, phone number, email address or street address in these measurement events.

3. How we separate personal information

Homeowner contact details are stored in a separate, access-restricted table from the project details listed in our marketplace. Roofing companies browsing available projects can never read that table. Contact details are released only through a controlled server-side check that confirms a completed purchase for that exact project.

4. Phone verification and transactional text messages

When you submit a roofing request, we send a one-time code by SMS to the mobile number you provide. The code is generated and validated by our SMS verification provider. The code itself is never stored or logged by RuufLink™.

We do retain a verification record that includes the associated request, the normalized phone number, the verification provider used, the status of the verification, the number of codes sent and attempts made, and the send and verified timestamps. This record is used for fraud prevention, audit and customer support.

Separately from the verification code, we send transactional text messages about your request: a confirmation once your request is complete, and a message identifying each roofing company RuufLink™ connects with your request. These are sent through our messaging provider, and we retain a delivery record for each message that includes the associated request, a masked recipient number, the provider message identifier and the delivery status. You can opt out of these transactional text messages at any time by replying STOP. Reply HELP for help. If you later wish to resume eligible text messages, you may reply START.

Roofing companies — account notifications. A roofing company applying to RuufLink™ may optionally consent, under the Mobile Number field of the contractor application, to receive transactional text messages about its own RuufLink™ account, such as an approval or account status notification. This consent is optional, is never required to apply, and is separate from the new-project text alerts a contractor can turn on in the contractor portal. Account notifications are sent only to the individual contact's mobile number, never to the company's business phone. We retain the consent time, the IP address the consent was submitted from, the disclosure version accepted, and a delivery record containing a masked recipient number, the provider message identifier and the delivery status. Reply STOP to opt out, HELP for help.

5. Consent

Before submitting a request, homeowners must confirm a single required statement. That statement covers: (1) agreement to receive text messages from RuufLink™ about the roofing request, including verification and updates, with message frequency varying and message and data rates possibly applying; and (2) understanding that the request may be shared with local roofing professionals who may contact the homeowner by phone, text or email. The statement also discloses STOP and HELP handling and links to this Privacy Policy and our Terms of Service.

We maintain records of consent and messaging activity as reasonably necessary to document your communication preferences, operate the Service, prevent abuse, and support compliance and customer service. We do not ask for or record consent for unrelated marketing, and we do not send marketing text messages.

6. How information is shared

• Before a purchase: roofing companies can see project type, city, ZIP code, timeline, roof age and roofing material only.
• After a purchase: the purchasing company receives the homeowner's name, address, phone and email.
• To the homeowner: when a roofing company purchases access to a request, RuufLink™ notifies the homeowner and provides that company's public business information — company name, business phone, CSLB license number, website and business email. No private contractor account information, payment information or internal RuufLink™ data is disclosed.
• Exclusive projects are released to a single company. Shared projects are capped at a published maximum — currently three companies.

Roofing companies pay RuufLink™ for access to a homeowner's project details, which are released to the purchasing company after payment is confirmed. We do not make a legal determination whether this arrangement constitutes a "sale" or "sharing" of personal information under California or other privacy laws; that classification should be reviewed by your attorney.

7. Photos

RuufLink™ no longer collects project photos. Photos submitted with earlier requests remain in private storage and are served only through short-lived signed links to authorized internal reviewers.

8. Service providers

We rely on third-party service providers for SMS verification, payment processing, email delivery, web hosting, database services, address lookup, and automated roof measurement and property data. To obtain an automated roof estimate for a submitted project, we may send the property address to a roof-data provider. We do not send the homeowner's name, phone number or email address to that provider.

We use Google Maps Platform (Google Places) to suggest and confirm street addresses. When you type in the address field, the address text you enter is sent to Google so it can return address suggestions and the details of an address you select. We do not send your name, phone number, email address or any other project information to Google. Google's handling of that data is described in the Google Privacy Policy.

We use Cloudflare Turnstile to protect our forms from automated abuse. It runs in the background when you submit a form and may process technical information such as your IP address and browser characteristics to tell genuine visitors from bots. Cloudflare's handling of that data is described in the Cloudflare Privacy Policy.

9. Security and retention

We use technical and organizational measures designed to protect your information. We maintain an append-only audit trail of key marketplace events. Records are retained as required for accounting, dispute resolution, fraud prevention and legal obligations.

10. Your choices

You may contact us to request deactivation of your request, a copy of your information, or correction or deletion. We will respond in accordance with applicable law. Companies who already purchased your project will retain the details they lawfully received, and we cannot retrieve copies from their systems. Specific consumer rights under California or other state privacy laws should be reviewed and implemented with your attorney.

11. Children's privacy

The Service is not intended for children under 16. We do not knowingly collect personal information from anyone under 16. If you believe we have collected such information, please contact us so we can delete it.

12. Changes to this policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top of the page reflects the most recent revision.