Privacy Policy

1. Overview

SunnySide is a Chrome extension that provides a self-contained gardening game inside the browser toolbar popup. Players can plant seeds, water and care for plots, improve soil, grow and harvest plants, earn and spend in-game coins, collect species, complete daily tasks, unlock gardening tools, use pollination and hybrid systems, and progress through multiple in-game days.

The extension is designed to work locally. Its core gameplay is calculated by JavaScript files packaged with the extension. The game does not require an account, remote login, online leaderboard, cloud-save account, advertising service, analytics platform, or developer-operated gameplay server.

2. Scope of this Privacy Policy

This policy applies to the SunnySide Chrome extension itself, including its popup interface, packaged game logic, local save data, built-in sound setting, garden simulation, collection and progression systems, journal and game log, and any other state used to continue the game.

This policy does not govern Google Chrome, the Chrome Web Store, your Google account, your operating system, browser synchronization provided by Google, security software, device backup software, or unrelated websites and applications. Those products may process information independently under their own privacy terms.

The policy is based on the behavior of SunnySide version 1.0.3. If a future release materially changes how information is handled—for example by adding an online account, server synchronization, analytics, website access, or new Chrome permissions—the policy should be updated to describe those changes.

3. Privacy design principles

SunnySide is built around a data-minimization approach. The game should only handle information that is needed to operate its own local game state.

• Local-first: the current garden and progression are saved in the extension's own local browser storage.
• No account: SunnySide does not ask users to register, create a profile, or sign in.
• No website access: the current manifest does not request access to tabs, web pages, browsing history, cookies, or page content.
• No analytics: there is no analytics SDK or automatic gameplay telemetry reporting.
• No advertising: no advertising network, retargeting service, or behavioral advertising component is included.
• No developer backend: the current game does not need a developer-operated server to save or process gameplay.
• No remote executable code: JavaScript, CSS, HTML, and icons required for the game are packaged with the extension.

4. Information collected by the developer

The current version of SunnySide does not collect personal information or gameplay data for the developer. The developer does not receive a copy of the player's garden save through normal extension operation.

SunnySide does not intentionally collect names, postal addresses, phone numbers, email addresses, Chrome account identifiers, precise or approximate location, passwords, authentication tokens, payment card information, banking information, medical information, biometric information, private communications, browser history, search history, or website content.

The extension also does not automatically send the developer information such as how often the popup is opened, which seeds are planted, how many coins are earned, what day the garden reaches, which upgrades are purchased, which journal entries appear, or how long a user plays.

If a user independently contacts the developer by email, that email is separate from the automated game behavior. Direct correspondence is discussed later in this policy.

5. Data-category disclosure

6. Local game data

SunnySide needs to remember the player's garden between popup sessions. It does this with the ordinary browser localStorage available to the extension's own origin. The current save key is:

sunnySideStateV1

This key is an implementation detail used to retrieve the player's local save. It is not an advertising identifier, account identifier, device fingerprint, or cross-site tracking identifier.

Information included in the local save

The serialized game state can contain the following categories of fictional game information:

• save-format version and a locally generated random seed used by game systems;
• current in-game day;
• coin balance, garden level, and experience points;
• the currently selected seed type;
• whether game sound is enabled;
• current weather, forecast, and sunset display;
• seed inventory for the plant species available in the game;
• the state of each garden plot, including plant species, growth, water, soil condition, dry-day count, planting day, generation value, orientation-related game state, and other plot flags;
• plant collection progress;
• hybrid discoveries;
• purchased or unlocked gardening tools and upgrades;
• rain-barrel and other progression values;
• current daily quest, quest progress, and claim state;
• recent garden log entries;
• journal or observation entries produced by game progression;
• statistics such as plants planted, watering actions, harvests, care actions, purchases, scans, days completed, hybrids created, and coins earned;
• internal progression and event flags required to prevent events from repeating incorrectly and to preserve the order of game systems;
• the currently selected in-game tab or plot where necessary for the interface.

These values describe the fictional SunnySide garden. They are not derived from the user's real garden, home, physical environment, financial account, browsing history, or geographic location.

Random seed

A numeric seed is created locally when a new garden begins. It is used to support deterministic or semi-deterministic game behavior such as day-level variation. The seed is part of the game simulation and is not used to identify a user outside SunnySide.

Game log and observations

SunnySide may keep a limited local list of garden log entries and observations so the player can review events that have occurred in the current garden. These entries are generated by the game. They are not a record of websites visited, browser actions outside the popup, operating-system events, or private communications.

Internal event flags

