Skip to main content

Privacy Policy

FaaStr privacy policy.

What FaaStr collects across faastr.tech, the FaaStr app for Google Chat, and the Branda and VIZEO Chrome extensions - why, where it lives, and how to delete it.

Effective date: November 4, 2026 · Version 2026-11-04

FaaStr is a product line of datajoi ("datajoi", "we", "us"). This policy is specific to the FaaStr products listed below. It sits under, and should be read together with, the datajoi Privacy Policy, which governs everything datajoi does. Where this document is more specific about a FaaStr product, this document controls for that product. The FaaStr Terms of Service & EULA and the datajoi Terms govern your use of the products.

Contents

1. Who we are and what this covers

FaaStr is built and operated by datajoi, a company registered in the United States. This policy covers four things:

  • The website at faastr.tech and its subpages, including every waitlist, sign-up and assessment form.
  • FaaStr Flow for Google Chat (the "App"), installed from the Google Workspace Marketplace and used with the /faastr command.
  • Branda, a brand-asset manager Chrome extension, installed from the Chrome Web Store.
  • VIZEO, a site & AI visibility audit Chrome extension, installed from the Chrome Web Store.

The other products shown under "Built FaaStr" (LinkedUp, Votee, Battle Buddy, EpiSaaS, Facts & Data, Tagmin, promotto) are not yet released; the only data they collect today is a waitlist email, covered by section 2. votee.org is a separate site and links to the datajoi Privacy Policy directly.

2. The faastr.tech website, waitlists and forms

What you give us. When you join a waitlist, request early access, or take the Founder Fitness assessment, we collect what you type into the form: your email address, and where the form asks for it, your name, company or organization, and your assessment answers. Every form also records that you ticked the box agreeing to the Terms & EULA and this Privacy Policy, the time you did so, and the version of those documents (currently 2026-11-04).

What we collect automatically. Our forms are protected by Cloudflare Turnstile, which checks that a request comes from a person rather than a bot; Turnstile is governed by Cloudflare's privacy policy. With each submission we also store the page you submitted from, the country Cloudflare reports for your connection, and your browser's user-agent string. We do not store your IP address in our database. The site uses Google Tag Manager and Google Analytics 4 to count page views, installs and sign-ups. Advertising cookies and Google Ads conversion measurement are off by default; they run only if you choose "Allow analytics & ads" in the cookie bar, and visitors in the EEA, UK and Switzerland get analytics only after choosing too. You can change your choice by clearing this site's storage in your browser. We do not build advertising profiles and we do not sell your information.

How we use it. To put you on the list you asked to join, to email you about that product (when it launches, when your workspace is ready, meaningful updates), to show you your assessment results, to keep the forms free of spam, and to understand which pages bring people to us. We do not sell your information and we do not share it with advertisers.

Where it lives. Submissions are stored in a Cloudflare D1 database in the United States, with access limited to the people who run FaaStr. Confirmation emails are sent through Cloudflare Email. On datajoi.com, platform early-access requests may also be mirrored to a Google Sheet we control.

Retention. We keep waitlist and lead records until the product you signed up for launches and you have been told, or for 24 months after our last contact with you, whichever comes first, unless you ask us to delete them sooner. Assessment answers are kept so you can return to your results. Consent records are kept for as long as the lead they belong to.

Sharing. Only with service providers that host or process data on our behalf (Cloudflare for hosting, storage and email; Google for analytics and, on datajoi.com, Sheets), under obligations consistent with this policy; or if required by law.

3. FaaStr Flow for Google Chat

This section applies only to the FaaStr app for Google Chat (the "App"), installed from the Google Workspace Marketplace and used with the /faastr command.

