Privacy policy

Who we are

OwnerCue helps the owner of a local service business see what works and decide what to do next. This policy is issued by OwnerCue, operated by Evgeny Popov, who is responsible for your data under it. OwnerCue is a pilot. On the demonstration at demo.ownercue.app anyone can request a report on a business; creating an account is limited to invited email addresses. Sample reports there use made-up businesses.

Account data

When you set up your account, by accepting an invitation or by starting a trial from a report, OwnerCue stores:

• your name and email address, and whether the address is verified;
• your password, only as a one-way hash, never in readable form;
• your two-step sign-in factor and its recovery codes, once you set them up;
• your sessions, with the IP address and browser description each one started from;
• an audit record of security and account events, such as sign-ins, password changes, invitations and role changes.

Business data

For each business workspace, OwnerCue stores what you or your operator bring into it:

• uploaded sales and booking export files, and the rows read from them: dates, amounts, payments and refunds;
• a customer reference from your export, so repeat visits can be counted. OwnerCue asks for the export's customer id or code, never a name, email address or phone number. An uploaded file keeps whatever columns your system put in it until it is deleted;
• the sources you connect, with their status and the access they were granted;
• your business details, your weekly plans, the recommendations in them, your decisions, and the evidence each recommendation cites.

Public business reports

Anyone can ask OwnerCue for a report on a business by entering its name, website, town, country and services. OwnerCue then reads public information about that business and nearby competitors: their websites and public search results. Requests are limited per connection and per day to prevent abuse. A report nobody claims is erased after seven days, with what was collected for it. Starting a trial from a report asks for your name, email address and a password, which become account data. On the demonstration, starting a trial is limited to invited email addresses.

Google user data

Status today: an owner or operator can connect Google Analytics and Google Search Console from the Connections page, and OwnerCue then reads their reporting data daily. Google Ads reporting is built but not switched on yet: until it is, no Google Ads account can be connected and the Google Ads card shows labelled sample data. These rules apply to every Google connection.

• OwnerCue asks only for read-only access to Google Analytics and Google Search Console. Google Ads offers one access scope for its API. OwnerCue uses it only to read reporting data and never creates, changes or pauses a campaign.
• OwnerCue uses Google user data only to provide your own reports and recommendations inside your workspace. It is not used for any other purpose.
• Google user data is never sold, and never used or transferred for advertising, including retargeting or interest-based ads.
• Google user data is never used to develop, improve or train general or non-personalised AI or machine-learning models.
• People read Google user data only with your consent, such as the operator you invite to prepare your weekly plan, when needed for security, such as investigating abuse, or when the law requires it.
• Google user data is not transferred to anyone else, except as needed to provide the service, for security, or as the law requires.

OwnerCue's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How we use data

OwnerCue uses your data to run your account, keep it secure, send the email your account needs, build your reports and weekly plans, and keep a record of what was decided. OwnerCue does not sell data, does not show advertising, and does not use advertising cookies.

Who else handles data

These services process data for OwnerCue. Each one receives only what its job needs.

How long data is kept

These retention periods are proposed. They may change once the pilot's country and its rules are confirmed.

• Uploaded export files: 30 days (proposed).
• The normalised records read from them: 13 months (proposed).
• Account records and the audit trail: kept while the account exists, as the record of what happened.

Your controls

• Export. An owner can download the workspace's records from Settings and history: bookings, sales, payments, refunds, connections, actions, activity and evidence.
• Deletion. An owner can request deletion of the workspace from Settings and history. Deletion removes connected-source credentials and tokens, uploaded files and their parsed copies, the normalised records, derived data such as plans and recommendations, and the workspace's memberships and pending invitations.
• Google access. You can disconnect a Google source from the Connections page, which deletes its stored access. You can also revoke OwnerCue's access at any time from your Google Account permissions page.
• Your account. You can change your password and your two-step sign-in in Account settings. Deleting an account yourself is not available in the pilot yet: write to us and we will do it.

Cookies

OwnerCue sets only the cookies that keep you signed in and protect your session, and, when you request a public report, one that lets the same browser claim it within seven days. It uses no advertising, analytics or tracking cookies.

Changes to this policy

When this policy changes, the new version is posted here with its effective date. Significant changes are also sent to account holders by email.

Contact

Questions, requests and complaints: privacy@ownercue.app.