01
Scope of this policy
This policy describes the Creaseboard Android app, version 1.0.0, and the accompanying static landing and privacy pages. It covers the project details you choose to save, the app features that can open another installed app, and ordinary website requests made by your browser.
02
Projects you create
Creaseboard can keep the selected pattern, unit, scale, preparation checks, completed step, undo frame, variation note and saved project jackets. These values are created by your use of the app.
03
Local storage
Project state is stored in app-private SharedPreferences on the Android device. It is used to restore the workboard after backgrounding, force-stop or relaunch. Creaseboard does not implement a remote account or cloud database.
04
Preferences and display choices
Unit choice, scale, reduced-motion preference and other worktable settings can be saved with the project state so the next session opens in the arrangement you selected.
05
Undo and variations
An undo frame and branched project jackets record only the paper-project values needed to reverse or compare your recent choices. Creaseboard does not turn those values into a public activity history.
06
Source links
The Edge Drawer contains public reference links for paper-tool and paper-size context. A link opens only after your deliberate tap and asks another installed app, such as a browser, to handle the address. That external app and website apply their own privacy practices and may require a network connection.
07
External destinations
Once a reference link leaves Creaseboard, the selected browser or other receiving app controls its own connection, storage and privacy behavior. Creaseboard does not receive the contents you view or enter on those external destinations.
08
Accounts and profiles
The app does not provide sign-in, membership profiles, public comments, leaderboards or a remote account area. Paper-project notes remain part of the local project state described in this policy.
09
Clearing your desk
The Clear the local desk control removes project progress, preparation checks, undo frames, notes, saved jackets and preferences from Creaseboard on that device. Android settings can also clear app data, and uninstalling removes the app-managed local state.
10
Device backup and transfer
Android cloud backup and device-to-device transfer are disabled for Creaseboard. A device or operating system may still keep data outside the app through mechanisms controlled by the device owner; Creaseboard does not claim control over independent device backups or screenshots.
11
Audience and tools
Creaseboard is designed for general paper-craft use. It does not knowingly request personal details from children. Cutting tools, scoring tools and materials should be selected and supervised by the person responsible for the physical activity.
12
Organization and contact
Creaseboard is prepared for the user-supplied release profile FRIENDS OF THE FILM LOUNGE. Privacy correspondence may be mailed to 1329 Pheasant Way, Park City, UT 84098-5533. This contact identifies the proposed release profile without claiming a public venue, screening program or third-party endorsement.
13
Permissions and device access
The signed app requests no Android runtime permission and does not declare the Internet permission. It does not request camera, microphone, precise location, contacts, nearby-device, notification, sensor or shared-storage access.
14
Export, sharing and system services
Creaseboard does not include a project export or in-app sharing service. If a platform link is opened, Android asks a compatible installed app to handle it; no paper-project record is attached by Creaseboard.
15
Third-party services
Version 1.0.0 does not bundle advertising, analytics, payment, authentication, crash-reporting, synchronization or remote-content SDKs. Android platform UI, drawing, JSON and app-private preferences support the core experience.
16
Retention
Saved project state remains until you edit it or use one of the deletion controls described above. Creaseboard does not set a remote retention period because it does not maintain a remote project database.
17
Static website requests
Opening these static pages causes a browser to request the page files and images from the chosen web host. The current site code contains no contact form or app-project upload. A future host may keep routine request logs under its own published terms.
18
Cookies and browser storage
The static landing and policy pages do not set application cookies, create a website account or add analytics and advertising trackers. Browser features, extensions or a future hosting provider may operate independently and should be evaluated under their own settings and notices.
