Local work.
Clear boundaries.

FLIPFOLIO is a drawing and short-animation studio delivered as a browser extension. This policy describes version 1.0.0 of the packaged application: its New Tab studio, toolbar launcher, local project workspace, file import and export tools, and this bundled privacy page. It describes the application code, not every activity performed by your browser or operating system.

The publisher identified in the extension’s Chrome Web Store listing distributes the extension. The application does not create an account with that publisher and does not connect to a publisher-operated project server. Your drawings are processed on your device rather than submitted for online rendering or review.

This policy distinguishes information processed locally from information transmitted to someone else. A brush stroke, an imported image and a project name are still information handled by the application, even though this version does not send that information to the publisher.

Your creative workspace stays in the browser profile where you use FLIPFOLIO, subject to the browser’s storage availability and your own backup choices. The extension contains no analytics service, advertising integration, remote drawing service, account registration, cloud synchronization or automatic upload feature.

When local storage cannot be opened or a save fails, the interface shows a warning. A drawing that exists only in the open tab is not a confirmed persistent save. Export an editable project before closing that tab, clearing browser data or changing devices.

Choosing to download or share a file is different from the extension transmitting it automatically. Exported files can contain the artwork and names you entered. You decide where those files are kept and whether another person or service receives them.

FLIPFOLIO declares a New Tab override in its manifest. Opening a new tab therefore opens the packaged studio instead of the browser’s previous New Tab experience while this override is active. The toolbar launcher also offers a link to open the same studio in a separate tab.

This replacement is part of the extension’s single creative purpose. It is not a request to inspect the page you were viewing before opening the tab. The code does not examine your previous page, search terms, browser history, bookmarks, top sites, open-tab inventory or browsing habits.

To restore another New Tab experience, disable or remove FLIPFOLIO in the browser’s extension manager, or use the browser’s available controls for competing New Tab extensions. The browser controls which installed override is active. Disabling an extension and erasing its creative workspace are separate actions.

A project contains its name, internal identifier, 960 by 640 canvas settings, paper color, frame count, playback rate and loop range. Each layer contains a name, visibility, lock setting, opacity, drawing references and any motion keyframes. Keyframes describe position, rotation, scale, alpha and interpolation choices.

Drawing records contain the marks needed to reproduce the artwork: tool type, color, stroke width, fill choice and coordinates. Imported raster images are stored as embedded image data after local decoding and canvas rendering. The application uses these records to paint the canvas, create thumbnails and generate exports.

You may put personal or sensitive content in a drawing, image or layer name. The application cannot determine whether an artwork is confidential. It does not analyze subject matter, infer interests, recognize faces or classify your images, and it does not send them to an AI service.

The production manifest does not request browser API permissions or host permissions. There are no content scripts injected into other websites and no background service worker in this product. The application does not request access to cookies, passwords, browsing history, tabs data, location, microphones, cameras or contacts.

File import uses a standard user-initiated file picker. Selecting one file does not grant a general ability to search your disk or browse neighboring folders. The extension does not scan a downloads directory, monitor file changes or read files merely because they exist on your computer.

Canvas input is used to draw inside the studio. Keyboard shortcuts apply while you interact with the application; the extension is not a system-wide keylogger. There is no clipboard-reading integration, notification permission, payment integration or identity provider in this version.

When available, IndexedDB stores the creative workspace in a database named flipfolio-v1. The workspace includes up to twelve projects and identifies the project to reopen. A browser-managed transaction writes a complete workspace record together with a revision number; no corresponding copy is maintained on a publisher server.

Changes are scheduled for local saving after a short delay. The interface distinguishes a completed save from unsaved or memory-only work. Delayed writes, interrupted transactions, quota limits, device failures or browser restrictions can prevent a recent edit from being retained. The save indicator is more useful than assuming that every visible stroke has already reached disk.

Internal identifiers and revision numbers organize records and prevent stale updates. They are not advertising identifiers and are not transmitted for cross-site recognition. FLIPFOLIO does not use cookies or localStorage to maintain an online session, and it does not use browser-account synchronization for its project database.

Because every new tab can open the studio, several instances may exist at once. The application uses the Web Locks API to allow one editing tab for the product workspace. Other tabs show a read-only state rather than silently competing to save different copies of the same projects.

