Qwrki

Privacy policy

Updated 17 October 2026

About this policy

This policy covers the Qwrki app at app.qwrki.com. The Qwrki website at qwrki.com has its own policy.

The app is operated by Qwrki Pty Ltd, 74 Thorburn St, Nimbin NSW 2480, Australia. Questions about this policy go to [email protected].

Information the app holds

An organisation that uses Qwrki owns its workspace. Its members enter and manage records such as customers, cases, projects, invoices and files. Qwrki stores those records to run the app for that organisation and shows them to that organisation's members, according to the roles its admins assign, and to the people the organisation shares them with, such as its portal contacts and visitors to its public forms and surveys.

To sign you in, Qwrki keeps your email address and your password, stored only as a one-way hash, and sets a sign-in cookie in your browser.

When a member opens a page in the app, Qwrki records the page's path, the referring page, the device type, the country and the campaign value, with a daily pseudonymous visitor value, so the organisation's admins can see how the app is used.

Google user data

When you connect a Google account, Qwrki asks Google for the permissions below and nothing else.

Google permissions Qwrki can request
PermissionConnected byWhat Qwrki readsWhy
openidAn admin, for the organisationThe Google account's identifier.So a later reconnection can only use the same Google account.
analytics.readonlyAn admin, for the organisationReport totals for the Google Analytics property the admin picks: sessions, users, conversions and sessions by channel.To show the organisation its own website figures on its dashboards.
webmasters.readonlyAn admin, for the organisationSearch Console totals for the site the admin picks: clicks, impressions and click-through rate, also split by search query, page, device and country.To show the organisation how its site appears in Google Search.
adwordsAn admin, for the organisationPerformance reports for the Google Ads account the admin picks: cost, clicks, impressions and conversions. Google offers no read-only Ads permission; Qwrki only reads reports and never changes a campaign.To show the organisation its advertising figures beside its other figures.
openid, emailA member, for themselvesThe identifier and email address of the member's own Google account.To show which account is connected and to refuse a different account on reconnection.
calendar.readonlyA member, for themselvesRequested only when Qwrki has switched calendar sync on. The member's own Google Calendar: the events on the member's primary calendar for the next 24 hours, shown beside the member's meetings. Events are read each time and never stored.So the member can see their own day when scheduling a meeting.
calendar.eventsA member, for themselvesRequested only when Qwrki has switched calendar write on. The member's own Google Calendar: one meeting the member chooses, added to the member's own primary calendar. Adding the same meeting twice adds nothing new. Qwrki stores no copy of the event; the audit trail records the meeting id.So the member can add a scheduled meeting to their own Google Calendar.

Qwrki'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 use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

Google's policy: https://developers.google.com/terms/api-services-user-data-policy

Google user data at a glance

What Qwrki accesses

The table above lists every Google permission Qwrki can request.

Every permission except Google Ads is read-only (Google offers no read-only Ads permission), and the person connecting the account chooses the account and can see in the app what the connection is used for.

How it is used

Qwrki uses Google user data only to provide the features described in the table above, which the person connecting the account can see in the app.

Figures from a connected Google account are shown to members of that organisation.

Who it is shared with

Figures from an organisation's Google Analytics, Search Console and Google Ads connection are shown to members of that organisation, according to the roles its admins assign.

If an admin gives an AI Employee access to a connected account, the stored figures from that account are included in requests to Qwrki's AI model providers to draft that Employee's work, with the provider's logging of prompts turned off.

Qwrki does not sell Google user data, does not use it for advertising, and does not transfer it to data brokers or information resellers, and people at Qwrki do not read Google user data, except with your explicit permission for specific data, when needed for security purposes such as investigating abuse, to comply with applicable law, or when it has been aggregated and anonymised for internal operations.

How it is protected

Google access tokens are stored encrypted with AES-256-GCM.

Every page from the app carries a header telling browsers to keep using HTTPS.

Stored report figures belong to one organisation: the figures table enforces row-level security, and every request that reads those figures runs with that organisation set as the tenant.

How long it is kept and how to remove access

Report figures from Google Analytics, Search Console and Google Ads are deleted automatically 400 days after the period they cover, while the organisation is active.

After an organisation's connection is disconnected, Qwrki's background job deletes the report figures Qwrki stored from that connection and the figure files exported from it, normally within two hours.

Removing Qwrki in your Google Account, under Security, Third-party apps and services, ends every Qwrki connection that Google account holds, in every organisation.

How Qwrki uses Google user data

Qwrki does not access Gmail or Google Drive. If this changes, this policy will say so first.

Qwrki uses Google user data only to provide the features described in the table above, which the person connecting the account can see in the app.

Who can see it

Figures from an organisation's Google Analytics, Search Console and Google Ads connection are shown to members of that organisation. Only its admins and owners can connect, update or disconnect that connection.

AI features

An organisation's admins can give one of its AI Employees access to a connected Google Analytics, Search Console or Google Ads account. The figures Qwrki stored from that account are then included in requests to Qwrki's AI model providers to draft that Employee's work. Qwrki sends those requests with the provider's logging of prompts turned off.

Qwrki does not use Google user data to train or improve AI or machine learning models.

Your AI Employees learn only inside your organisation. What they learn is stored with your organisation's data, can be seen and switched off by your admins, and is never used to train AI models or to improve another customer's AI Employees.

