Privacy Policy

1Two kinds of data, and who controls each

The distinction runs through everything below, so it comes first.

Account data is about the brokerage and its staff — names, work email addresses, roles, and how the workspace is used. We decide how this is handled, so we are the controller of it.

Customer data is what a brokerage puts into its workspace about its own contacts, deals, properties and messages. The brokerage decides what to collect and why; we only process it on their instructions. If you are a buyer, seller or tenant asking about your own record, the brokerage you dealt with is the right place to ask, and we will help them answer.

2What we collect

Directly from you, or generated as you use the product:

• Account and profile details: name, work email, phone, job title, organization, and the role assigned to you.
• Authentication data: password hashes (never the password itself), session tokens, and sign-in timestamps.
• Content you enter: contacts, deals, tasks, notes, activity logs, message templates and uploaded media.
• Integration data you connect: advertising and messaging accounts you authorize, and the campaign, lead and message records they return.
• Usage and diagnostic data: pages visited, actions taken, IP address, device and browser, and error reports.
• Commercial details: the bundle, quotes, invoices and payment status. Card numbers are handled by our payment processor and never reach our servers.

3Why we use it

To run the service you asked for, and for nothing incompatible with that:

• Providing the platform: authentication, permissions, storing and displaying your records.
• Sending the notifications you configure — in-app and email — and the messages you send to your own contacts.
• Security and abuse prevention: rate limiting, audit trails, and investigating suspicious activity.
• Support: reproducing a problem you reported.
• Improving the product in aggregate, and invoicing.

4What we do not do

We do not sell personal data. We do not share it with advertisers. We do not use the content of your workspace to train models for other customers, and we do not read it except when you ask us to help with a specific problem or the law requires it.

5Who we share it with

Only the processors the service actually runs on, each bound to handle the data only as we instruct:

• Cloud hosting and managed databases.
• Email and messaging delivery providers, for notifications and for messages you send from the product.
• Advertising and messaging platforms you yourself connect, and only the data that integration requires.
• Payment processing.
• Push notification delivery for the mobile app: Expo, Apple Push Notification service and Firebase Cloud Messaging.
• Error monitoring and analytics.
• A public authority, when we are legally required — and, where we are lawfully able to, we will tell you first.

6Google user data: what we access and why

An administrator can connect their organization's Google Ads account to WzState by signing in with Google. We request a single Google permission: the Google Ads API scope, https://www.googleapis.com/auth/adwords, which lets an app view and manage Google Ads accounts. WzState uses it only to read reporting data and to link the account under our manager account, as described below. It never creates, edits, pauses or removes campaigns, ad groups, ads, budgets or bids.

With that permission, and only for the organization that connected the account, we read:

• The Google Ads accounts your Google login can access, with each account’s name and whether it is a manager account — so an administrator can pick the account to connect.
• The structure of the connected account — campaigns, ad groups and ads, with their names and status — and their daily performance: impressions, clicks, cost and conversions. These power the marketing dashboards in your workspace and let the organization attribute its leads and deals to the campaigns that produced them.
• Submissions to the account’s lead-form ads — the fields a person filled in, such as name, email and phone number, with the campaign and ad they came from — which are added to your workspace as leads.
• A manager-account link. To read reporting reliably, we send a request from WzGate’s Google Ads manager account (customer ID 912-457-9413) to link the connected account under it, and accept that request on your behalf with the access you granted. If your Google user is not allowed to accept it, the request waits for an administrator of that Google Ads account to accept or decline it in Google Ads. Once linked, reporting is read through our manager account’s own access. If the organization has no Google Ads account yet, an administrator can ask us to create a new, empty one under our manager account.

7Google user data: storage, sharing and deletion

Use. Google user data is used only to provide these dashboards, attribution and leads to the organization that connected the account. We do not sell it, use it for advertising, or use it to develop, improve or train artificial-intelligence or machine-learning models. Our staff do not read it except with your permission to resolve a support request, for security purposes, or where the law requires it.

Storage and security. OAuth access and refresh tokens are encrypted with AES-256 before they are stored in our integration service’s database, and are decrypted only to make the calls described above. We keep them only while the connection needs them: they are deleted once the account is linked under our manager account, if the link request is declined, and when you disconnect. Reporting data is stored in your workspace with the rest of its content, and kept while the account stays connected.

Sharing. We do not transfer Google user data to any third party, except the cloud hosting and database providers the service runs on — each bound to handle it only as we instruct — or where the law requires it.

