Privacy policy
Effective September 9, 2026. This policy explains how MeetingBrand ("MeetingBrand", "we", "us") collects, uses and protects information.
1. What MeetingBrand does
MeetingBrand is a business service that creates branded virtual-meeting backgrounds and name bars for a company and delivers them to that company's employees' meeting applications (Zoom, Microsoft Teams, Google Meet, Zoho Meeting). Our customers are companies; the people whose data we process are their administrators and employees.
2. Data we collect
- Brand-set builder — the builder at https://meetingbrand.com/app/ runs in your browser. The domain you type is used to fetch that company's public logo and colors; the images you create are rendered on your device and are not uploaded to us during early access.
- Account data — the administrator's name, work email and company, given when requesting access or signing up. You can sign up with a work email and password or with Sign in with Google (which shares only your Google email address and basic profile with us). The domain of your work email is used to identify your company and fetch its public brand (section 7).
- Directory data — when an administrator connects a platform, we import employees' display names, email addresses, job titles, departments and platform user identifiers, using the permissions shown on the platform's consent screen.
- Connection data — the OAuth tokens the platforms issue so the connection keeps working. They are encrypted at rest and never shown to anyone.
- Brand and image data — logos, colors, scenes and the background images we render for each person.
- Delivery records — which image was delivered to which person, when, and the result, so administrators can see who is on brand.
- Technical data — standard server logs (IP address, browser, timestamps) kept for security and up to 90 days. This website is hosted on GitHub Pages, which logs requests under GitHub's privacy statement; fonts are loaded from Google Fonts.
We do not read meeting audio, video, recordings, chat messages, calendars or files.
3. How we use it
To render personalised backgrounds, deliver them to employees' meeting applications, show administrators delivery status, keep the platform connection alive, provide support, and secure the service. We do not sell personal data and we do not use it for advertising.
4. Google API Services
MeetingBrand's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google Workspace directory data only to import your organization's people into MeetingBrand for the purpose of personalising and delivering backgrounds; we do not transfer it to third parties except as needed to provide the service, do not use it for advertising, and do not allow humans to read it except with your permission, for security, or to comply with law.
Sign in with Google. If you choose to sign in with Google, we request only your Google email address and basic profile (the openid and email scopes) to create and identify your account. Authorization happens directly between your browser and Google; your Google password is never seen by MeetingBrand. Google user data received this way is used only to sign you in, is not transferred to third parties except as necessary to provide the service, and is never used for advertising. You can revoke MeetingBrand's access at any time at myaccount.google.com/permissions.
5. Sharing
We share data only with the meeting platforms you connect (Zoom Video Communications, Microsoft, Google, Zoho — to deliver backgrounds and read your directory as authorized) and with our infrastructure providers under data-processing terms (website hosting: GitHub; application database and file storage: Supabase). We disclose data when the law requires it.
6. Where your data lives
Account, brand, background, directory and delivery data are stored with our database and file-storage provider, Supabase, in its Frankfurt (EU) region, protected by industry-standard security and row-level access controls so that each company's data is visible only to that company's users. This website and the application page are hosted on GitHub Pages. Usage events (for example that a brand was fetched or a background was downloaded) are recorded with a random device session identifier and, when you are signed in, your user identifier, so we can see where the product works and where it fails; they are never sold or used for advertising.
7. Account data and deletion
When you sign up, the domain of your work email (for example acme.com) is used to fetch your company's public logo and colors from its public website and to create your brand kit; nothing is read from your mailbox. Your brand kit and the backgrounds you save are stored with your account so they can be reused, updated and deployed to your people.
- Self-serve deletion — you can delete your account at any time from Settings → Danger zone in the application. This permanently removes your login, your profile and, when you are the last user of your company workspace, the workspace itself with its brand kit, backgrounds, uploaded logos, directory data and delivery records.
- By request — write to support@meetingbrand.com from the email address on the account and we delete it for you, or send you a copy of your data, within 30 days.
- Retention — data is kept while your account is active. After deletion it is removed from live systems immediately and from backups within 30 days, except where the law requires us to keep it longer.
8. Retention and deletion of platform data
Directory and delivery data are kept while the platform connection is active. Disconnecting a platform deletes the data synced from it within 30 days; deleting your MeetingBrand account deletes everything within 30 days. Any administrator or employee can ask us to access, correct or delete their data at support@meetingbrand.com; we answer within 30 days.
9. Security
Data is encrypted in transit (TLS 1.2+) and at rest; OAuth tokens are stored encrypted with keys separate from the database; access is limited to staff who need it to operate the service; we log administrative access.
10. International transfers
Our providers process data in the EU and the United States under standard contractual clauses or equivalent safeguards.
11. Children
MeetingBrand is a business service and is not directed to anyone under 16.
12. Changes
We will post changes on this page and update the effective date; material changes are announced to administrators by email.