Foldline
Privacy Specification

1. Scope

This privacy policy applies to Foldline version 1.0.0, including its packaged app page, background launcher, puzzle definitions, local progress state, icons, and interface assets. Foldline is designed as a finite local puzzle game rather than as a service that analyzes browsing or synchronizes gameplay to an account.

The policy describes what the actual extension code does. Foldline draws a paper-like canvas, accepts crease gestures, reflects marks mathematically, tracks undo history in memory, records a small completion list locally, and opens its own app page when the toolbar action is clicked. It does not need personal information to perform those tasks.

2. Product behavior

Each Foldline study starts with a predefined set of normalized two-dimensional points and a maximum number of folds. The user drags across the canvas to define a crease. After the line is drawn, the user clicks one side. Points on that side are reflected across the line using local geometry calculations. The puzzle is solved when the resulting points converge within the game's alignment tolerance.

The twelve studies included in version 1.0.0 are shipped directly in the extension's JavaScript. They include horizontal, vertical, diagonal, shifted, and two-fold arrangements. Foldline does not download new levels from a server and does not submit a solution to a server for validation.

Undo restores a previous point snapshot kept in memory for the current study. Reset reloads the current study's packaged starting points. Hint temporarily displays a known useful crease from the packaged level definition. Unfold Replay displays in-memory snapshots in reverse order after a completed solution. None of these features requires external storage or network access.

3. Information Foldline handles

Persistent progress

Foldline stores the index of the current study and a list of integer indices for studies the user has completed. These values allow the study selector and footer progress marks to remain consistent across sessions.

In-memory puzzle state

While a study is open, Foldline maintains the current point coordinates, crease endpoints, the chosen fold side, undo snapshots, temporary hint lines, and replay snapshots. This data is mathematical gameplay state. It disappears when the page is closed or reloaded except for the small completion record described above.

Pointer input

The game handles pointer coordinates over its own canvas when the user draws a crease or chooses a side. Coordinates are normalized relative to the Foldline canvas and used immediately for puzzle geometry. They are not recorded as a behavioral log, not associated with a website, and not sent elsewhere.

Information not requested

• No real name, username, profile, email address, phone number, or postal address is requested.
• No password, login cookie, authentication token, financial record, or payment method is requested.
• No location, camera, microphone, screen-capture, or sensor data is requested.
• No browser history, bookmark list, download list, tab URL, tab title, or webpage text is read.
• No files or documents from the user's computer are uploaded or parsed.
• No advertising identifier or cross-site identifier is created.

4. Storage and persistence

Foldline uses the standard localStorage area belonging to its own extension origin. In version 1.0.0 the storage key is foldline.v1. The stored JSON contains a current number and a done array of completed study indices.

The game does not store every crease a user has drawn across previous sessions. Failed attempts are not appended to an analytics record. Undo history is held only for the open page and is reset when a different study is loaded. The saved state is therefore a progress marker rather than a gameplay transcript.

Foldline does not request the Chrome storage permission because the built-in localStorage available to the extension page is sufficient for this small state. The product does not use chrome.storage.sync and has no custom cloud-save mechanism.

If stored JSON cannot be parsed, Foldline falls back to a valid default state rather than attempting to send the malformed data for remote repair. Completion values are treated as local indices, not as identity data.

5. Permissions

The production manifest declares "permissions": []. Foldline does not ask for the tabs, storage, history, bookmarks, downloads, notifications, clipboard, geolocation, or any other Chrome extension permission.

No host permissions are declared. Foldline has no <all_urls> access and no permission pattern for individual websites. No content script is registered. This means the game does not need permission to inject itself into pages the user visits.

The toolbar action uses a background service worker whose only responsibility is to create a browser tab pointing to Foldline's own packaged app.html. Chrome permits creation of that tab without granting the broad tabs permission. The worker does not read the active tab's URL, title, content, or other sensitive properties.

6. Webpage access and browsing data

Foldline operates in a dedicated chrome-extension:// page. The game canvas is not placed on top of arbitrary websites and the extension does not alter webpages. It does not watch navigation, search terms, shopping activity, social-media activity, form contents, or page structure.

The product's paper metaphor is purely local UI. A user may have other browser tabs open at the same time, but Foldline does not query Chrome for those tabs and does not combine puzzle progress with browsing behavior.

Because the core feature is a geometric puzzle, website access would not be relevant to the stated single purpose. The absence of host permissions is therefore part of the product architecture rather than merely a policy promise.

7. Network behavior

Foldline version 1.0.0 makes no application network request. Its production JavaScript contains no feature use of fetch, XMLHttpRequest, WebSocket, EventSource, or remote JavaScript imports. It does not contact a score server, level server, analytics server, advertising network, or crash-reporting endpoint.

