ConnectorCONNECTOR · PUBLIC POLICIES
Privacy Policy
This policy describes data handled by this self-hosted Connector installation. Its operator is Vectre Pay Inc; privacy questions and deletion requests can be sent to contact@vectrepay.com. It applies to this installation, not to the independent services you connect.
Data processed
When an account is connected, Connector stores the access credentials needed to use the platform and an account summary such as its identifier, display name and available resources. It also processes configuration, AI access permissions, authorization metadata, action inputs, scheduling information, job status, results and error messages. Depending on the tools used, inputs and results may contain posts, video links, comments, messages, analytics, advertising data, workspace documents, email, notes or bank account and transaction information.
TikTok connection verification reads the authorized account’s basic profile. Publishing requests send the selected caption, video source URL, privacy and interaction choices, commercial-content and AI-content declarations, and the required consent to TikTok. Creator settings, publishing status and selected owned-video metrics are read from TikTok as requested. TikTok retrieves submitted video media from its supplied source URL.
Why data is used
The app uses this data to authenticate accounts, maintain approved access, carry out requested actions, run confirmed schedules, display results, prevent duplicate submissions, and show failures for troubleshooting. The public operator name and contact email are displayed on these policy pages. A TikTok website-verification text file explicitly uploaded by the owner is publicly served at its verification URL until replaced or removed.
Where data goes
Requests and necessary data are sent to the selected platform through its API. Authorized AI clients receive tool results they request; the app does not control those providers’ retention or use of results. Platforms, AI providers and any hosting or tunnel provider selected by the operator (such as ngrok) process relevant traffic under their own policies. Network infrastructure also handles connection metadata. The app does not include an advertising tracker or a facility for selling connected-account data.
Obsidian reads and writes the local vault folder selected by the owner. When Obsidian Sync is enabled in the desktop app, that separate app may sync changes to the owner’s cloud vault. Connector does not collect the Obsidian Sync password. Bank linking uses Plaid Link; Connector receives a Plaid access token and supported account, balance and transaction data, not the bank login credentials entered into Plaid Link. Bank tools do not transfer funds.
Google account data and purposes
Google sign-in supplies an account identifier and verified email address so Connector can label the connection and keep accounts separate. OAuth access and refresh tokens maintain the access you approve. Connector requests the service permissions for the connector or Workspace apps you select; declining permission can make the corresponding feature unavailable.
- YouTube: channel identity, owned-video information, available comments and channel metrics support channel selection, reporting and replies. A requested upload sends the video and its selected title, description and publication settings to YouTube.
- Google Ads, Analytics and Search Console: accessible customer accounts, properties, campaign data and performance reports support reporting and requested management actions. Authorized writes may send campaign changes, eligible click-conversion records, Analytics key-event settings or sitemap submissions to Google.
- Sheets, Docs and Slides: requested spreadsheet cells, document text and presentation content support reading, creating and editing the selected resources.
- Gmail and Chat: requested message IDs, sender and recipient details, subjects, message text and Chat spaces support searching, reading, drafting and sending messages. Gmail attachments are not downloaded by the current tools.
- Drive, Meet, Tasks and Voice: file metadata and app-managed file content, meeting links and conference records, task content and administrator audit events support their requested tools. The Voice integration does not access personal call recordings, text messages or voicemail.
- Maps: public place searches use a separately configured Google Cloud project key. Connector does not read your personal Maps Timeline or saved places.
Google Workspace agent profiles restrict an AI connection to the Google accounts and apps selected by the owner. Standard Google connectors, such as YouTube and Ads, are covered by standard platform access. An authorized AI client receives the results of its permitted requests. These results can contain Google account data, including email or document text; approving an AI connection allows this transfer for the requested features.
Google API Limited Use commitments
The operator commits that Connector’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements, and the applicable Google Workspace API User Data and Developer Policy.
Google user data is used to provide the requested user-facing features described here. Connector does not sell that data, build advertising profiles from private Workspace content, or train or improve generalized AI models. Transfers must be limited to providing or improving the permitted features, or other purposes expressly allowed by Google’s policies, such as security or legal compliance. Human access must also be limited to the cases allowed by those policies.
The operator must authorize only AI providers and other recipients whose terms and data-use settings are compatible with these restrictions. An AI provider’s access is not permission to use Google data for unrelated purposes or generalized model training. Connector cannot independently inspect or enforce an external AI provider’s retention or training practices; review that provider’s terms and settings before authorizing access. This statement is an operator commitment, not a claim that Google has verified or approved this installation.
Storage and security
Records are stored in the installation’s local database on the owner’s computer or chosen server. Connector encrypts stored platform credentials, saved settings, job inputs and job results. Some metadata, including account summaries, job identifiers, timestamps, statuses and error messages, is not encrypted by the app. The encryption key is kept in the installation’s local configuration, so protection of the device, configuration and backups remains important. Platform credentials and the encryption key are not published by these pages.
Cookies and authorization records
The dashboard uses a necessary sign-in session cookie with a lifetime of up to 12 hours. Short-lived authorization state links a platform sign-in to the owner’s session. AI authorization uses limited-life access and refresh tokens; expired or revoked grants and token records are cleaned during authorization activity. Previously approved AI client registration metadata may remain for reconnection, subject to a bounded registration limit. These public policy pages do not require sign-in and do not add tracking cookies.
Retention, disconnecting and deletion
Connection credentials and account summaries remain until disconnected or removed by the operator. Settings and job inputs, history and stored results remain until explicitly removed from the installation; there is no automatic job-history deletion schedule. A cancelled job can still appear in history. Disconnecting an account removes that connection’s stored credential and account summary, but does not erase previous job records or platform-side content. Revoking an AI connection stops future access through that grant; it does not retrieve results already sent to the AI provider.
Contact the operator to request access, correction or deletion of data held by this installation. Because some records do not have a per-record deletion control, removing all installation data may require the operator to stop the app and delete its database and relevant backups. Local Obsidian notes, external platforms and AI providers hold their own copies separately. Remove content there or use those providers’ privacy controls as appropriate. The operator should retain data only as needed for the purposes above and applicable obligations.
For Google, disconnect the relevant connector or Workspace account in Connector to remove its saved credentials and account details. Disconnecting a Workspace account also removes its agent assignments. You can separately remove Connector’s access through Google Account third-party connections. Revocation stops future authorized Google access; it does not delete existing content in Google or copies already held in action history, backups or AI conversations. Workspace read results are returned to the requesting client without a saved read-history record; account settings and write receipts remain until removed from the installation. Contact the operator above for deletion of retained Google data, and use the AI provider’s controls for its separate copies.
Your choices and changes to this policy
You can decline platform or AI authorization, select available permissions, disconnect accounts, revoke approved AI access and cancel pending scheduled actions. Data rights depend on applicable law and the operator’s circumstances; use the contact above to make a request. The operator may revise this notice when the installation changes; the effective date identifies the current version.