LSWEF Local Service Website Engineering Framework

Privacy Policy

Last updated 27 September 2026  ·  Operated by Redlane Marketing Services, Regina, Saskatchewan, Canada

1. Scope of this policy

This policy explains how information is handled in connection with the website at lswef.com and with LSWEF Ads Conversion Sync, a technology component of the Local Service Website Engineering Framework (LSWEF). LSWEF is operated by Redlane Marketing Services of Regina, Saskatchewan, Canada, referred to in this policy as "we", "us" or "our".

This policy covers this website and the Ads Conversion Sync integration. It does not govern the separate websites of businesses that engage our services; those sites are operated under their own arrangements and may have their own privacy policies.

2. Current operational status

We want to be accurate about what is actually happening today rather than describe a system that is not yet running.

LSWEF Ads Conversion Sync is pre-launch. At the time of the last update to this policy, it is not connected to any live Google Ads account. No Google Ads account data, conversion data or lead data is currently being received, transmitted or stored by us through this integration.

The sections below describe how the integration is designed to handle information once it is in use and a user has authorized it. Where a practice has not yet been established, this policy says so rather than implying otherwise. We will update this policy, including its "last updated" date, before or at the point that materially changes.

3. Information we collect

We may handle the following categories of information.

Information you send us directly

If you email us, we receive your email address, your message and anything you choose to include in it. We use this to respond to you and to keep a record of the correspondence.

Technical information from visiting this website

This website is a set of static pages. It does not use cookies, does not include analytics or advertising scripts, and does not attempt to identify or track visitors across sites. Our hosting provider processes standard technical request information as described in Website and server logs.

Information from an authorized Google Ads connection

If an authorized user connects a Google Ads account to Ads Conversion Sync, the integration is designed to access information from that account only as needed to provide the conversion and attribution functionality the user has authorized. This is covered in section 6.

Conversion and lead information

Where a website engineered under LSWEF produces an enquiry, the integration is designed to handle information about that outcome so it can be attributed to the advertising that produced it. This is covered in section 5.

4. Website and server logs

This website is hosted on Cloudflare Pages. As with essentially any web host, serving a page involves processing standard technical request information, which typically includes the requesting IP address, the time of the request, the page or file requested, the HTTP response status, and browser-supplied details such as the user-agent string.

This processing is performed by our hosting and network provider as part of delivering and protecting the site. We do not use this information to build visitor profiles, and we do not combine it with advertising data. The retention and handling of that infrastructure-level log data is governed by the provider's own practices, which we do not control. See Third-party services.

5. Advertising and conversion data

The purpose of Ads Conversion Sync is advertising measurement and attribution: establishing which advertising activity produced a genuine enquiry, so that advertising decisions can be based on outcomes.

To do that, the integration is designed to handle:

  • Conversion events — the fact that an enquiry or qualifying action occurred, and when it occurred.
  • Click identifiers — such as the Google Click Identifier (GCLID), which links a conversion back to the advertising click that led to it. See section 8.
  • Call and enquiry attribution information — where call tracking is used, information about the call event and the source that produced it, so that a telephone enquiry can be attributed in the same way as a form submission.
  • Limited lead information — where a conversion type requires it, information associated with the enquiry itself.

Lead and enquiry information can include personal information such as a name, telephone number or email address supplied by the person making the enquiry. Where that is the case, that information belongs to the business receiving the enquiry, and we handle it only to provide the authorized integration on that business's behalf.

6. Google account access and OAuth

Connecting a Google Ads account to Ads Conversion Sync uses Google's own OAuth authorization process. We never ask for, receive or store your Google account password. Authorization happens on Google's screens, under your control.

During that process:

  • Google shows you exactly what access is being requested before you decide.
  • You choose whether to grant it. The connection is initiated by you, not by us.
  • We request access at the narrowest scope that allows the integration to perform the function you are authorizing.
  • If you grant access, Google issues us an authorization credential — a token — that allows the integration to act within the scope you approved. That token is the mechanism of access; it is not your password, and it can be revoked by you at any time.

Access obtained this way is used only to provide the integration functionality you authorized. It is not used to explore unrelated parts of your account, and it is not used for any separate purpose of our own.

7. Use of Google user data

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Specifically, Google user data obtained through OAuth:

  • is used only to provide or improve the integration functionality the user has authorized;
  • is not sold, in any circumstance;
  • is not transferred to others except as needed to provide the authorized functionality, to comply with applicable law, or as part of a merger, acquisition or sale of assets with prior notice to affected users;
  • is not used for advertising profiling, retargeting, credit assessment, lending, or any purpose unrelated to the authorized integration;
  • is not read by humans, except where the user has given explicit consent for specific data, where it is necessary for security purposes such as investigating abuse, where it is necessary to comply with applicable law, or where the data has been aggregated and anonymized for internal operations.

8. Click identifiers such as GCLID

When someone clicks a Google Ads advertisement, Google may append a click identifier — commonly the gclid parameter — to the destination URL. That identifier represents the advertising click, not the identity of the person.

Where conversion measurement is in use, this identifier may be recorded alongside a resulting enquiry so that the conversion can be reported back and matched to the advertising click that produced it. This is the standard mechanism by which advertising attribution works, and it is what makes it possible to tell which advertising is actually producing enquiries rather than merely producing clicks.

9. Why we process this information