All twelve level definitions are included in the extension package. Hints are derived from those packaged definitions. The game can therefore be played after installation without downloading puzzle content from Foldline infrastructure.

Interface fonts are selected from local system families and assets such as icons are packaged with the extension. There is no hosted font request that could disclose an IP address or gameplay page load to a font provider.

The Chrome browser or Chrome Web Store may independently perform browser-level update or distribution operations. Those platform operations are outside the Foldline application code and are governed by the platform's applicable policies.

8. Analytics, telemetry, ads, and monetization data

Foldline includes no analytics SDK and sends no custom telemetry. The developer does not receive per-user completion events, fold coordinates, number of failed attempts, hint use, session duration, level popularity, or replay usage from version 1.0.0.

The product contains no advertising SDK, behavioral ad targeting, sponsored puzzle feed, affiliate link instrumentation, or cross-site profiling code. Foldline does not sell or rent gameplay information because the extension does not collect a server-side gameplay dataset.

There is no user leaderboard and no score submission. The phrase “12 studies” refers only to the number of packaged puzzles; it is not an online challenge system.

9. Third parties

No third-party processor receives Foldline's local progress through the application. There is no external identity provider, database provider, analytics vendor, advertising provider, payment service, AI service, or remote content provider integrated into the game.

Chrome and the Chrome Web Store remain platform services used for browser execution and distribution. Information they handle about extension installation, browser operation, store access, or updates is controlled by their own systems. Foldline does not gain browsing-data access merely because it runs inside Chrome.

10. Retention

The current study index and completion list remain in localStorage until the user changes progress, clears the extension's local data, resets the relevant browser profile, or uninstalls the extension. Completing another study updates the same small progress object.

Undo snapshots, draft crease lines, hint lines, and replay snapshots are temporary. They are associated with the currently open page and are not written to the persistent progress object. Closing or reloading the page discards them.

Foldline has no server retention schedule for gameplay data because gameplay data is not uploaded to a Foldline server. The developer cannot remotely inspect or purge a local progress record that was never transmitted.

11. Deleting progress

Uninstalling Foldline and removing its local extension data deletes the game progress maintained by the extension in that browser profile. Browser environments that expose extension-origin storage controls may also allow the localStorage record to be cleared without uninstalling.

After the local record is removed, Foldline starts again with the first study as the current study and with no completed studies. There is no online account that must be contacted separately to reset the game.

A user does not need to submit identity documentation or disclose gameplay details to request deletion from a developer database because version 1.0.0 does not create such a database.

12. Security

Foldline follows a data-minimization approach: no host access, no declared Chrome permissions, no remote code, and no application network layer. This reduces the number of places where gameplay information could be exposed.

The saved progress is not sensitive credential material and is not encrypted by Foldline. It resides in browser-managed local storage. A person who already has access to the user's unlocked operating-system account or browser profile may be able to inspect that storage with local diagnostic tools.

Users should keep their browser and operating system updated and use normal device-access controls. Foldline's local-only architecture reduces remote data exposure but does not replace the security protections of the underlying device.

13. User choices and controls

The user decides when to open Foldline by clicking the toolbar action. Foldline does not replace the new-tab page, open itself on browser startup, inject banners into websites, or create background puzzle notifications.

Inside the game, the user chooses every crease and fold side. Undo and Reset change only the current local puzzle state. Hint briefly renders a packaged reference crease and then removes it. The Levels panel changes which packaged study is active.

After a solution, Unfold Replay displays earlier in-memory point snapshots in reverse. Next Study changes the current local index. These actions do not transmit an event to a remote service.

14. Children and personal information

Foldline is a general-audience logic puzzle. It does not provide accounts, public profiles, chat, social sharing, behavioral advertising, purchases, or features designed to solicit personal information from children.

Because the application does not collect a remote user record, it does not knowingly collect personal information from children through gameplay. The saved data is limited to anonymous local puzzle indices within the browser profile.

15. Policy updates

This policy may be updated when a future Foldline release changes privacy-relevant behavior. For example, adding cloud synchronization, downloadable levels, analytics, accounts, or new Chrome permissions would require a new explanation of what information is involved and why it is needed.

Minor editorial revisions may clarify existing statements without changing the product's data practices. Users evaluating the policy should consider the extension version identified at the top and bottom of the document. This text describes version 1.0.0.

16. Contact

Questions about Foldline's privacy behavior can be sent through the developer support contact associated with the Foldline Chrome Web Store listing. The listing support channel is used so the current developer contact can be maintained without embedding an unrelated or obsolete address in the static policy file.

A privacy or bug report does not need to contain browsing history or private documents. Foldline does not use those materials. Providing the extension version, browser version, study number, and a concise description of the observed behavior is normally enough to investigate an issue.