1. Scope of this policy
This policy describes how CRM by Fatek collects, uses, stores and processes platform usage data, integrations enabled by the customer business and support channels in a B2B SaaS context.
Nuvemshop integration
When authorized by an administrator, the integration accesses store customers, products, variants, prices, inventory and orders. Changes to linked records may be sent to Nuvemshop according to synchronization settings. This integration's credentials are encrypted on the server.
Access or deletion requests received by webhook are recorded for the responsible administrator. Deletion considers retention obligations, particularly tax and financial records. Disconnecting stops the integration and removes the saved token; business records are not automatically deleted.
TikTok integration — organic content
When an administrator authorizes the connection, we process account identifiers, name, avatar, granted permissions and credential validity to identify the destination and control workspace access. New credentials and refreshes are encrypted on the server. Organic authorization does not grant access to TikTok API for Business advertisers, leads or conversions.
When a user requests or schedules a video transfer, TikTok receives temporary access to the selected media through a signed URL. The caption remains in CRM to copy; the creator must open the notification in the TikTok app, review the options and finish posting. This mode does not publish automatically. We retain upload receipts and identifiers to verify outcomes and avoid duplication.
Disconnecting disables the channel and removes local credentials while preserving operational records. We request revocation from TikTok when possible; remote results depend on the provider. Disconnecting does not delete videos already sent to or published on TikTok. CRM data retention follows the purposes and deletion procedures described in this policy.
TikTok Business integration — setup
The optional TikTok Business connection uses separate authorization. We store encrypted credentials and authorized advertiser identifiers; the administrator explicitly selects each workspace’s accounts. After approval and a controlled release, permitted users can query daily reports for selected advertisers, including spend, impressions, clicks, currency and timezone. This integration does not import leads, send conversions or modify campaigns. Disconnecting removes this workspace’s local credentials and selection; revoking authorization in TikTok may affect other connections to the same app.
2. Data that may be processed
Registration and authentication data such as name, email and account information; operational data entered by the business, such as customers, deals, tasks, appointments and messages; technical and usage data needed to maintain, protect and improve the platform; and data from authorized integrations.
3. Purposes of processing
Authentication; CRM, scheduling, communication, ERP, inventory, orders and consignment workflows; delivery of contracted or requested features; technical support, security and maintenance; and automations and AI features enabled by the business.
4. Google APIs — sign-in, Gmail, Calendar, Meet, Ads, Sheets and Business Profile
Access to Google services requires explicit OAuth 2.0 authorization for the connected feature. Sign-in and integrations have their own flows; connecting one service does not automatically authorize every feature.
4.1 Permissions and features
openid, email, profile— Identify the account at sign-in using email and basic profile. Email and profile declarations correspond to userinfo.email and userinfo.profile.gmail.send— Permission retained in earlier sending grants. New connections use gmail.modify, which also permits sending, without requesting gmail.send separately. Existing grants are not revoked by this reduction.gmail.modify— Retrieve incoming messages and history, display them in the Inbox, send messages and replies in the original thread, and mark messages as read. Enabled AI features may process conversation context to generate replies. This scope does not allow immediate permanent deletion bypassing Trash. The Gmail workflows described here do not implement permanent message deletion.userinfo.email— Identify the account authorizing Gmail or data export; it may differ from the account used to sign in to the CRM.calendar.events— Permission retained in old connections. It is not requested in new authorizations. Existing connections continue working without automatic revocation.calendar.events.owned— Read, create, change and cancel events on owned calendars. The CRM uses the primary calendar. New authorization is restricted to the demo and authorized reviewer until Google verification.meetings.space.created— Create Google Meet spaces for appointments and access spaces created by the application.adwords— Discover authorized accounts and read campaign performance for reporting. Google's broad scope description does not change the read-only purpose of the reports described here.drive.file— Create and update export spreadsheets used by the application, without requesting general access to every Drive file.business.manage— Read authorized business accounts, locations and reviews, and submit replies whose exact text and location were explicitly approved by a person. A draft, including an AI-assisted draft requested by a user, is not published automatically. The Reviews integration does not implement Business Profile messaging.
4.2 Data processed and storage
Gmail: sender, recipients, subject, date, message and thread IDs, text content and relevant labels such as INBOX and UNREAD. The CRM stores synchronized data for display, history and continuity of communication.
Calendar and Meet: appointment data, times, participants when supplied, event identifiers and meeting links. Ads: authorized-account identifiers and performance data. Sheets: data selected for export and identifiers of spreadsheets used by the application.
Reviews: account, location and review identifiers, rating, text and public name when supplied, drafts and approval/publication records. Review content and drafts are cached for up to 30 days; the application's own operation audit records may remain after this content expires.
Data persisted by the CRM uses PostgreSQL on Supabase in Frankfurt, Germany (eu-central-1). The application runs on a Hetzner VPS in Europe. External services may process data under their own terms and in their own locations. Access follows workspace boundaries, permissions and applicable operational needs.
4.3 Limited Use and artificial intelligence
CRM by Fatek's use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including its Limited Use requirements.
Google API Services User Data Policy- Google data is used for user-facing features such as communication, calendar synchronization, reporting, exports and review replies, according to the authorized integration.
- Gmail data is not used for advertising, retargeting or interest-based advertising, or to train generalized AI models. Processing a conversation to generate a reply is distinct from training a generalized model.
- Human access to Google data is limited to what the user authorizes, what is necessary for security or legal obligations, or aggregated and anonymized data where allowed by Google's policy.
- When a business enables AI or requests a draft, the necessary content may be sent to the model provider to generate a response. Processing and retention depend on the service, configuration and applicable controls. A zero-retention agreement is not assumed.
- OpenAI API documentation describes default abuse-monitoring logs retained for up to 30 days, with legal and safety exceptions and retention controls subject to approval. Some features may also store application state. This policy does not assume the controls of any particular account.
4.4 Disconnection, authorization and deletion
Connections can be disabled in their respective CRM settings. The CRM removes its stored credentials for that integration; where applicable, it requests revocation from Google, whose result depends on the provider. Disconnecting Google Reviews removes only the Reviews connection and does not globally revoke the application's Google access.
Authorizations can also be managed directly in the Google Account. Disconnecting does not automatically erase history already synchronized to the CRM. To request account and data deletion, follow the deletion instructions or contact support below, subject to legal retention obligations.
Manage Google Account authorizations5. Meta APIs
When a business connects Meta channels, data and permissions enable authorized WhatsApp Business, Instagram, Facebook messaging, publishing, insights and lead-capture features. Processing is limited to the account's operational context and user-enabled features.
6. Sharing and access
For subscriptions, Asaas receives the identification and contact details provided by the payer and the verified email of the account starting checkout. Card details are entered in Asaas checkout; the CRM stores financial identifiers and states for receipts and plan access. Stripe continues processing previous contracts and existing top-ups. Google integration data is not shared with these providers for this purpose.
CRM by Fatek does not sell integration data or publicly disclose it for advertising enrichment. Data is shared with providers when needed to perform requested features with applicable authorization, or to meet legal obligations. Internal access is limited to necessary operations, support and security routines and applicable permissions.
7. Storage and security
We use technical and administrative measures to reduce risks of unauthorized access, improper alteration or data loss. Retention considers service operation, integration settings, deletion requests and legal obligations. No environment is completely infallible.
8. Rights and requests
Requests about data, integrations and deletion may be sent to the contact below. Public account and data deletion instructions are available on the deletion page.
9. Changes to this policy
This policy may be revised to reflect product, integration and operational changes. The version published at this route is the current public reference.