What This
Policy Covers
This Privacy Policy applies to every product, bot, integration, or workflow published under the Vector Workflows name — current and future — collectively referred to here as our "Services." Rather than drafting a fresh policy per tool, one consistent standard governs how we handle data everywhere.
One Standard, Every Product
Whatever Service you connect to — today or one we launch later — the same collection principles, guarantees, and deletion rights apply. Where a Service touches something genuinely specific, we'll note it plainly inside that Service itself.
Only What's Functionally Required
Every Service is built around a simple rule: request only the access, credentials, or identifiers required to do the specific job it exists to do — never more.
What Information
We Process
Across our Services, the categories of data we handle generally fall into a few functional groups — always the minimum required to operate.
Authorization Tokens
Where a Service connects to a platform you already use — a calendar, a messaging app, a productivity tool — we store the secure OAuth or API tokens needed to perform the specific actions that Service is designed for, and nothing beyond that scope. For the exact Google API scopes and data fields each of our products accesses, see that product's disclosure below.
Account & Platform IDs
A platform-issued identifier (such as a messaging user ID) and the timestamps of your interactions with a Service, so it knows who to respond to and when.
Configuration & Settings
Any preferences or settings you explicitly configure within a Service, so it behaves the way you've set it up to.
Contact Details You Provide
If you reach out for support, the email address or contact information you send us, used only to respond to that request.
We never request access to contacts, emails, location, or any connected platform's data beyond what a given Service explicitly needs to function.
How Your Data
Is Used
Every piece of data processed has a single, functional purpose tied directly to the Service you're using.
Operating the Service You've Connected
Reading and writing only the specific data a Service needs to carry out the function you've enabled it for — nothing beyond that stated purpose.
Session Management
Storing encrypted access tokens so a Service can keep working on your behalf without forcing you to re-authenticate constantly.
Support & Troubleshooting
Using account identifiers and interaction timestamps to diagnose issues if something isn't working as expected, or if you reach out for help.
Keeping the Service Reliable
Basic operational logging — errors, uptime, request volume — used to keep a Service stable and secure, never to build a profile of you.
Our Data
Guarantees
Across every Service we operate, the same guarantees hold. Where a Service connects to Google, this also means we strictly comply with the Google API Services User Data Policy, including its Limited Use requirements.
Your data is never used to serve ads, build ad profiles, or target marketing.
We do not sell, rent, trade, or transfer your data to any third party.
Your personal data is never fed into AI or machine learning models.
No member of the Vector Workflows team reads your data without your explicit written permission.
Google Workspace Integrations
Where a Service connects to a Google product on your behalf — Calendar, Sheets, or Drive — the exact Google user data it accesses, the exact API scope it requests, and what it's used for is listed in that Service's own disclosure below, not buried in general language here. This data is never used for advertising, is never used to train AI or machine learning models, and is never sold or shared beyond what's needed to operate that Service. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Third Parties &
Disclosure
01 Connected Platforms
To function, a Service may exchange data with the platform you've connected it to (such as Google or Telegram), strictly limited to the actions you've authorized. That platform's own privacy policy governs its handling of your data on its end.
02 Service Providers
We may use infrastructure providers (hosting, encrypted storage) to operate our Services. These providers process data strictly on our behalf and are not permitted to use it for their own purposes.
03 Legal Requirements
We may disclose limited data if required to comply with applicable law, a valid legal process, or to protect the rights, safety, or property of Vector Workflows or others.
04 Never Otherwise
Outside of the above, your data is not shared, sold, or disclosed to any third party.
You Stay
In Control
You can disconnect any Service and wipe your data from our systems whenever you choose.
One-Click Wipe
Use the built-in delete or disconnect option inside any Service's own interface. This immediately purges your stored tokens and session credentials from our servers.
Platform Security Settings
You can also revoke access directly from the connected platform's own security settings — for example, your Google Security Dashboard — at any time.
Encryption
All communication between a connected platform, our servers, and any third-party API is protected using industry-standard encryption in transit. Your secret tokens are stored in isolated environment variables and encrypted datastores, regardless of which Service you're using.
Per-Product
Data Disclosures
The clauses above are the general rules that govern every Service we operate. Because what one Service actually touches — a calendar, a spreadsheet, a phone line — is different from another, each product below has its own plain disclosure of exactly what it accesses and why, in addition to (not instead of) everything above.
Google Calendar Scheduler
Builds your day's schedule on top of your connected Google Calendar.
WA Site Tracker
Organizes site photos and updates from your engineers into your own Google Sheet and Drive folder.
Missed Lead Responder
Texts back and logs details from callers your business line couldn't answer.
Google Calendar
Scheduler
This Service connects to your Google Calendar so you can build out your entire day's schedule with a single click — adding tasks, clearing a day, planning future days, and managing your account settings and profile, all from one place.
A.1 Google API Scope Requested
This is the only Google scope our application requests or calls. It does not match, and is narrower than, full calendar read/write access.
A.2 Google User Data We Access
Within that scope, we read and write: event titles and descriptions, event start and end date/time, and the free/busy availability implied by your existing events. We do not access your Gmail, Drive, Contacts, or any other Google product through this Service, and we do not read calendar data outside of events (such as calendar settings or other calendars you haven't connected).
A.3 How It's Used
Solely to perform the actions you trigger — creating, updating, clearing, or rescheduling events when you add a task, clear your day, or plan a future day. Nothing here is used for advertising, is fed into any AI or machine-learning model, or is shared with anyone else.
A.4 Your Controls
In-app settings let you reset your profile, adjust preferences, or delete your data outright. Disconnecting the Service immediately revokes our stored tokens and deletes your cached schedule data from our systems; you can also revoke access anytime from your Google Security Dashboard.
WA Site
Tracker
You create a Google Sheet and Drive folder for your project (or ask us to create one), then share that Sheet and folder with our service account. Your engineers send photos and descriptions to a WhatsApp bot, and the Service files them into your Sheet and Drive in an organized, per-site structure. You control who can use the bot and can configure project name, engineer names, site location, and similar settings.
B.1 Google Data We Access
Only the specific Google Sheet(s) and Drive folder(s) you have explicitly shared with our service account — never your wider Drive, other Sheets, or any file you haven't shared with us. Access is scoped through Google's own file-sharing permissions, not a broad account-wide OAuth grant.
B.2 WhatsApp & Bot Data
The phone numbers of engineers and other users you've authorized to use the bot, the photos and text descriptions they send, and the settings you configure (project name, engineer names, site location, and similar). This is used only to route each submission into the correct row and folder in your Sheet and Drive.
B.3 Sharing
Submitted photos and data are written only into your own Google Sheet and Drive folder — storage you own and control. We do not share this data with any other party.
B.4 Your Controls
Remove the service account's access from your Sheet or Drive's own sharing settings at any time to cut off access immediately. Contact us to have your access-list and configuration data deleted from our systems.
Missed Lead
Responder
When a call to a connected business line rings and goes unanswered, this Service automatically texts the caller back, and sends the business owner a Telegram message with the caller's contact details and anything else the caller shared. Business owners can optionally configure a custom greeting and keypad menu for callers.
C.1 Data We Collect
The caller's phone number, the automatic SMS exchange, and any additional information the caller chooses to share — such as answers to a general query form, a keypad selection, or a voice note — along with the time of the call.
C.2 How It's Used
To send the caller an automatic SMS response, to notify the business owner via Telegram with the caller's details, and to log the same information to a Google Sheet the business owner has connected for their own records. Where a business owner enables a custom greeting, it is used only to greet and route that caller according to the owner's configuration — never to build a profile of the caller or to train any model.
C.3 Google Data We Access
Only the specific Google Sheet the business owner connects for lead logging, and only to append new rows — no other Sheets, Drive files, or Google data are accessed.
C.4 Sharing & Retention
Caller details are shared only with the business owner who received the missed call, via Telegram and their connected Sheet. This is a client-configured business tool, not a public consumer app; the business owner can request deletion of stored lead records at any time.
Children's
Privacy
Our Services are not directed at children, and we do not knowingly collect data from anyone under the age of 18, or the age of legal majority in their jurisdiction. If you believe a child has provided us data, contact us and we'll remove it.
Changes To
This Policy
We may revise this policy from time to time as our Services evolve. Material changes will be reflected by a last updated date on this page, and where practical, communicated directly. Continued use of a Service after changes take effect constitutes acceptance of the revised policy.
Questions or
Support?
If you ever have questions about how your data is handled, reach out directly.
Email SupportLast updated: August 28, 2026