The save may include internal flags that indicate whether specific game events have occurred or whether certain game systems have been unlocked. These flags are necessary to maintain coherent progression when the popup closes and later reopens. They are not used for profiling, advertising, or external analytics.

7. Storage, persistence, and retention

The local SunnySide save is retained in the Chrome browser profile so the garden can continue after the popup is closed. The developer does not control a remote retention period because the save is not held in a developer database.

The save may remain until one of the following occurs:

• the game overwrites the save as normal progress continues;
• the user uses SunnySide's “Start a new garden” or equivalent reset action;
• the user clears extension/site storage through browser tools;
• the browser profile is reset or removed;
• the extension is uninstalled and Chrome removes its associated local data;
• Chrome or an administrator otherwise clears extension-origin storage.

Exact retention behavior can depend on the Chrome version, browser profile settings, enterprise policies, device-management policies, browser backup behavior, or other software outside SunnySide.

SunnySide does not currently provide a developer-operated cloud-save service. If a local save is deleted, the developer ordinarily cannot restore it because the developer never received a copy.

8. Chrome permissions

SunnySide version 1.0.3 uses Manifest V3 and currently requests no Chrome extension permissions and no host permissions.

The manifest does not request access to tabs, activeTab, history, scripting, cookies, downloads, notifications, geolocation, or Chrome's extension storage permission.

The game can use ordinary browser features available inside its own popup, including DOM rendering, timers, Canvas/CSS rendering where applicable, localStorage, and browser audio APIs. Those capabilities do not give SunnySide access to arbitrary websites or unrelated browser data.

9. Website, tab, and browsing access

SunnySide is designed as a self-contained toolbar game. It does not need the page behind the popup in order to function.

The current version does not:

• read the URL of the active tab;
• read or modify web page text, images, forms, buttons, or DOM content;
• inject content scripts into sites;
• monitor browser tabs;
• read search history or browsing history;
• read cookies belonging to websites;
• read website localStorage or sessionStorage;
• observe what the user types into web pages;
• collect page titles or website navigation patterns.

The localStorage used for the garden save belongs to the extension's own origin and is separate from storage used by unrelated websites.

10. Network activity and remote services

The current SunnySide code does not use fetch, XMLHttpRequest, WebSocket, or a developer API for its core gameplay. The gardening simulation, weather system, progression, journal, economy, collection, and local save operate without a developer backend.

The package does not rely on remote JavaScript, external CSS, a remote font service, cloud rendering, online AI, social-login APIs, analytics endpoints, ad networks, or remote game assets.

Chrome itself may communicate with Google for browser updates, extension-store functions, Safe Browsing, account features, extension updates, or other Chrome services. Your operating system, security software, DNS provider, network administrator, or device-management software may also create network activity. Those activities are outside SunnySide's gameplay implementation and are not developer-operated SunnySide telemetry.

11. Sound and audio

SunnySide includes a sound preference and may generate simple in-game audio locally using browser audio capabilities. The sound setting is part of the local game state so the user's preference can persist.

SunnySide does not request microphone permission, does not record the microphone, does not capture system audio, and does not upload audio recordings.

Turning game sound on or off affects only the locally generated game experience.

12. Analytics, cookies, tracking, and advertising

Analytics

SunnySide does not currently include Google Analytics, Firebase Analytics, Mixpanel, Amplitude, Segment, PostHog, or another comparable analytics platform. The developer does not automatically receive statistics about session duration, retention, feature use, garden level, harvest frequency, or other gameplay behavior.

Crash reporting

The extension does not currently include a third-party crash-reporting SDK that automatically uploads stack traces or device information to the developer.

Advertising

SunnySide does not display third-party advertising. It does not include ad-network code, retargeting pixels, behavioral advertising SDKs, or an advertising auction.

Cookies

The extension does not request the Chrome cookies permission and does not use website cookies to operate the garden.

Fingerprinting

SunnySide is not designed to fingerprint the browser or device, correlate users across websites, or build a cross-context behavioral profile.

13. Sharing, disclosure, sale, and monetization of data

The developer does not sell, rent, license, trade, or share SunnySide gameplay data with advertisers, data brokers, analytics providers, social networks, AI providers, or marketing platforms because the current version does not collect the local game save for developer use.

There is no online leaderboard, multiplayer profile, public garden account, or social feed that automatically publishes the player's local garden state.

If a user voluntarily takes a screenshot, records the popup, copies information manually, or describes the garden on another service, that later sharing is controlled by the user and by the separate service used for sharing.

If the developer is legally required to respond to a valid legal request, the developer can only provide information actually possessed. The local SunnySide save described in this policy is not stored in a developer database.

14. Security and data minimization

