Effective date: March 18, 2026
ABE is operated by Viewcy, Inc. (“Viewcy,” “we,” “us”). This Privacy Policy describes how we collect, use, and protect information when you use the ABE platform (“Service”).
Account information. Name, email address, and organization details you provide during registration.
Usage data. Pages visited, features used, timestamps, and device/browser information collected automatically.
Connected service data. When you connect third-party services (QuickBooks, Slack, GitHub, Intercom, Shopify, and others), we access and store data from those services as authorized by your OAuth grants or API credentials. This may include financial records, customer information, conversations, issues, and analytics events.
Customer data you import. Feedback, conversations, financial records, and other business data you bring into ABE.
We use collected information to: operate and improve the Service; provide AI-powered analysis, recommendations, and automated workflows; sync and aggregate data from connected services; send notifications and reports you have configured; and comply with legal obligations.
ABE integrates with services including Intuit QuickBooks, Slack, GitHub, Intercom, Shopify, Mixpanel, and others. Each integration accesses only the scopes you authorize. We do not sell or share your data with these providers beyond what is necessary to operate the integration. Your use of connected services is also governed by their respective privacy policies.
Advertising & conversion measurement (Meta Pixel & Conversions API). On our public marketing pages we use the Meta (Facebook/Instagram) Pixel and Conversions API to measure the effectiveness of our advertising. This sets first-party cookies (e.g. _fbp, _fbc) and sends Meta a record of page views and conversion events such as sign-up. Where we send identifying fields (e.g. email) to Meta for ad attribution, those values are cryptographically hashed (SHA-256) before transmission — we do not send raw personal information. We honor the Global Privacy Control browser signal: when it is enabled we revoke advertising consent and apply Meta’s Limited Data Use. You can further limit this with an ad-blocker or by adjusting your Meta ad preferences. This measurement runs only on our marketing pages, not inside your authenticated workspace data.
Google Workspace integrations. ABE’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Each Google integration accesses only the data needed to provide a specific feature:
Google Meet (scope: meetings.space.readonly) — reads metadata for past Google Meet conferences and their transcripts when generated by Meet. ABE imports transcript text into your workspace so ABE can reference meeting context in answers. Data is scoped per tenant and never shared across tenants.
Google Analytics (scope: analytics.readonly) — reads GA4 metrics for properties you authorize. Used to surface traffic, conversion, and engagement data in the analytics surface.
BigQuery (scope: bigquery.readonly) — runs read-only queries against datasets you authorize. Used to answer custom analytics questions you ask ABE.
Google Drive / Docs (scope: drive.readonly) — reads documents you authorize so ABE can reference them. Imported document text is stored in your workspace’s Data Lake and is visible to members of that workspace, so only connect an account whose documents you are willing to share with your team. Data is scoped per tenant and never shared across tenants.
Gmail (scopes: gmail.send, gmail.readonly) — each user connects their own Google account. ABE reads that user’s inbox so it can answer questions about their mail and follow up on customer conversations, and sends email on their behalf. Every outbound email is confirmed by a person before it is sent; ABE never sends email on its own. Inbox content is visible only to the user whose account it came from — it is not shared with their colleagues. Synced mail is kept until you delete it — we do not remove it on a timer — and you can delete any message, any conversation, or everything ABE has synced at any time. You can also set a retention window on the connection if you want mail aged out automatically.
Google Sheets — via a service-account / explicit share model; no user OAuth scope is requested. Used to import financial records and other tabular data.
ABE stores Google API tokens encrypted at rest, refreshes them only when needed to fulfill a sync the tenant authorized, and deletes them when the integration is disconnected. Imported transcript and analytics data is deleted from ABE’s systems when the source integration is disconnected, on tenant request, or on account deletion (see Data Deletion).
ABE uses AI models (including Anthropic Claude) to analyze your data and generate insights. Your data is sent to AI providers solely for processing your requests and is not used to train third-party models. We retain AI interaction logs for service improvement and debugging.
We retain your data for as long as your account is active or as needed to provide the Service. You may request deletion of your account and associated data at any time by contacting us. When you disconnect a Google integration ABE deletes its stored tokens for it immediately, and you choose whether to also delete the data already synced. Google issues a single authorization covering all of the Google services you have connected, so ABE revokes that authorization with Google when you disconnect your last Google integration — disconnecting one while others remain connected would otherwise cut off those too. You can revoke ABE’s access for all Google services at any time from your Google account’s third-party access settings. Aggregate records derived from that data (for example financial totals) may be retained so historical reports stay accurate — see Data Deletion for exactly what is removed and what is kept. Previously this page stated that connected service data was always removed on disconnect the integration.
We use encryption in transit (TLS) and at rest, scoped multi-tenant isolation, and encrypted credential storage. Access to production systems is restricted. We do not expose, sell, or misuse customer data. See our Security Architecture for technical details.
You may access, correct, or delete your personal data by contacting us. If you are in the EU/EEA, you may exercise rights under GDPR including data portability and the right to object to processing.
We may update this policy from time to time. Material changes will be communicated via the Service or email.
For privacy inquiries, contact us at privacy@viewcy.com.
Viewcy, Inc.
New York, NY