We process the information described above in order to:

  • provide the conversion measurement and advertising attribution functionality a user has authorized;
  • report eligible conversions to the connected Google Ads account for attribution;
  • allow advertising performance to be assessed against real enquiries rather than assumptions;
  • operate, secure, troubleshoot and maintain the framework's technical components;
  • respond to messages you send us;
  • comply with legal obligations that apply to us.

We do not sell personal information. We do not use conversion or lead information to build advertising profiles of individuals, and we do not use it for any purpose unrelated to the measurement function described here.

10. Storage and security

As of the last update to this policy, we do not maintain our own store of conversion or lead data. Ads Conversion Sync is designed to transmit eligible conversion information to the connected Google Ads account for attribution, rather than to accumulate a separate database of that information under our control.

Where information does need to be held transiently in order to complete a transmission, it is held only for as long as that operation requires. Authorization credentials issued by Google are held only so that the integration can perform the function you authorized, and cease to be usable once you revoke access.

We apply access controls and encrypted credential storage appropriate to the integration, and information in transit to Google's APIs and to this website is carried over encrypted connections (HTTPS/TLS).

Stated plainly: we make no claim to hold any security certification, formal audit, or compliance attestation, because we hold none. We describe only the measures actually in place. No method of transmission or storage over the internet can be guaranteed absolutely secure, and we do not claim otherwise.

If this changes — in particular if we begin retaining conversion or lead data in our own systems — we will update this policy before or at the point that happens, and we will state where that data is held.

11. Third-party services

We rely on the following third parties. Each processes information under its own privacy terms, which we do not control.

  • Google / Google Ads — the advertising platform to which eligible conversion information is transmitted, and the provider of the OAuth authorization process. See the Google Privacy Policy.
  • Cloudflare — hosting and network delivery for this website (lswef.com), including the technical request processing described in section 4.
  • RingRobin — used in connection with call and enquiry tracking, where call attribution forms part of the measurement described in section 5.
  • Xagio Hosting — hosting used for websites operated under the LSWEF framework. Note that this website itself is hosted on Cloudflare Pages; Xagio is listed because it forms part of the wider framework environment.

We do not sell or rent information to third parties, and we do not pass information to anyone for their own independent marketing purposes.

12. Retention

We have not established a fixed retention period, and we are not going to state one that does not exist.

What we can state accurately:

  • We do not currently maintain our own store of conversion or lead data, so there is presently no such data of ours to retain. Conversion information transmitted to a connected Google Ads account is retained by Google under Google's own retention practices.
  • Google authorization credentials cease to be usable when you revoke access, and we do not keep them in a usable form after that.
  • Email correspondence is kept for as long as needed to deal with the matter and to keep a reasonable business record.
  • Infrastructure-level server logs are retained by our hosting provider under its own retention practices.

If we begin retaining conversion or lead data in our own systems, we will define a retention period and publish it here.

13. Disclosure

We may disclose information only in these circumstances:

  • To provide the authorized functionality — for example, transmitting conversion information to the Google Ads account the user connected.
  • To service providers listed in section 11, to the extent needed for them to provide their service to us.
  • To the business the information belongs to — where we handle enquiry information on behalf of a business, that business receives it.
  • Where required by law — to comply with a legal obligation, court order or lawful request from a public authority, or to establish, exercise or defend legal claims.
  • In a business transfer — in connection with a merger, acquisition or sale of assets, with prior notice to affected users where Google user data is involved.

We do not sell personal information, and we do not sell Google user data.

14. Your choices and rights

Depending on where you live, you may have rights in relation to your personal information, including the right to ask what we hold, to ask for a correction, to ask for deletion, to withdraw a consent you gave, and to complain to a regulator.

In Canada, personal information handling in the course of commercial activity is subject to the Personal Information Protection and Electronic Documents Act (PIPEDA), and complaints may be made to the Office of the Privacy Commissioner of Canada.

To exercise any of these, email privacy@lswef.com. We will respond within the timeframe required by applicable law. We may need to verify your identity first, and where the information belongs to a business we act for, we may need to direct your request to that business.

One practical note: because we do not currently maintain our own store of conversion or lead data, a request about conversion data already transmitted to a Google Ads account is usually best directed to the holder of that account, or to Google.

15. Revoking Google authorization

You can disconnect Ads Conversion Sync at any time, without contacting us. Revocation is done in your own Google Account:

  1. Go to your Google Account connections page (Security → Your connections to third-party apps & services).
  2. Select LSWEF Ads Conversion Sync.
  3. Choose the option to remove or revoke its access.

Once revoked, the authorization credential issued to us stops working immediately, and the integration can no longer access your Google Ads account. Conversion information already transmitted to your Google Ads account remains in that account, under your control and Google's retention practices.

You may also email privacy@lswef.com and ask us to disconnect it, though revoking directly in your Google Account is faster and takes effect immediately.

16. Children

LSWEF is a business-to-business framework and is not directed at children. We do not knowingly collect personal information from children. If you believe a child has provided information to us, contact us and we will delete it.

17. Changes to this policy

We may update this policy as the framework and its components develop. The "last updated" date at the top of the page reflects the current version. Where a change materially affects how Google user data or personal information is handled, we will update this page before or at the point that change takes effect. We recommend reviewing this page if you are considering authorizing the integration.

18. Contact

For any privacy question, request, or concern about this policy or the Ads Conversion Sync integration:

Operator
Redlane Marketing Services
Location
Regina, Saskatchewan, Canada

See also our Terms of Service.