After the editing tab closes, another tab can retry acquiring the lock and reload the current workspace. If the browser cannot provide a safe editing lock while persistent storage is available, editing is disabled rather than treated as coordinated. A revision check inside the write transaction provides an additional stale-record safeguard.

A lock coordinates browser tabs locally; it is not a login, network session or collaboration service. Memory-only fallback work is confined to that tab and is not synchronized with another instance. Export that work before changing tabs when the interface cannot confirm persistence.

Undo and redo history, the current tool, pointer gestures, temporary selections, onion-skin display, canvas zoom and open panels are held in memory for the active page. They are used to make editing responsive. This version does not promise to restore every session-only control after the tab closes.

Undo keeps a bounded number of document states subject to a memory budget. It is a convenience for recent editing, not a permanent backup or an audit log. A downloaded editable project contains the document, not the full undo stack or a recording of every pointer and keyboard event.

Thumbnail surfaces and rendering caches are produced from project content. They are not screenshots of other tabs. Closing a page releases its active JavaScript environment, although the browser and operating system decide when memory and temporary resources are actually reclaimed.

The image picker accepts PNG, JPEG and WebP files within the application’s size limits. The browser decodes the selected file locally. The application fits its pixels to the project canvas, renders them into a new canvas and embeds a PNG representation as a drawing element.

The project does not intentionally retain the source file’s original filename, folder path or a separate EXIF metadata record. Re-rendering is not a guarantee that the visible image is anonymous: written names, faces, document text, addresses or other identifying details can remain plainly visible in the pixels.

Image URLs from the web are not accepted by this import feature. A selected image is not uploaded for resizing, background removal, moderation or recognition. An invalid, unsupported, oversized or undecodable image is rejected with feedback rather than fetched from a substitute online source.

An editable .flipfolio file contains the project’s schema version, name, layers, drawings, embedded images, frame arrangement and motion data. Import validates these fields and limits before adding a separate project identifier, so the imported copy does not silently replace the project that was already open.

The file contains one project, not the entire twelve-project workspace. Export each important project separately. Project files are readable JSON and are not password-protected or encrypted by FLIPFOLIO. Anyone who receives a file can inspect its names and recreate its included artwork.

Import failures do not deliberately erase the current drawing. Validation is intended to reject unsupported structures and oversized content; it is not a malware-scanning service and cannot guarantee that every file on your computer is trustworthy. Only open backups from sources you choose to trust.

PNG export renders the current visible composition at the project canvas size. GIF export renders the selected loop range at 480 by 320 using a fixed 256-color palette. Sprite-sheet export renders all timeline frames at 240 by 160 into a PNG and requests a separate JSON file describing their positions and playback rate.

These files flatten the visible artwork rather than preserving editing history. Hidden layers are not painted into a flattened image, but they remain in an editable project backup. Check the chosen export format before sharing a file that contains material you intended to keep private.

Export processing happens on the device. GIF encoding can use a packaged worker script; the worker receives pixel buffers inside the browser, not through a remote endpoint. Export creates temporary Blob URLs for browser download handling. Those URLs are revoked later, while downloaded copies remain wherever your browser saves them.

The application contains no fetch, XMLHttpRequest, WebSocket, beacon, analytics endpoint or remote asset dependency. Its scripts, styles, icons, examples and worker code are packaged with the extension. The content security policy restricts executable code to local extension resources and blocks application network connections.

No remote font, image generation endpoint, crash-report collector or video-encoding server is used by the studio. Processing a complex drawing does not trigger an online fallback. Failure messages are shown locally instead of transmitting the project to diagnose or complete an operation.

Chrome Web Store installation, browser-managed update checks and any website you deliberately open are separate activities controlled by the browser or the destination. If the publisher hosts this HTML policy on a website, that website’s hosting infrastructure may receive ordinary page-request information independently of the offline studio.

This build does not record usage analytics for the publisher. It does not count your drawing sessions on a server, create an advertising profile, sell artwork, share project content for marketing, embed advertisements or include an external telemetry SDK.

The browser supplies Canvas, IndexedDB, Web Locks, file decoding and download services. Those platform facilities are not evidence that the publisher receives the content processed through them. Your browser vendor’s own diagnostics, account settings and policies apply separately from the extension’s behavior.

There is no third-party online processor selected by the application to store or transform your projects. A cloud-synced downloads folder, device backup program or service you use to share an export may nevertheless copy files under its own settings. FLIPFOLIO cannot control those independent systems.

