Cookie Policy

1. Scope of this Policy

This Policy explains how tracking and storage technologies may be used when you:

• visit the Rloop website;
• create or access an account;
• submit a quote or service request;
• use the Contractor portal;
• use a future Customer portal;
• schedule or manage Services;
• submit documents or forms;
• make or receive payments;
• interact with Rloop communications.

This Policy does not independently govern cookies placed on websites that Rloop does not own or control.

2. What cookies are

Cookies are small text files that a website stores on a browser or device.

Cookies may allow a website to:

• recognize a browser;
• maintain a login session;
• remember settings;
• protect forms from unauthorized requests;
• measure website usage;
• diagnose technical issues;
• support other website functions.

Cookies may be set directly by Rloop or by a third-party service used by Rloop.

3. Similar technologies

In addition to cookies, Rloop and its service providers may use:

• local browser storage;
• session storage;
• software development kits;
• tracking pixels;
• web beacons;
• embedded scripts;
• device or browser identifiers;
• server logs;
• similar technologies.

References to “cookies” in this Policy generally include these related technologies where appropriate.

4. Why Rloop uses cookies

Rloop may use cookies and similar technologies to:

• operate the website and platform;
• authenticate users;
• maintain secure sessions;
• prevent cross-site request forgery;
• prevent fraud and abuse;
• remember preferences;
• process forms;
• improve performance;
• diagnose errors;
• measure website engagement;
• process payments;
• comply with legal obligations.

5. Strictly necessary cookies

Strictly necessary cookies support essential website and platform functions.

These cookies may be used to:

• keep users signed in;
• protect accounts;
• validate form submissions;
• maintain shopping, booking, or workflow state;
• balance network traffic;
• prevent malicious requests;
• remember privacy choices;
• maintain platform reliability.

Because these technologies are required to provide requested functionality, they may be used without optional-cookie consent where permitted by law.

Blocking strictly necessary cookies may prevent login, registration, scheduling, document upload, payment, or other platform functions.

6. Django session and security cookies

Rloop is built using the Django web framework. Django may use cookies that support authentication and security.

Cookie names and technical configurations may change as Rloop’s security and platform architecture develop.

7. Preference and functionality cookies

Preference cookies may remember choices that improve the user experience.

These choices may include:

• cookie preferences;
• selected service areas;
• display preferences;
• form progress;
• portal navigation state;
• accessibility preferences.

Some preference cookies may be optional. Disabling them may cause settings to reset between visits.

8. Analytics cookies

Rloop may use analytics technologies to understand how users interact with the website and platform.

Analytics information may help measure:

• page visits;
• traffic sources;
• feature usage;
• approximate session duration;
• navigation patterns;
• form completion;
• device and browser types;
• website errors.

Analytics tools may collect identifiers, IP addresses, browser information, device information, referral information, and activity data.

Rloop may require consent before activating optional analytics cookies where applicable.

9. Performance and reliability technologies

Performance technologies may help Rloop:

• identify failed requests;
• diagnose application errors;
• monitor response times;
• identify unusual traffic;
• improve page-loading performance;
• maintain platform availability.

Performance data may be aggregated or deidentified when reasonably possible.

10. Payment-related technologies

Rloop may integrate with third-party payment processors to accept Customer payments and issue Contractor payouts.

Payment providers may use cookies or similar technologies to:

• process transactions;
• authenticate payment methods;
• detect fraud;
• prevent unauthorized transactions;
• remember checkout state;
• perform identity verification;
• comply with financial laws.

Payment-provider technologies may be governed by the provider’s own privacy and cookie policies.

11. Cloudflare security and delivery technologies

Rloop may use Cloudflare for domain services, content delivery, security, traffic management, and protection against malicious activity.

Cloudflare may process technical information or use cookies to:

• distinguish legitimate users from automated traffic;
• mitigate attacks;
• enforce security rules;
• balance traffic;
• improve content delivery.

