Privacy Policy
Last updated: 2026-11-04
This Privacy Policy explains how Quassum MB (“Quassum,” “we,” “our”) collects, uses,
and protects information when you use FutureBase.
For service terms, please read our Terms and Conditions.
Overview
We respect your privacy. This policy describes what data we collect, why we collect it, and the choices you have. It applies to all visitors, customers, and end-users of futurebase.io.
Information We Collect
| Category | Details (examples) |
|---|---|
| Account Data | Name, email address, password hash. |
| Payment & Billing | Managed by Stripe via Polar.sh checkout (PCI-DSS compliant); Quassum never stores raw card data. |
| Usage Data | Prompts, responses, logs, IP address, device/browser metadata, timestamps. |
| Support Comms | Emails, tickets, chat transcripts. |
How We Use Your Information
- Provide and maintain the service
- Troubleshoot, secure, and improve performance
- R&D and model fine-tuning on de-identified data (never on Google user data, see Google User Data below)
- Send product updates or marketing emails (opt-out link in every message)
- Comply with legal obligations
Legal Bases for Processing (GDPR)
- Contract – deliver the service you request
- Legitimate interest – improve, secure, and market our service
- Legal obligation – keep records for tax or regulatory purposes
- Consent – marketing emails and cookies
Data Sharing & Processors
| Processor | Purpose | Region | Link |
|---|---|---|---|
| Polar.sh | Subscription & checkout management | EU | polar.sh |
| Stripe | Payment processing | US/EU | stripe.com |
| Vercel | Server hosting | EU/US | vercel.com |
| Railway | Backend hosting (containers) & Postgres database | EU/US | railway.app |
| Cloudflare | DNS, CDN, WAF, optimization | Global | cloudflare.com |
| Cloudflare R2 | Object storage (file uploads, assets) | Global | developers.cloudflare.com/r2 |
| Google (GTM/Ads/GA) | Tag management, ads, analytics | Global | marketingplatform.google.com |
| Meta (Pixel + CAPI) | Ads measurement and conversions API | Global | facebook.com/business/tools/meta-pixel |
| LinkedIn (Insight + CAPI) | Ads measurement and conversions API | Global | linkedin.com |
| PostHog | Product analytics | EU | posthog.com |
| Grafana Cloud | Observability & web vitals | EU/US | grafana.com |
| Resend | Transactional email delivery | US/EU | resend.com |
| Exa | Website crawling / scraping for knowledge ingestion | US | exa.ai |
| OpenAI / Groq / X Grok / Cloudflare Workers AI | LLM inference providers (chat, RAG, tools) | Global |
We sign Data Processing Agreements and, where required, Standard Contractual Clauses with all processors.
Cookies & Tracking
We use first-party cookies (session, authentication, preferences) and third-party cookies
(analytics, CDN). Manage preferences at
futurebase.io/cookies.
Analytics & Ads
- We use
gtag.jsvia Google Tag (GTM/Google Ads/Analytics) where enabled. Consent defaults to denied until granted. - We use PostHog for product analytics; EU data residency is configured where available.
- We load LinkedIn Insight Tag and use LinkedIn Conversions API for measurement.
- We use Meta Pixel and Meta Conversions API (server-to-server). We may read
_fbpand_fbccookies to improve attribution. - You can opt out or adjust preferences at
Settingsor/cookies. Browser-level ad preferences and Do Not Track are respected where supported.
Data Retention
We retain user data for 2 years after the last recorded usage or account deletion, unless law requires longer.
Security Measures
- Encryption in transit (HTTPS); integration credentials encrypted at rest with AES-256-GCM
- Role-based access and least-privilege principles
- Documented incident-response plan
International Transfers
When data moves outside the EEA, we rely on Standard Contractual Clauses (SCCs) and additional safeguards (encryption, access controls, monitoring).
Your Rights
- GDPR – access, rectify, erase, restrict, portability, object, and avoid automated decision-making
- CCPA – know, delete, opt-out of sale/sharing, freedom from discrimination
To exercise any right, email [email protected].
Children’s Privacy
The service is not directed to anyone under 13 years old. If we learn that a child has provided personal data, we will delete it promptly. Parents may contact us to request removal.
Changes to This Policy
We may revise this policy periodically. Material changes will be emailed before they take effect. The “Last updated” date above shows the current version.
Contact
For privacy questions or to reach our Data Protection Officer, email
[email protected].
Supported languages: English (canonical). Machine-translated copies are provided for convenience only and are non-binding.
AI Providers
To provide AI responses and tools, your prompts, context (e.g., website content), and the model outputs may be sent to third‑party AI providers you select in the product (OpenAI, Groq, X Grok, Cloudflare Workers AI). We configure “no training”/data‑control flags where providers support them. Logs may contain hashed or redacted identifiers. You can change the default model in settings; using a provider implies sharing the necessary data with that provider to perform the request.
Crawling & Indexing
If you connect a site or sitemap, we may fetch and process publicly available pages, files, and metadata to build a knowledge base for your chatbot. We attempt to honor robots.txt and standard crawl-delay directives where feasible. You can request re-crawl or deletion of indexed content at any time; deletions propagate to caches within a reasonable period.
Browser Extension
The FutureBase browser extension reads a page only when you click Add this page. It then sends the address, title and visible text of that page to FutureBase to add it to the agent you picked, and nothing else: no browsing history, other tabs or cookies. Pages you add are stored and processed like the rest of your agent’s knowledge and are never fetched again on their own. The access token that connects the extension is stored locally in your browser; we keep only a one-way hash of it. You can revoke a token at any time from your dashboard.
Google User Data
Some features let you connect a Google account. We only ask for the access each feature needs, you can disconnect at any time, and we treat the data as follows.
Google sign-in. When you sign in with Google we receive your name, email address and profile picture to create and identify your account. We request no other Google data at sign-in.
Google Drive (knowledge base). If you connect Google Drive, we request read-only access
(drive.readonly) so that you can choose files and folders for your agent to learn from. We
read only the items you select, convert their text into your agent’s knowledge base, and keep
that text until you remove the item or disconnect Drive. We never modify, share or delete
anything in your Drive.
Google Calendar (meeting booking). If a team member connects Google Calendar so that the agent and the booking page can offer meetings, we request:
calendar.freebusyto read only the busy/free intervals of the calendars the team member selects, so customers are offered times when the team member is free. We never read event titles, descriptions, attendees or any other event content, and busy intervals are kept in a cache for at most 60 seconds.calendar.calendarlist.readonlyto list the team member’s calendars once, on the settings page, so they can choose which calendars to check for conflicts and where to add meetings. We store only the selected calendar IDs.calendar.events.ownedto create the meeting event (with its Google Meet link) on the team member’s own calendar when a customer books, to update it when the customer reschedules and to delete it when the meeting is cancelled. We only touch events that FutureBase itself created and never read, change or delete other events.
How we protect and use this data. Access and refresh tokens are encrypted at rest (AES-256-GCM) and used only by our servers. Google user data is used solely to provide the feature you connected; it is not sold, not used for advertising, not used to train or improve AI models, and not transferred to third parties except as needed to provide that feature or as required by law. Disconnecting Drive or Calendar in FutureBase revokes our access at Google and deletes the stored tokens; deleting your account removes the data we kept from Google.
FutureBase’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
CCPA “Do Not Sell or Share”
We do not sell personal information. We may “share” data for cross‑context behavioral advertising as defined by CCPA/CPRA when ads/analytics are enabled. You can opt out at /cookies or by contacting support; we will honor Global Privacy Control signals where supported.