3.1 Information the App accesses

  • Google Chat messages sent to the App. When you mention FaaStr or use /faastr, Google Chat sends the App that message along with the space it was sent in. The App does not read other messages in your spaces.
  • Basic profile information. Your name, email address and profile picture, and your Google Workspace domain, as provided by Google Chat with each message.
  • Google Drive files the App creates. The App uses only the drive.file scope (https://www.googleapis.com/auth/drive.file). It can see and edit only files it created or that you explicitly open with it. It cannot see the rest of your Drive.
  • Data the App generates. The company knowledge base, knowledge graph and related content the App builds from the messages and files above.

3.2 How we use it

We use this information only to provide and improve the features you use in the App: answering your requests in Google Chat, creating and updating documents in your Drive, and maintaining your company knowledge base and graph. We also use it to keep the App secure, prevent abuse, and meet legal obligations.

We do not sell your data, use it for advertising, or use it to build user profiles for any unrelated purpose.

3.3 Google API Services Limited Use disclosure

FaaStr'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.

In particular, data obtained through Google Workspace APIs is:

  • used only to provide or improve user-facing features that are visible in the App;
  • not transferred to others except as needed to provide or improve those features, to comply with applicable law, or as part of a merger, acquisition or sale of assets with notice to users;
  • not used for serving advertisements, including retargeting, personalized or interest-based ads;
  • not read by humans unless you give us permission for specific content, it is needed for security purposes such as investigating abuse, to comply with applicable law, or the data is aggregated and anonymized for internal operations;
  • not used to develop, improve or train generalized artificial intelligence or machine learning models.

3.4 Where your data is stored

Your data never leaves your Google Workspace. The documents the App creates, including your company knowledge base and graph, live in your own Google Drive, under your Google Workspace security controls. Data is encrypted in transit and at rest, and access is limited to systems and personnel who need it to operate the App.

3.5 Sharing

We share data only with service providers that host or process it on our behalf to run the App, such as Google, under obligations consistent with this policy and the Limited Use requirements above. We may disclose data if required by law or to protect the rights and safety of our users. We never sell it.

3.6 Retention and deletion

We keep your data while the App is installed in your Google Workspace. When your workspace uninstalls the App, we delete all of the App's data associated with that workspace. Files in your Google Drive are yours: uninstalling does not delete them, and you can remove them at any time.

You can also ask us to delete your data at any time before uninstalling by emailing support@datajoi.com.

3.7 Your choices

  • You can stop sending messages to the App, or remove it from a Google Chat space at any time.
  • Your Google Workspace administrator can uninstall the App for your whole organization from the Google Admin console.
  • You can revoke the App's Drive access from your Google Account permissions page.

4. Branda (Chrome extension)

Branda is a brand-asset manager that lives in a Chrome side panel. Branda has two parts. The extension runs in your browser and works with your own Google Drive. A small Branda account service, which we run, handles sign-in and the Pro plan. Your files, your folder index, your tags, and your brand content are never sent to our account service. There is no analytics or telemetry of any kind - not first-party, not third-party. Everything about your brand lives in two places: your own Google Drive, and the storage the extension keeps inside your browser. Your account and plan records live on our account service, described in section 4.5.

4.1 What Branda accesses

  • Your Google Drive. When you connect a folder, Branda uses Google's OAuth to request the drive and userinfo.email scopes. It reads the files under the folder you picked - names, sizes, dimensions, MIME types, folder structure, and Drive's own thumbnail images - to build a local index, and writes back to those same files when you rename them, move them, upload to them, or tag them. Branda needs the full drive scope rather than the narrower drive.file because its whole purpose is to organise files it did not create; drive.file cannot see them. Only files under the folder you chose are indexed, shown, or modified. To notice changes, Branda reads Drive's account-wide change feed and filters it on your machine; metadata for files outside your chosen folder is received from Google and immediately discarded. It is never stored, displayed, or sent anywhere.
  • Your email address and name. Read from Google when you sign in, to create your Branda account and show which account is connected. They are stored on our account service (section 4.5) and in the extension's browser storage.
  • Your Google sign-in token, once, at sign-in. The extension sends the Google token it received to our account service, which checks it with Google and then creates a session for you. The token is not kept after that check.
  • A web page, when you ask. "Grab assets from this page" reads the tab you are looking at - its title, favicon, logo images, og-image, stylesheet links, font declarations and any application/ld+json data blocks - and captures a screenshot of the visible area to sample its colours. This happens only when you click that button, only on that tab, and never in the background.

4.2 What leaves your machine

  • googleapis.com - Drive API calls and the one-off account lookup, whenever Branda indexes, syncs, or you change a file.
  • *.googleusercontent.com - requests for Drive's own thumbnails of your files, during indexing and classification.
  • fonts.googleapis.com, fonts.gstatic.com - a request for the font you selected, only when you add a Google Font to a kit.
  • The Branda account service (branda-api-prod.datajoi.workers.dev) - your Google sign-in token at sign-in, then your session token, to check your plan and to start a checkout or a cancellation. It never receives your files, index or tags. Contacted when you sign in, when you open the Upgrade or Manage dialog, and when the extension checks your plan.
  • Intuit (QuickBooks payments) - your name and email, to create your billing customer, and the invoice amount and plan. Contacted by our account service, not by the extension, when you choose a plan to buy.
  • The site you are on, and the origins it names - requests for that page's favicon, logos, images, stylesheets and font files, only when you click "grab assets from this page".
  • A dataset's own host - a request for chart rows, only when you click "Load data", after Branda shows you the host name.

That is the complete list. Nothing is sent to an AI or model API, an analytics service, or an error reporter. Your files, your index, your tags and your brand content are never sent to the Branda account service or to Intuit.

4.3 What is stored, and where

In your browser, via IndexedDB and chrome.storage.local: the index of your folder (file names, IDs, sizes, dimensions, folder paths, Drive thumbnail links), the tags Branda worked out, your extracted colour palette, and your settings. This never leaves the browser profile it was created in. Uninstalling Branda, or clearing the extension's data, deletes all of it.

In your Google Drive, on your own files: tags are written to each file's appProperties metadata, under keys prefixed branda.. This is what lets a tag survive a reinstall and follow the file when it moves. Renames, moves and uploads you approve are also changes to your Drive. Branda keeps no copy of any of this anywhere else.

Your files and the index of your folder are never copied to us. The only records we keep are the account and billing records in section 4.5.

Classification is local. Branda works out what a file is - logo, icon, banner, screenshot, light, dark, transparent - by reading metadata Drive already returned and by analysing the pixels of the thumbnail inside your browser. No file, thumbnail, or derived description is uploaded to any classification service, and no machine-learning API is called.

4.4 Your control

  • Disconnect at any time. Settings → Disconnect drops every cached token and forgets the connected folder. You can also revoke Branda's access to your Google account entirely at myaccount.google.com/permissions.
  • Undo. Every rename batch and every move is written to an operations log and can be reversed with one click. Renames are shown to you as a diff before anything is written.
  • Delete everything. Uninstalling the extension removes the local index and everything else Branda stored in your browser. Tags Branda wrote into your files' appProperties stay on those files, because they are your files and the tags are metadata on them; they are removable through Google Drive's own API.

4.5 What our account service stores

Only what is needed to sign you in and to record your plan:

  • Account: your email address, your name, and your Google account ID.
  • Sessions: a hashed form of your session token, when it was created, and when it expires. We do not store the session token itself.
  • Plan and billing: your current plan, its status and end date, the invoices we created for you (invoice ID, plan, amount, and payment link), and your billing customer ID from Intuit.
  • Operational logs: requests and errors for the service. Logs never include session tokens, Intuit tokens, or the body of a payment response.

Our account service does not store your Drive files, your folder index, your tags, your colours, your fonts, or any web page content you grab.

How long we keep it.

  • Account and sessions: kept while the account is active. If you have not signed in for 12 months, or you ask us to delete your account, we delete the account and its sessions.
  • Invoices and payment records: kept for 7 years after the payment date, as required for accounting and tax records, and then deleted.
  • Operational logs: kept for 30 days, then removed.

How to delete your account. Email privacy@datajoi.com from the address on your Branda account. We delete your account and its sessions within 30 days. Invoice and payment records are kept for the period above, because we are required to keep them.

Payments. Plans are paid through Intuit (QuickBooks). You pay on Intuit's invoice page, where your card details are entered and held by Intuit. Branda never receives your card number. We receive a confirmation of payment from Intuit, and we record it against your account.

Signing up for Branda launch or Pro updates on faastr.tech/branda is a website form and is covered by section 2.

5. VIZEO (Chrome extension)

VIZEO analyzes websites you choose for speed, SEO, AI-agent readiness, security hygiene and accessibility/policy compliance, and turns the findings into a fix plan you can hand to your own tools. VIZEO has no accounts and no sign-in. Nothing you audit is stored on any FaaStr or datajoi server.

5.1 Data handling

  • Analyses are user-initiated. The audit script is injected only when you click Analyze, fetches the site's own public files (llms.txt, robots.txt, index.json) from within the page, and reads public page metadata. Nothing runs automatically or in the background.
  • PageSpeed audits use Google's PageSpeed Insights API. When you click Analyze, the audited page's URL is sent to googleapis.com to run Lighthouse. Only the URL is sent; results render in the panel.
  • Provider detection uses DNS-over-HTTPS. During an analysis, the audited site's hostname is sent to Google Public DNS (dns.google) to read its public NS records, so the Report tab can link the right DNS dashboard.
  • Security scans are user-initiated and read-only. The security probe runs only when you click Scan. It fetches the site's own security.txt and sitemap.xml, re-fetches the current page (without your cookies) to read its response headers, and inspects the DOM for mixed content and similar risks. Scan results stay in the panel.
  • Compliance scans are user-initiated and read-only. The compliance probe runs only when you click Scan. It reads the page's own markup and computed styles to check accessibility (alt text, labels, contrast, headings, zoom and similar), and fetches the site's own /accessibility, /privacy and /terms pages - same-origin, without your cookies - to see whether those disclosures are published. Scan results stay in the panel.
  • "Fix with Claude" opens claude.ai with your fix list. When you click it and your DNS provider isn't recognized, the extension opens claude.ai/new with the prepared fix prompt - the audited domain and fix summaries - included in that URL, so Anthropic receives it if you proceed. The prompt is also copied to your clipboard first, and nothing is sent unless you click the button. Recognized providers open their own dashboard instead, with the prompt only on your clipboard.
  • Stored locally (chrome.storage.local): your settings - currently the optional PageSpeed API key - and your audit results, kept per domain (the last 10 run summaries plus the latest full result) so the panel can restore them when it reopens. Results never leave your machine; you can delete any saved run from the History section, and removing the extension removes them all.
  • Per-site access is opt-in and revocable. VIZEO asks for access to a site's origin only when you audit it; you can revoke any origin under the extension's Site access settings in Chrome.
  • No analytics, no tracking, no sale or sharing of data.

Signing up for VIZEO launch or Pro updates on faastr.tech/vizeo is a website form and is covered by section 2.

6. Your rights and choices

  • Unsubscribe. Every email we send has an unsubscribe link, or reply with "unsubscribe".
  • Access, correct, export, delete. Depending on where you live (including the EU/UK under GDPR and California under the CCPA/CPRA), you may have the right to access, correct, export or delete your personal data, to object to or restrict certain processing, and to not be discriminated against for exercising these rights. Email support@datajoi.com and we will respond within 30 days. We do not sell or share personal information for cross-context behavioral advertising.
  • Extensions. Branda and VIZEO store data only in your browser and (for Branda) your own Google Drive; uninstalling the extension removes what it stored in the browser.
  • Complaints. If you are in the EU/UK you can complain to your local data protection authority; we would appreciate the chance to address your concern first.

7. Children

FaaStr products are business tools and are not directed to children under 16. We do not knowingly collect data from children; if you believe we have, email us and we will delete it.

8. Changes to this policy

If we change this policy, we will update the effective date and version above. If a change materially affects how we use data from Google APIs, or how an extension handles your data, we will notify you before it takes effect. The version you agreed to is recorded with your form submission.

9. Contact

Join the waitlist

Join the FaaStr Flow waitlist

FaaStr Flow installs into your Google Workspace from the Marketplace.