VIBE WORK · LEGAL
Privacy Policy
Effective date: October 15, 2026 · Updated: October 16, 2026
How Vibe Work handles account information, public projects, responses, contacts, analytics and authorized Google integrations.
1. About this policy
This policy explains data handling for Vibe Work at vibework24.com and its operational integration, Vibe Work Assistant. References to “we” mean the team operating this service. For privacy questions or requests, contact contact@vibework24.com. This policy does not apply to independent websites linked from external listings.
2. Information we process
When you register, we process your email address, a password hash, account identifiers and session information. Depending on what you provide, client and freelancer profiles can include your public name, company or headline, biography, country, timezone, avatar and portfolio. We also process project descriptions, budgets, deadlines, proposals, response decisions and contact-sharing records. Optional contact details can include an email address, phone number or messenger information. Support correspondence and account-security requests are also processed.
3. Public and private information
Project pages, eligible public profiles and portfolio cases may be accessible without signing in and may appear in search engines. Do not place secrets, confidential customer data or private contact details in public fields. Proposal access is restricted by the relevant account and project roles. Client contact sharing follows the approval flow; a freelancer can choose to make supported contact details public. Once another person receives information, we cannot control copies they make. Removing information from Vibe Work does not immediately remove search-engine caches or third-party copies.
4. Why we use information
We use information to create and secure accounts, display profiles and projects, process proposals and contact approvals, provide notifications and account emails, respond to support requests, prevent abuse and understand how the service is used. Where applicable data-protection law requires a legal basis, these purposes rely on providing the requested service, legitimate interests in security and service operation, legal obligations, or consent where required. Optional publication or sharing choices remain subject to the controls available for that feature.
5. Cookies, browser storage and analytics
We use first-party session cookies to keep you signed in and protect account access. Browser storage can remember interface preferences and in-progress drafts. Example-project drafts are kept in the browser tab for up to 24 hours; the funnel does not store passwords in those drafts. First-party analytics records page paths, timestamps, referral channel, approximate country and events such as registration or project publication. Network addresses are processed for request handling, security and approximate geolocation; these analytics are not a claim of a visitor’s identity. The current analytics collector respects Do Not Track and Global Privacy Control signals. Clearing browser data removes local state but does not delete server-held account records.
6. Google data: access and purpose
Vibe Work Assistant connects Google accounts only for authorized Vibe Work operators. Marketplace registration does not connect a user’s Gmail. Access is obtained through a separate Google OAuth consent flow; the account holder can review and decline permissions. The current scopes are https://www.googleapis.com/auth/webmasters, https://www.googleapis.com/auth/gmail.readonly and https://www.googleapis.com/auth/gmail.compose.
7. Search Console information
The webmasters scope allows access to authorized property identifiers and permission levels, sitemap information, URL indexing and crawl reports, and aggregate search-performance data: query, page URL, country, device, date, clicks, impressions, click-through rate and average position. We use these records to diagnose indexing problems and evaluate Vibe Work’s search visibility. Reports can be stored as operational snapshots. Routine reporting is read-only; the scope also allows write operations such as a sitemap submission, which require a specific operator instruction. Search-performance reports do not identify individual search visitors.
8. Gmail information
The gmail.readonly scope can expose mailbox information, message and thread identifiers, labels, sender and recipient addresses, subjects, timestamps, snippets and message bodies. We read relevant service correspondence selected by an authorized operator to help handle requests and service operations. This permission is broader than a single message or folder. The gmail.compose scope allows creating and managing drafts and sending messages, including the recipients, subject and body the operator approves. Granting this permission is not permission to send every proposed message: each send requires the operator’s separate approval. No email content is published to marketplace profiles or project pages by the integration.
9. Google data: processing and sharing
Authorized operational requests can involve AI-assisted analysis, summarization or drafting. Relevant message text or search reports may be processed by assistant tooling and supporting inference providers to carry out that request. Hosting and operational-service providers process data only for the authorized service functions, not for unrelated marketing. We do not sell Google user data, use it for ad targeting, credit or lending decisions, or use it to train general-purpose AI models. We do not allow independent third-party use of Google data beyond the permitted service purpose. Human access to Google-derived data is limited to the account holder’s affirmative permission to review specific data, necessary security investigations, legal requirements, or aggregated and anonymized internal operational information as allowed by Google policy. Vibe Work Assistant’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
10. Google data: storage and retention
OAuth access and refresh tokens are stored in restricted server-side configuration files, separate from public web assets; they are not placed in browser storage, public profiles or page source. Search Console report snapshots and operator-requested working material may be retained in access-controlled operational files and assistant records. Email extracts and drafts may remain in those records when needed for the requested correspondence; drafts saved in Gmail also remain in the connected Google account. Operational snapshots do not currently expire automatically. Retention is reviewed when the connection is no longer needed or an account holder requests deletion; revoking Google access alone does not remove stored copies. Any legal or security retention exception and relevant backup limitations are considered when handling a request. We do not promise a fixed automatic deletion period that the service does not implement.
11. Revoke access and request deletion
You can disconnect Vibe Work Assistant in Google Account connections. This stops future access under that grant without deleting your Google account or its original messages. To request deletion of our stored Google data, email contact@vibework24.com with the subject “Vibe Work Assistant data deletion”, identify the connected Google account, and say whether the request covers correspondence, search reports or all retained integration data. Do not send a password, authorization code or token. We verify account authority, identify the relevant tokens and operational copies, and handle deletion or explain any legally required retention and backup limitations. You may request confirmation when this is complete. Data deletion is handled by the team, not by a button on this informational page.
12. Sharing and service providers
Information is shared with other users only as needed for the public features, project workflows and sharing choices described above. Hosting, email-delivery, security and authorized operational-tool providers may process information to support the service. We may disclose information when legally required or reasonably necessary to investigate abuse and protect rights or security. We do not sell personal information. External listings link to independent services whose privacy, application and payment rules apply when you leave Vibe Work.
13. Storage, security and retention
We use HTTPS, password hashing, server-side sessions and access controls; selected private contact fields and backup copies are encrypted. No system can promise complete security. Account and activity records may remain while your account is active and afterward where needed for support, security, disputes or legal obligations. Retention depends on the record and purpose; we do not promise that deleting a task immediately erases every record or backup. Access to retained data is restricted, and deletion requests are assessed for the relevant records, obligations and backup lifecycle. Providers may process information outside your country; applicable transfer safeguards must be considered where required by law.
14. Your choices and requests
You can edit supported profile and project fields, choose optional public contact settings and stop using the service. To request access, correction, export or deletion of account data, or to raise an objection or restriction request, email contact@vibework24.com from your account address when possible. Do not send your password. We may need proportionate identity verification before releasing or changing data. Requests are handled subject to applicable law, including relevant response deadlines and exceptions. You may also have the right to complain to your local data-protection authority.
15. Age and changes
The service is intended for adults able to enter agreements. Do not submit information about children. If you believe a child’s information has been supplied, contact us. We may update this policy as the service changes and will show the revised date here. Where required, material changes will receive additional notice or consent.