Cloudflare cookies used for security or network delivery may be treated as strictly necessary.

12. Email and communication technologies

Emails sent by Rloop or its communication providers may use tracking pixels or tagged links to determine whether a communication was:

• delivered;
• opened;
• clicked;
• rejected or marked as spam.

This information may help Rloop deliver transactional messages, improve communications, and prevent abuse.

Users may opt out of promotional communications where offered, but operational and transactional communications may still be sent.

13. Advertising and marketing cookies

Rloop does not need to use advertising cookies to provide basic website or portal functionality.

Rloop may introduce advertising or marketing technologies in the future to:

• measure advertising effectiveness;
• understand campaign performance;
• limit repeated advertisements;
• build or measure audiences;
• display more relevant promotions.

Certain advertising technologies may involve the “sharing” of personal information for cross-context behavioral advertising under California law.

Where required, Rloop will provide appropriate notice and a method to opt out before or when these technologies are used.

14. Third-party technologies

Depending on the features enabled, third-party technologies may be provided by:

• cloud-hosting providers;
• content-delivery and security providers;
• payment processors;
• analytics providers;
• map and location providers;
• customer-support platforms;
• email providers;
• identity-verification providers;
• advertising providers.

A third party may process information under its own terms and privacy policy when acting independently from Rloop.

Rloop does not control every cookie placed by a third-party website reached through an external link.

15. Cookie categories used by Rloop

16. Cookie duration and retention

Cookies may be either session cookies or persistent cookies.

Session cookies

Session cookies generally expire when a browser session ends, although browser settings may affect when session data is removed.

Persistent cookies

Persistent cookies remain until their configured expiration date, until replaced, or until deleted through browser or device controls.

Rloop seeks to retain cookie-derived information only for as long as reasonably necessary for the purposes described in this Policy, legal compliance, fraud prevention, security, dispute resolution, or business records.

17. Your cookie controls

You may be able to control cookies through:

• an Rloop cookie-preference tool;
• browser settings;
• device settings;
• privacy extensions;
• provider-specific opt-out tools;
• legally recognized opt-out preference signals.

Most browsers allow users to:

• view stored cookies;
• delete cookies;
• block all cookies;
• block third-party cookies;
• receive warnings before cookies are stored.

Blocking all cookies may prevent Rloop from remembering your session or completing secure account actions.

Deleting cookies may also delete previously saved consent or preference settings.

18. Global Privacy Control

Global Privacy Control, commonly called GPC, is a browser-based signal that may communicate a consumer’s request to opt out of the sale or sharing of personal information.

Where the California Consumer Privacy Act applies and requires recognition of a valid opt-out preference signal, Rloop will process that signal as required by applicable law.

A valid signal may apply to the browser or device from which the signal is sent. Additional verification or account-level handling may be appropriate where permitted.

A standard cookie banner does not necessarily replace a legally required method for submitting a request to opt out of sale or sharing.

19. California privacy rights

Depending on Rloop’s activities and whether the California Consumer Privacy Act applies, California residents may have rights concerning personal information collected through cookies and similar technologies.

These rights may include the right to:

• know what personal information is collected;
• request access to personal information;
• request deletion;
• request correction;
• opt out of sale or sharing;
• limit certain uses of sensitive personal information;
• receive equal service without unlawful discrimination.

Cookies used for cross-context behavioral advertising may constitute “sharing” under California law even when money is not exchanged.

Rloop’s separate California Privacy Notice will describe applicable rights and request methods in greater detail.

Rloop does not represent that every California privacy-law provision necessarily applies to the Company at every stage of its development.

20. Updates to this Cookie Policy

Rloop may update this Policy when:

• new platform features are introduced;
• service providers change;
• analytics or payment systems are added;
• advertising technologies are introduced;
• cookie practices change;
• legal requirements change.

The revised Policy will display an updated effective date or last-updated date.

Rloop may provide additional notice or request renewed consent when required by law or when a material change affects optional-cookie choices.