Storage, retention and deletion

Text already copied into a case stays in Qwrki as part of that case.

Report figures from Google Analytics, Search Console and Google Ads are deleted automatically 400 days after the period they cover, while the organisation is active. Figures of a suspended organisation are kept until it is active again. Copies in exports, saved reports, report emails, drafts and notifications are not automatically deleted.

Google access tokens are stored encrypted with AES-256-GCM.

Every page from the app carries a header telling browsers to keep using HTTPS. Stored report figures belong to one organisation: the figures table enforces row-level security, and every request that reads those figures runs with that organisation set as the tenant. Qwrki only shows those figures to members of the organisation they belong to, in the app and in emails they receive.

When a Google connection is disconnected, or when a member's own Google connection is disconnected because that member is removed from an organisation, Qwrki overwrites its stored token so it can no longer be used and discards its cached access token. After an organisation's Google Analytics, Search Console or Google Ads connection is disconnected, Qwrki's background job deletes the report figures Qwrki stored from that connection and the figure files exported from it, normally within two hours. Copies already in the organisation's own work keep what they contain: drafts an AI Employee wrote, saved reports already run, notifications in Qwrki, alert messages already posted to a chat tool, and emails already sent or waiting to send.

When you disconnect Google in Qwrki, Qwrki can no longer use the access. Google keeps listing Qwrki until you remove it in your Google Account, under Security, Third-party apps and services. Removing it there ends every Qwrki connection that Google account holds, in every organisation.

What Qwrki never does with Google user data

Qwrki does not sell Google user data, does not use it for advertising, and does not transfer it to data brokers or information resellers.

People at Qwrki do not read Google user data, except with your explicit permission for specific data, when needed for security purposes such as investigating abuse, to comply with applicable law, or when it has been aggregated and anonymised for internal operations.

Your Google Account permissions page: https://myaccount.google.com/permissions

Meta (Facebook) data

An organisation's admin can connect a Meta account to Qwrki. Qwrki asks Meta only for permission to read advertising performance. Before Qwrki reads any other kind of data from Meta, this policy will name it first.

For a connected Meta account Qwrki keeps the access token Meta issues, stored encrypted with AES-256-GCM, the account number Meta gives Qwrki for that person, and a label for the connection.

To ask Qwrki to delete this data, remove Qwrki in Facebook under Settings & Privacy, Settings, Apps and Websites, and send the deletion request there. You can also write to [email protected], or ask an admin of the organisation to disconnect Meta in Qwrki.

When Meta sends Qwrki your request, Qwrki overwrites the stored token so it can no longer be used, discards any cached token, and removes the Meta account number and label from every Qwrki organisation that holds them. Qwrki keeps a record that a Meta connection existed, who in the organisation connected it and when, and that it was removed at your request. You receive a confirmation code and a page where you can check your request.

Records an organisation keeps in Qwrki belong to that organisation. If they mention you, ask that organisation.

Shopify data

An organisation’s admin connects its Shopify store to Qwrki. Qwrki reads each customer’s email, first name, last name, phone, last updated date, customer number and email marketing consent. Qwrki never keeps where a customer lives. For each order Qwrki keeps the order number, dates, payment and fulfilment status, totals and currency, line item names and quantities, the customer’s email and customer number, and their email marketing consent.

Qwrki keeps this data to show the organisation its own customers and orders, to link them to its records, and to let its people and AI Employees act on them with approval. Nothing is sold, shared for anyone else’s benefit, or used to train models.

When the store uninstalls Qwrki, Qwrki stops reading it and removes the store’s data when Shopify sends its shop erasure. A Shopify customer erasure blanks that customer. Disconnecting stops new reads. A Shopify customer data request reaches the organisation’s admin, who answers within 30 days.

The organisation is the controller of its Shopify data. Questions about a record go to that organisation. Qwrki Pty Ltd’s contact for Shopify data is [email protected].

If you received a confirmation code, check your request on the data deletion page.

Services Qwrki uses

Qwrki uses service providers for AI features, bot protection, telephone calls, sending email, file storage and billing.

AI features send the records an AI Employee is working with, and the words it is asked to write, to AI model providers through one AI gateway. Qwrki turns off the gateway's storing of those requests and answers, and sends only reference numbers with them, never a person's name, as the request's label. Qwrki does not use your records to train AI models, and only adds a model provider whose business terms say it does not train its models on customers' requests. The providers in use are named on our subprocessors page.

Your organisation's records, and the app that serves them, are held on servers in the United States. Files your organisation uploads are held with our file storage provider, and the nightly backup copies are held with the same provider once the backup service is deployed. AI requests are processed on our AI providers' networks, which may be outside the country your organisation is in. Telephone calls pass through our telephone provider and through our call server in the United States; call transcripts are stored with your other records. Voicemail recordings are deleted 60 days after the call; the transcript stays with the call record. Qwrki does not offer a choice of country for storage.

Complaints

To complain about how Qwrki handles personal data, write to [email protected]. We acknowledge every complaint within 30 days. In Australia you may also contact the Office of the Australian Information Commissioner.

Changes to this policy

When this policy changes, this page shows the new text and the date it was updated.

The outside services that may receive company data are listed on our subprocessors page.