Privacy Policy

Draft for review · Version 2026-11-01 · Prepared November 1, 2026. Publish an effective date when this release is ready for approved member registration.

This Policy explains how Gio Celenza MGMT, operating through Omniant, handles information in Figtree features that link to this Policy. Omniant is a division rather than a separate incorporated entity. “We,” “us,” and “our” mean Gio Celenza MGMT operating through that division. Figtree is a standalone product; this Policy does not automatically extend permissions granted to OMNII or replace a separate management-records policy.

1. Information we handle now

• Account details: your name, email address, internal account identifier, verification status, registration time, and, for email/password enrollment, the Terms/Privacy version and eligibility confirmation. Google sign-in does not require a separate Figtree Terms checkbox; we do not record it as an affirmative Terms or age confirmation.
• Authentication: salted, derived password values if you choose email/password login; Google account identifiers and basic identity information if you choose Google; hashed session tokens, session creation/expiry, and short-lived verification or password-reset records. We do not store your Google password.
• Operational requests: hosting and security providers may process IP addresses, browser request details, timestamps, and error information. The application uses keyed hashes of network information for short-lived abuse-control counters rather than creating a browsing-history profile.
• Support information: the message, email address, and any information you choose to provide when contacting us. Do not send passwords or unnecessary sensitive identifiers.
• YouTube connection: when you authorize it, your connected channel IDs/titles, channel statistics, available daily report metrics and aggregate age/gender/country reports that YouTube makes available, granted scopes, connection/refresh dates, and connection/optional Admin-sharing choices. Access and refresh tokens are encrypted on the server and are not sent to the browser or included in exports.
• Browser state: essential authentication cookies, short-lived sign-in state, and temporary interface state. Appearance choices are stored in this browser. Content-discovery preferences (topic, format, and region) are stored here per member. The dashboard does not include a sample viewer or imported creator records.

Private-beta access: the configured owner Admin maintains email addresses, optional reference names, and Approved, Pending, or Removed status in a restricted database. The Admin can see basic account metadata needed to administer access and a recent access-change history. These records are not sent to ordinary members or visitors. Approval is checked for account APIs. Removing access blocks subsequent access and invalidates that person’s sessions and verification/reset links; it does not automatically delete their account records. The owner Admin can open an approved member’s current Figtree workspace using a temporary Admin-initiated member session. The session identifies the acting Admin internally, lasts up to 30 minutes, and records its start and end in access history. The owner does not receive your password or a Google session. This does not itself authorize future third-party platform permissions or access to unrelated services.

Content discovery: when you request inspiration, Figtree sends your selected topic, format, and region to YouTube using your authorized connection to find recent public videos. This does not provide access to your private recommendation feed or identify individual viewers. Public video metadata may be cached for up to six hours without member data or credentials. Cached reports and discovery results are labeled with their source and dates.

2. Why we use it

We use information to create and verify accounts, authenticate users, maintain sessions, deliver requested verification/reset emails, prevent abuse, resolve support requests, provide available controls, and meet applicable legal obligations. We do not sell personal information, display behavioral advertising, or use connected Google user data to train generalized AI models. This build includes no AI assistant or automated analysis of private social accounts.

Where data-protection law requires a legal basis, the basis depends on the feature and jurisdiction: providing services you request, your consent for optional connections, legitimate interests in proportionate security and support, and compliance with applicable legal obligations. You may contact us about the basis and rights applicable to your circumstances.

3. Google sign-in

Optional Google sign-in requests basic identity scopes: your Google account identifier, name/profile information, and email address/verification information. It does not request Gmail, Google Drive, Calendar, YouTube Analytics, or permission to post on your behalf. The identity response is used to authenticate the Figtree account. The server verifies Google’s signed identity response during the short-lived token exchange. It does not retain that exchange as a social-account connection.

Your Google password stays with Google. See the Google Privacy Policy and manage app access through Google Account connections. Removing Google authorization does not itself delete an independent Figtree account; use Figtree’s deletion controls or contact us.

Figtree’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Administrative status alone is not authorization to inspect Google user data.

4. Optional platform connections

YouTube is optional and separate from basic Google sign-in. After you review and authorize the connection, Figtree requests youtube.readonly and yt-analytics.readonly. These read-only permissions support channel information and available reports: subscribers, lifetime views, video count, daily views, likes, comments, shares, watch time, and subscribers gained/lost. We do not request upload, channel-editing, or revenue permissions. A missing Analytics permission or unavailable report leaves those values unavailable rather than inventing statistics.

Encrypted access and refresh tokens allow requested refreshes without entering your Google password into Figtree. Saved statistics load without contacting Google on every page view. Refresh is requested from your account and limited to once per 15 minutes. Reports use YouTube’s Pacific reporting dates and may be delayed; the displayed date range ends on the last day returned. Channel subscriber counts may be rounded or hidden.

The optional connection choice “allow the owner Admin to view my YouTube reports” is off by default. If you enable it, the owner Admin can view saved reports through an identified temporary member session for management/support. You can withdraw that choice from Social accounts immediately. Without it, those reports are omitted from Admin member views and exports. An Admin member session cannot authorize, refresh, disconnect, or change sharing for your channel.