Deletion and revocation. An administrator can disconnect Google Ads in WzState at any time. Disconnecting deletes the stored tokens and connection records, deletes the campaigns, ad groups, ads and daily performance and spend figures imported from Google, and clears the Google connection references from lead-source records; leads already added to your workspace remain workspace content under the retention rules in this policy. You can also revoke WzState’s access at https://myaccount.google.com/permissions and end the manager-account link in Google Ads under Admin › Access and security › Managers — while that link exists, our manager account can still read the account’s reporting data, even after the Google permission is revoked. To have anything else deleted, write to info@wzgate.com.

WzState's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The policy is available at https://developers.google.com/terms/api-services-user-data-policy.

8Meta data: Facebook, Instagram and WhatsApp

An administrator can connect the organization’s Facebook Pages, Meta ad accounts and WhatsApp Business number. We ask Facebook only for the permissions these features need — for advertising, read-only access (ads_read), never permission to manage ads — and use the data only to run these features for that organization.

Tokens are encrypted at rest in the same way as Google tokens. Disconnecting Meta in WzState withdraws our permissions on Facebook, deletes the stored tokens, and deletes the imported campaigns and performance data. You can also remove WzState under Facebook Settings › Business integrations. The Data Deletion Instructions page explains how to have data that reached a workspace through Meta products deleted.

What we read, and why:

• The Pages you choose and their lead forms, and the submissions from Facebook and Instagram lead ads, which are added to your workspace as leads.
• Ad account, campaign, ad set and ad names and status, and their performance and spend, for the same dashboards and attribution as Google Ads.
• WhatsApp messages exchanged with your contacts, so they appear in your inbox and you can reply from it.

9The WzState mobile app

The WzState app for iPhone and Android is used by staff of organizations that subscribe to WzState. Accounts are created by the organization; the app has no public sign-up.

• What the app stores on your phone. Your sign-in session, the workspace you chose, your language, and whether you were asked about notifications. They are kept in the phone’s secure storage (Keychain on iPhone, Keystore on Android) and are removed when you sign out or delete the app.
• What the app sends to us. Your sign-in details, what you do in the app (notes, call outcomes, task updates, assignments and messages you send to your organization’s customers), the app version and platform, your phone’s model or name, and its language. We use the device details to show your active sessions, to keep the app compatible with the server, and to secure your account.
• Notifications. If you allow notifications, the app registers a push token for your phone. We use it only to tell you about leads assigned to you, tasks due, and messages from customers. Notifications are delivered through Expo, Apple Push Notification service and Firebase Cloud Messaging, and may include a customer’s name and the first words of a message. You can turn notifications off in the phone’s settings at any time; signing out removes the token.
• Calls and WhatsApp. When you tap Call, the app opens your phone’s dialer; it does not read your call history, record calls, or access your phone’s contacts. WhatsApp conversations are sent and received through your organization’s WhatsApp Business number.
• What the app does not do. It does not use your location, camera, microphone, photos or address book. It contains no advertising, no analytics or tracking tools, and does not share data with advertisers.
• Customer data in the app. The leads, units and conversations you see belong to your organization, which is the controller of them; we process them on its behalf, as described above.
• Deleting your account. In the app, open Me › Delete account. Your organization’s administrators and WzGate are notified, and the account is deleted within 30 days. Records of business actions you performed on behalf of the organization remain with the organization.

10Where it is stored, and for how long

Data is stored on infrastructure that may sit outside your country, protected by contractual safeguards for any transfer.

We keep workspace content for as long as the account is active. After an account closes, content is deleted or anonymized within 90 days, except where we must keep records longer to meet a legal or accounting obligation. Some records — audit logs and invoices among them — are retained for their own statutory period.

11Your rights

Subject to local law, you may ask us to give you a copy of your data, correct it, delete it, restrict or object to a use, or export it in a portable format. Where we rely on consent — marketing email is the usual case — you can withdraw it at any time without affecting what happened before.

Write to info@wzgate.com and we will respond within the period your law sets, and within 30 days where none is set. If you are asking about a record a brokerage holds about you, we will route you to that brokerage, who is the controller of it.

If you use the mobile app, you can also start account deletion from Me › Delete account.

12Security

Access is scoped by role and by organization, credentials for connected integrations are encrypted at rest, traffic is encrypted in transit, and administrative actions are recorded in an audit trail. No system is perfectly secure; if a breach affects your data we will notify you and the relevant regulator as the law requires.

13Cookies

The application uses cookies and similar storage that are strictly necessary to keep you signed in and to remember interface preferences such as language and theme. This website additionally uses limited analytics to understand which pages are read. It sets no advertising cookies.

14Children and the service

The service is a business tool and is not directed at children. We do not knowingly collect data from anyone under 18. If you believe a child has provided us data, contact us and we will delete it.

15Changes to this policy

When we change this policy materially, we will update the effective date above and notify account administrators in the product before the change takes effect.