Privacy Policy — Google Flower

1. Introduction

Welcome to Google Flower AI—Google's dedicated collaborative canvas and filmmaking studio. We give independent directors, VFX artists, and writers the generative infrastructure required to take ideas from a blank page to a textured, cinematic reality. Whether you are staging complex camera movements through language or testing character consistency across multi-scene timelines, we recognize that your creative output requires absolute ownership and clear privacy boundaries.

We believe transparency is just as critical as the safety guardrails under our model's hood. This Privacy Policy lays out exactly how we process, protect, and respect your personal information, technical telemetry, and workspace assets when you interface with our platform (collectively, the "Services").

By logging into your workspace and accessing Google Flower AI, you agree to the practical workflows outlined in this document. If you do not feel comfortable with these data practices, please hold off on creating an account.

2. Information We Collect

Data Provided by You

Workspace Profile: When setting up your creator account, we request basics like your name, verified email address, a unique username, and secure credentials.
Creative Inputs & Prompts: We process the cinematic instructions, character details, script files, and structural outlines you feed into the workspace to generate footage and storyboards.
Project Metadata: Structural tracking information tied to the sequences you stitch, edit, and fine-tune inside our canvas timeline.
Direct Communication: Any explicit context you share when messaging our support staff, filing system bugs, or responding to community surveys.

Automated Platform Telemetry

Usage & Interaction: We evaluate how you move through the platform—tracking features utilized, timeline editing choices, active exporting trends, and rendering iterations to improve user flow.
Technical Infrastructure Log: Standards such as your IP address, browser architecture, operating system configuration, and approximate regional location data (limited strictly to the city or country tier).
Model Performance Data: Real-time processing logs, including rendering duration, execution failure rates, and hardware timeouts, helping us maintain stable cloud clusters.

Third-Party Platform Integrations

If you opt to log in via your main Google Account or connect external asset repositories for direct cloud importing, we capture subset profile data as permitted by those platforms and your personal authorization limits.

3. How We Use Your Information

Your telemetry and workspace inputs are applied to functional ecosystem operations:

To execute, optimize, and scale the Google Flower AI environment, translating complex cinematography parameters into responsive video outputs.
To customize the editor interface—saving your favorite lens configurations, aspect ratios, or custom style rules so they remain consistent across projects.
To unblock technical errors, resolve billing queries, and answer individual workflow inquiries through our help desks.
To actively guard against malicious system use, preventing deepfakes, bad actors, or security exploits from destabilizing cloud assets.
To refine generative mechanics, helping deep learning engineers upgrade temporal stability, lighting physics, and complex motion framing.
To share necessary service notifications, major core features, or fund updates (with direct opt-outs always accessible).
To enforce user terms and adhere to necessary legal data baselines.

4. How We Share Your Information

We have never sold, traded, or commercialized user data. Information access is confined entirely to these structural paths:

Operational Infrastructure Partners

We utilize trusted modern infrastructure services for foundational cloud compute cluster management, secure video rendering pipeline hosting, error diagnostics, and customer ticket sorting. These parties process data under strict, non-disclosure compliance agreements.

Legal Compliance & Protection

We will share specific logs only if legally obligated by a court order, explicit statute, or regulatory demand, or when necessary to protect the safety of our engineering staff and creator community.

Corporate Adjustments

Should Google Flower AI transition via an organizational spin-off, merger, or asset sale, existing profile assets will remain shielded under equivalent protective standards, with clear user alerts delivered ahead of time.

Explicit Creator Authorization

When you intentionally click to make an asset public, submit your timeline cut to the Creator Fund showcase, or share an integration link, we execute that action strictly at your command.

5. Cookies and Tracking

Our system depends on essential session variables to keep your timeline synced, preserve cookie authorization state across page switches, and retain custom workspace configurations. Performance analytics help us track UI latency. You can control cookie rules dynamically via your local browser preferences or our main settings dashboard.

6. Keeping Your Data Secure

We deploy resilient physical, administrative, and technological data defenses. All sensitive project files, model keys, and script text are protected using industry-standard encryption protocols both during network transfer and while resting on our cloud clusters. Because no connected tool is completely immune to security threats, we urge you to use strong account passwords and safeguard your active login tokens.

7. Your Rights and Choices

Depending on your geographic location and local data privacy frameworks (such as GDPR or CCPA), you can access specific control features:

Review, modify, or permanently wipe your account records.
Restrict or opt out of specific back-end telemetry recording or outreach updates.
Export a clean file copy of your raw profile and project assets.
Revoke previously granted data processing permissions at any point.

To file a request, simply drop our team a line via the information below. We handle inquiries within mandatory statutory timelines. Rest assured, you retain legal ownership over your final exported cinematic creations.

8. Younger Creators

Google Flower AI does not knowingly allow registration from children under 13 (or 16 in specific international jurisdictions). If we discover an active account belongs to a minor who has bypassed these parameters without parent validation, we will purge those profile records from our servers immediately.

9. Global Transfers

Because our platform routes operations across international data center nodes, your workspace assets may travel to and be stored on infrastructure outside your native territory—including the United States. We manage these transfers using approved standard contractual clauses to ensure uniform data protection.

10. Data Retention

We host your creative data only as long as your workspace profile remains open or as required to keep our systems secure. If you close your account, we clear your timeline models, text prompt lists, and drafts within standard operational cycles, keeping only what is required to comply with strict financial audit laws or open disputes.

11. Policy Changes

As we expand our toolkit with features like real-time foley generation and multi-track spatial editing, our data practices may adjust accordingly. We will post any text changes directly to this URL and bump the revised effective date at the top. Keeping your workspace profile active after an update confirms you are on board with the updated terms.

12. Contact Our Team

If you want to exercise your legal data rights, clear up a rule inside this document, or share feedback on our privacy framework, please get in touch:

Email: [email protected]

Address: Google Flower AI, Privacy Team, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

We take every inquiry seriously and will follow up with an answer as quickly as humanly possible.