Multiple channels can be connected independently. Each has its own reports, refresh time, sharing choice, and removal control. Adding another channel does not replace an existing one. Combined subscribers count subscriptions across channels, not unique people; combined period metrics use a common report window.

Remove channel & delete data removes that channel’s saved connection, reports, and tokens from Figtree. When other channels remain connected, removal does not revoke a potentially shared Google grant, so those connections can continue. Removing the final channel or deleting the Figtree account attempts to revoke the remaining YouTube grants. If revocation cannot be confirmed, you can also remove Figtree through Google Account connections. This does not delete your YouTube channel or videos. Account deletion also removes the connection. If Google reports revoked/expired authorization during refresh, the saved tokens and reports are cleared and reconnection is required.

Instagram professional accounts can authorize basic identity and supported follower/following/media counts. Direct Instagram Login uses instagram_business_basic; Unified Login uses Meta Facebook Login for Business with instagram_basic and a configured system-user grant. The selected Meta configuration may request additional ads, comments, messaging or publishing permissions, as displayed by Meta; Figtree only calls read endpoints for account identity/counts and token validation. Facebook Pages authorization uses pages_show_list and pages_read_engagement, returns the Pages you manage and their Page access credentials, and reads identity and available follower/like counts. Personal Facebook profiles, private posts and messages are not collected. Meta grants can cover multiple selected assets, each saved as a separate account. TikTok uses user.info.basic, user.info.profile and user.info.stats for identity and available account counts. X uses users.read, tweet.read and offline.access for identity, public account metrics and refresh access. Twitch reads identity, available follower total and current live-stream state without email/chat permissions or follower identities. Snapchat links an authorized Public Profile identity through snapchat-profile-api after Snap allowlisting; this release does not collect private audience insights. SoundCloud reads identity and up to 200 returned uploaded tracks with available play/like counts. Its provider authorization may describe broader access, but Figtree does not use publishing or editing endpoints. Spotify user-read-private links a user profile; we do not retain listening history, email or country from that response. Apple Music does not have an OAuth listening connection in this release. Missing provider values remain unavailable. Current snapshots are not date-range reports. All provider tokens are encrypted on the server and excluded from browser responses and exports. Each provider/account has separate refresh, removal and optional owner-Admin sharing, off by default. Admin member sessions see only shared accounts and cannot mutate connections. Statistics refresh on request, at most once per 15 minutes per account. Twitch tokens are validated hourly and may be renewed in the background; this does not collect new profile statistics. Disconnect deletes local data and attempts provider revocation when supported and no other account shares that provider connection. Where revocation is unavailable or not confirmed, remove the grant in the provider’s app-access settings too.

Spotify and Apple Music artist URLs and normalized music-report CSV rows are member-provided records. We retain the artist label/URL, track ID/title, reporting dates, stream/play counts and optional listener counts you import. Artist ownership and report origin are not independently verified. A Spotify listener connection does not unlock Spotify for Artists analytics. Imports and SoundCloud snapshots are not proof of royalties or payouts. Import only reports you are authorized to use.

5. Managers, organizations, and OMNII

When you choose Continue with OMNII, OMNII supplies your member ID, name, and email to Figtree over a server connection to sign you in or link your account. Figtree approval is still required. Existing Figtree accounts must be signed into first before linking. OMNII and Figtree retain separate account sessions; signing out of one does not automatically sign out of the other.

A linked account can use its OMNII profile picture in Figtree. The image is requested through authenticated server endpoints, without making the underlying storage public. You can turn picture sync off in Figtree Settings.

Management sharing starts off and is selected separately for each connected provider account. Selecting an account permits its retained reports to appear in OMNII for you, assigned managers, and organization Admins, with approved detailed reports available in Figtree. OMNII receives a summary: supported totals, top countries, public-video view rankings, and recent public uploads when supplied by the provider. Figtree may also display supported age/gender aggregates and content reports. Unavailable fields are labeled. OMNII does not receive provider OAuth credentials. Assignment and active membership are checked when reports are requested.

Change these selections or unlink OMNII in Figtree Settings to stop future sharing. Figtree checks active OMNII membership for sessions issued through OMNII; independently approved Google/password Figtree access is managed separately. Removing a link does not delete either product’s account or your social accounts. It does not erase copies someone previously downloaded. The separate optional owner-Admin member-session sharing choice remains independent.

This connection does not authorize access to OMNII messages, journals, email, private documents, or unrelated records. Profile sync flows from OMNII to Figtree; analytics flow from Figtree to the approved OMNII viewers.

6. The future Chrome extension

The extension is deferred until after the website. This build does not install an extension or collect browser-tab contents, browsing history, or extension telemetry. Before an extension is released, its permission request, store disclosures, and this Policy will explain its actual behavior. The intended purpose is a quick authorized summary and a link to the full Figtree dashboard.

7. Who can receive information

