Privacy Policy
Effective November 10, 2026
Victr OPS is a client management tool for marketing teams. It is operated by Victr OPS ("we"). This policy explains what the CRM and this website collect and how it's used.
Information we collect
- Team accounts: names, work emails, roles and sign-in details of the people who use the CRM.
- Client records: the client details, contacts, tasks, notes and results that users add or import.
- Team performance data: the work a team member logs or is credited with in the CRM, the clients they held and when, any blockers they log, and the performance scores, rating labels and monthly history worked out from these.
- Google sign-in: when a team member links an account by signing in with Google, we receive that Google login's email address and a token that lets the CRM keep reading the linked accounts.
- Google Ads data: we list the Google Ads accounts a login can reach, with their names, IDs, currencies and manager accounts. For ad accounts linked in the CRM, we also read the account's time zone, its change history, and its conversion action settings.
How we use Google data
We use the login's email to show which saved login is which. We use the token only to read the Google Ads data described in this policy.
We use Google Ads data only for these features in the CRM:
- letting a team member pick the right Google Ads account for a client, and showing its name, currency and manager account on that client
- showing a record of account changes, so the team managing an account can see what changed and when. This includes changes to budgets, bids, statuses, campaigns, ad groups, ads, keywords and conversion tracking. This feature is in testing and isn't turned on for customers yet. We only read change history once it's turned on
The CRM only reads this data. It doesn't change anything in a Google Ads account.
The list of accounts a login can reach is shown while picking an account. We only save the account that's linked.
Google reports the email of the person who made a change. We compare it with our team's emails so we can show the team member's name. If there's no match, we label the change "Outside your team" and don't store that email.
Victr OPS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We don't transfer or sell Google user data to third parties such as advertising platforms or data brokers, and we don't use it for advertising or to decide credit or lending.
Demo requests
When you request a demo on this website, we collect the name, work email, agency details and message you enter. We use them only to reply and arrange the demo. Netlify receives and stores the form for us. To have a request deleted, contact us at the address below.
Who can see it
Information is available to signed-in team members according to their role and the clients they work on. A person's performance scores can be seen by that person and by admins. Saved Google tokens can't be seen by anyone using the CRM. We don't sell any of this information, use it for advertising, or share it with anyone else, except as described in this policy or where the law requires it.
When an agency uses Victr OPS, Victr OPS support staff can open that agency's workspace to help it, for example to answer a support ticket or fix a problem. They see the same information as the agency's admins. Anything they change is recorded in the client's change history and marked as made by support. A support ticket keeps the message and the sender's name and email, and only the sender and Victr OPS support staff and admins can see it.
A team member with manager access can share a client's performance report through a private link, and anyone with that link can open it until it expires or is stopped. Links last up to 90 days. Reports can also be downloaded as a PDF. Scheduled report emails aren't turned on yet. Once they are, reports can also be sent on a schedule to the addresses a team member chooses.
Service providers
We use Supabase to store data and run the server functions, and Netlify to host the site. Google supplies Google sign-in and the Google Ads data. If scheduled report emails are turned on, Resend delivers them. The CRM page also loads code from jsDelivr and cdnjs, and exchange rates from Frankfurter, which can see a visitor's IP address when they do. These providers only receive what they need to provide their service.
Security
Access requires a sign-in and is limited by role. Google tokens are encrypted, kept on the server and never sent to the browser. Data is sent over encrypted connections.
Keeping and deleting data
A saved Google login is kept until someone removes it. Removing it in the CRM deletes the saved token and asks Google to cancel the CRM's access. A linked account's details are kept with the client until they're replaced or the client is removed.
Change records are kept as a history for as long as the client remains in the CRM. To ask for data to be deleted, or to ask what we hold about you, contact us at the address below. You can also remove the CRM's access to your Google account at any time at myaccount.google.com/permissions.
Changes to this policy
If we change this policy, we'll update this page and its effective date.
Contact
Victr OPS, admin@victrops.com