SunnySide reduces privacy exposure by avoiding unnecessary data collection and broad browser permissions. The current architecture does not require a central account database, a gameplay telemetry server, or access to unrelated browsing data.

The extension's HTML, CSS, JavaScript, game-core module, and icon files are packaged locally with the extension. Avoiding remote executable code reduces reliance on external code that could change independently of the installed package.

No software can be guaranteed absolutely secure or error-free. Users should keep Chrome updated, use appropriate device security, and install the extension only from sources they trust. Anyone who has access to the same local browser profile or device may potentially gain access to locally stored browser data depending on device security.

15. Deleting or resetting local SunnySide data

SunnySide includes a garden reset workflow. The current implementation removes the sunnySideStateV1 save key when the user confirms starting a new garden, after which a new local game state is created.

Users may also manage or clear extension-origin data through Chrome's browser controls. The exact steps can vary by Chrome version and operating system.

Deleting the local save can permanently remove garden progress, including plant collection, upgrades, journal entries, statistics, and progression. Because SunnySide does not upload a cloud backup to the developer, the developer normally cannot recover deleted local progress.

Uninstalling the extension or deleting a browser profile can also affect local save data according to Chrome's own data-management behavior.

16. User rights and choices

Privacy laws in some jurisdictions provide rights such as access, correction, deletion, restriction, portability, or objection regarding personal information held by an organization.

Because SunnySide's game save remains local and is not transmitted to the developer, there is ordinarily no developer-held gameplay profile to access, correct, export, or delete.

Users can control the local game state by continuing the garden, resetting it, clearing browser storage, using a separate browser profile, or uninstalling the extension.

If a user has separately contacted the developer by email, they may contact the developer regarding information contained in that direct correspondence at tuytrung179227@gmail.com.

17. Children's privacy

SunnySide is a general entertainment game and does not create user accounts, request dates of birth, operate public profiles, provide user-to-user messaging, or build advertising profiles.

The game is not designed to solicit personal information from children or adults. If a parent, guardian, or other person believes personal information was sent directly to the developer outside the automated extension—for example through a support email—they may contact the developer using the address below.

18. International users and transfers

SunnySide can be used in different countries and regions. Its core save architecture does not require the player's garden state to be transferred to a developer server in another country because the save is kept in the browser's local extension storage.

If the user independently uses Chrome synchronization, device backup software, screenshots, cloud storage, or another service, those services may process information in other jurisdictions according to their own privacy practices. SunnySide does not control those separate services.

19. Third-party services and external code

The current SunnySide package does not integrate third-party analytics, advertising, authentication, social networking, cloud saving, AI, or remote game-content services.

It does not load externally hosted JavaScript or CSS for gameplay. All code required for the SunnySide experience is included in the installed extension package.

The Chrome Web Store and Chrome browser are third-party platforms used to distribute and run the extension. Their independent privacy practices are not controlled by SunnySide.

20. Automated game systems, randomization, and in-game decisions

SunnySide uses local rules and random or seeded calculations to determine fictional game behavior such as weather, growth variation, quests, progression events, pollination results, garden observations, and other game outcomes.

These automated calculations are entertainment mechanics. They are not decisions about employment, credit, housing, insurance, education, medical care, legal status, or eligibility for real-world services.

SunnySide does not send player behavior to a remote generative-AI service and does not use a remote AI system to profile the user. Game-generated text, observations, and events are produced by packaged game logic.

Fictional values such as coins, experience, seeds, soil quality, root measurements, weather, statistics, and collection status have no real-world financial or legal meaning.

21. Direct communications with the developer

If a user chooses to contact the developer by email, the email provider necessarily processes information required to deliver the message, such as the sender's email address, message content, and normal email-routing metadata. This happens because the user voluntarily sends a message outside the automated SunnySide game.

Information provided directly by email may be used to answer a question, investigate a bug, respond to a privacy request, or maintain necessary records relating to support or security.

Users should avoid sending passwords, payment-card information, government identifiers, medical records, or other sensitive information that is not necessary to explain an issue.

The developer does not use support correspondence to build advertising profiles or sell mailing lists.

22. Changes to this Privacy Policy

This Privacy Policy may be revised to improve clarity, reflect changes in SunnySide, respond to Chrome Web Store requirements, or address changes in applicable law.

The effective date at the top of this page identifies the current version of the policy.

If a future SunnySide update introduces materially different data handling—such as cloud saves, online accounts, analytics, advertising, website access, multiplayer services, external APIs, or new Chrome permissions—the privacy policy and relevant Chrome Web Store disclosures should be updated so that they accurately reflect the new behavior.