• Cloudflare: website/Worker hosting, D1 account records, security infrastructure, and operational processing where configured.
• Authorized platforms: the platform you choose receives authorization and API requests needed to link and refresh its account. Provider terms and privacy policies apply to those requests.
• Google: optional Google identity authorization and Google Fonts requests made by the page. Font delivery can involve your IP address and request information. Google applies its own policies to those services.
• The configured transactional-email provider: recipient address and the verification or reset email needed for your request. This package supports Resend when configured; Resend’s Privacy Policy describes its own processing. Email/password registration should not be enabled without a working sender.
• Authorized operational personnel: limited information necessary for support, security, account administration, or a legal obligation. Access to connected accounts and music reports through an Admin member session additionally requires the member’s explicit sharing choice.
• Other recipients where legally necessary: to comply with valid legal process, protect lawful rights and safety, or investigate abuse, subject to applicable platform-data restrictions.

There is no payment processor in this release. External links take you to services with their own terms and privacy practices. We do not represent their activities as controlled entirely by Figtree.

8. Cookies and local information

An essential HttpOnly session cookie keeps you signed in for up to seven days unless you sign out, delete your account, or access is revoked sooner. A short-lived OAuth state cookie helps protect Google sign-in. Verification and reset tokens are temporary credentials; do not share their links. Pages and API responses handling private account information are configured not to be publicly cached.

The current website does not use advertising cookies or third-party behavioral analytics. Google Fonts and Google sign-in can make third-party network requests. Your browser may retain normal page/cache information under its own settings. Clearing cookies can sign you out.

9. Retention and deletion

Active account profile and eligibility/acceptance records are retained while needed to provide the account. YouTube OAuth state expires after ten minutes. Cached YouTube channel/report data is hidden once its last successful refresh is older than 30 days, and scheduled cleanup deletes that cached data. Encrypted refresh tokens remain only to support the active connection until disconnection, account deletion, or detected revocation. Other OAuth profile/statistics snapshots follow the same 30-day cache limit. Artist links and imported music reports remain until you clear reports, remove their account link, or delete your Figtree account. Twitch token validation/renewal runs hourly when configured; statistics are not polled. Ordinary sessions expire after up to seven days; Admin-initiated member sessions expire after up to 30 minutes and require the initiating Admin session to remain valid; OAuth state expires after ten minutes, verification/reset tokens after one hour, and abuse-control buckets after their short time window. Scheduled cleanup removes expired records when enabled; expiration is checked before a record can authorize access even if cleanup has not yet run.

Access-change audit records identify the acting Admin, target email, action (including Admin-initiated member login/logout), and time. Scheduled cleanup removes audit records older than 90 days. Approval entries, including Removed entries, can remain after account deletion to manage access and prevent an old approval from restoring access. Contact us to request correction, deletion, or a copy of these access records; any necessary retained restriction will be limited to its access-control purpose.

The export control returns your available profile and account metadata without password-derived values, session secrets, or private security credentials. Account deletion removes your active Figtree account and associated session/verification records. It does not delete a Google, social-platform, or OMNII account. The account export includes the currently retained YouTube channel/report data without tokens. Exports also include retained permitted platform snapshots and imported reports without credentials. An Admin member export omits each account unless you enabled its owner-Admin sharing.

Limited provider logs, technical backups, support correspondence, or records required for a specific legal/security purpose may be handled separately. They should be retained only as needed for that purpose; this is not permission to retain everything indefinitely. We do not promise that every provider backup or log disappears instantly.

10. Security and processing locations

The implementation uses encrypted web connections, server-side authentication, salted password derivation, hashed session tokens, expiry checks, and same-origin checks for account changes. No system can guarantee complete security. Figtree is not represented as end-to-end encrypted or as holding a certification it has not obtained.

Cloud and email providers may process information in countries other than your own. We do not promise storage in one specific country. Applicable legal requirements and provider arrangements govern relevant processing.

11. Your choices and rights

Approved members can choose an available sign-in method, sign out, export supported account information, and use supported account-deletion controls. You may also contact us to request access, correction, deletion, a copy, or other rights available under applicable law. We will verify a request as reasonably necessary without asking for your password and respond within applicable legal time limits.

Depending on where you live, you may have rights to object, restrict processing, withdraw consent, or complain to the relevant supervisory authority. Removing a permission can make its related feature unavailable; it does not automatically undo processing already lawfully completed.

12. Minors

Figtree is not intended for children under 13, and email/password enrollment includes an age/eligibility confirmation rather than a full birth date. Google sign-in does not collect a separate Figtree age confirmation. Users must meet any higher local minimum age and have parent/guardian involvement where required. If you believe an ineligible child supplied information, contact us so we can investigate, restrict access, and delete information where required. A management relationship does not remove protections provided by law.

13. Changes and contact

Updates will display a revised version and date. Material changes will receive an appropriate notice, and permission will be obtained where required before introducing a materially different purpose or a new optional integration.

Omniant — a division of Gio Celenza MGMT
Figtree privacy, deletion, and support requests: management@giocelenzamgmt.com
Website: figtree.omniant.org