Locally saved projects remain in the workspace until you delete them, erase the workspace, remove relevant browser data, or the browser otherwise removes the storage. There is no server-side retention timer because the application does not hold an online copy. Closing a tab is not the same as deleting an IndexedDB project.

The interface limits projects to 120 frames and eight layers, and applies additional limits to marks, points, embedded images and imported file sizes. Browser storage quota remains separate from these application limits. The extension does not request unlimitedStorage or promise infinite disk capacity.

Browser data cleanup, storage pressure, profile corruption, a device change or uninstalling can make previously local work unavailable. Keep backups outside the browser for important projects. The publisher cannot restore an artwork from an online account that does not exist.

The Projects dialog lets you remove an individual project after confirmation. Erase this workspace removes the stored workspace record and replaces the working view with a blank project. Later editing may create a new record for that blank project; it does not intentionally recreate the deleted creative content.

Deleting a layer or frame changes the current project and can remain recoverable in the open tab’s undo history. That editing action should not be treated as a secure deletion request. Removing a whole project or erasing the workspace is a separate data-management action.

The extension cannot remove exported files from your downloads directory, cloud drive, messages or another person’s device. Delete those copies separately. Browser-managed deletion is not a promise of forensic erasure from disk backups, caches or storage hardware.

Project import reconstructs expected data rather than evaluating file contents as JavaScript. Names are displayed as text, not executed as HTML. Numeric ranges, record counts and supported image formats are checked. The packaged extension contains no remote executable code, signing key, authentication secret or embedded account credential.

Local storage is not encrypted by this application. Someone with access to your unlocked browser profile, operating-system account, backups or exported files may be able to read your work. Use device access controls and appropriate protection for sensitive files outside the extension.

No software can guarantee uninterrupted saving or eliminate every security defect. The application’s limits reduce accidental resource exhaustion but are not a substitute for browser updates, a trusted device and backups. Do not use the studio as a secrets manager or assume that local-only automatically means confidential against other users of the device.

The application has no account-registration form, chat, public gallery or built-in mechanism for asking a child to submit personal information to the publisher. It does not intentionally collect ages, school names, parent contact details or behavioral profiles through the studio.

Children can still draw identifying material or import a personal image. A parent, guardian or supervising adult should guide what is saved and shared, particularly on a shared computer. Downloading an artwork and sending it through another application is outside the studio’s local-only boundary.

FLIPFOLIO is not a child-monitoring or parental-consent system. It does not distinguish family members using the same browser profile. A shared profile can expose one person’s projects to another person with access to that profile.

You can choose not to import images, keep a project local, export a portable copy, delete individual projects, erase the workspace or disable the extension. Drawing tools do not require an online identity. There is no hidden setting that must be disabled to stop an analytics upload.

For access to locally saved content, use the studio and its editable export feature. For deletion, use the local controls or relevant browser data controls. The publisher cannot locate a project on your device by email address, because the application does not upload a project directory tied to an email account.

Where applicable privacy rights concern information you separately provide to the publisher, such as a support message, contact the publisher through the store listing. Do not send a full project merely to demonstrate a problem when a short description or a non-sensitive example would be enough.

This policy is dated 6 September 2026 and describes the version named at the top of the page. A future release may change behavior. Material changes such as introducing an online service, a new permission or a different data flow should be reflected in an updated policy and product disclosures.

The application itself does not download a live policy or remote configuration at startup. The bundled policy travels with the installed extension package. A publicly hosted copy may be maintained by the publisher for store-review and user-reference purposes.

Continuing to use an older installed version does not cause it to acquire undeclared online capabilities from this document. Review the policy supplied with an updated version, the store listing and any browser permission prompt before deciding whether to use that release.

Use the developer contact or support channel displayed on the FLIPFOLIO Chrome Web Store listing from which you installed the extension. Identify the product as FLIPFOLIO and include version 1.0.0 when describing a privacy question about this build. There is no in-application support chat or automatic support-file upload.

A useful report can describe your browser version, the operation you attempted and the exact visible error. Remove private details from screenshots or sample projects before sharing them. Never include passwords, browser-profile files, unrelated documents or confidential artwork unless you have independently decided that disclosure is appropriate.

An email, store review or support form that you choose to send is processed by the channel you use and by the publisher who receives it. That separate correspondence is not automatically generated by FLIPFOLIO. This offline policy file does not invent an email address or a publisher identity that has not been supplied in the product listing.