← BrightBlockPrivacy storybook

Privacy Policy

The details stay as clear as the plan.

Open each paper flap to see what BrightBlock stores, what it leaves untouched, and which controls remain with you.

OPEN THE INDEX

Every privacy detail, in reading order.

  1. Policy scope
  2. Planning marks
  3. Search activity
  4. Bundled cards and images
  5. Accounts and profiles
  6. Network connections
  7. Android permissions
  8. Personal and sensitive information
  9. Device sensors and address books
  10. Analytics and advertising
  11. Purchases and payments
  12. Sharing, sale, and disclosure
  13. Local storage
  14. Retention and deletion
  15. Backup and device transfer
  16. Security boundaries
  17. Children and family use
  18. Policy changes and questions

CHAPTER 1

The planning space

BrightBlock privacy illustration for Policy scope

01

Policy scope

This policy describes the BrightBlock Android app.

It covers the planning marks, preferences, bundled content, and device behavior of BrightBlock version 1.0.0. It does not describe a separate website account, donation service, application process, or organization database.

BrightBlock privacy illustration for Planning marks

02

Planning marks

BrightBlock remembers the choices that make the planning flow useful.

The app can save which cards you mark Hold or Act Next, the card identifiers in your Stack, the preparation checks in Round, and the Reduced Motion preference. Hold and Act Next are mutually exclusive for the same card.

BrightBlock privacy illustration for Search activity

03

Search activity

Search filters the built-in card catalog while you use Sparks.

The words entered in the Sparks search field are used to match card titles and planning text on the screen. BrightBlock does not write that search phrase into its saved planning preferences.

CHAPTER 2

Built-in content

BrightBlock privacy illustration for Bundled cards and images

04

Bundled cards and images

The illustrated planning library is packaged with the app.

Card text, family information, and illustrations are read from resources included in the installed application. Opening a card or image does not request that content from a remote content service.

BrightBlock privacy illustration for Accounts and profiles

05

Accounts and profiles

BrightBlock has no sign-in or account system.

The app does not ask for a username, password, profile, membership identifier, or social sign-in. Saved planning marks belong to the local Android app installation rather than an online BrightBlock identity.

BrightBlock privacy illustration for Network connections

06

Network connections

The Android app does not request Internet access.

BrightBlock does not include the Android Internet permission and its planning features do not make network requests. The app has no remote BrightBlock server, synchronization service, or cloud content feed.

CHAPTER 3

Permissions

BrightBlock privacy illustration for Android permissions

07

Android permissions

The app manifest requests no runtime or special permissions.

BrightBlock does not ask Android for access to contacts, precise or approximate location, camera, microphone, photos, media, nearby devices, notifications, calendar, phone, SMS, or health information.

BrightBlock privacy illustration for Personal and sensitive information

08

Personal and sensitive information

The planning flow does not provide fields for personal records.

Cards and check-ins are structured choices, not free-form forms for names, email addresses, phone numbers, medical details, financial details, eligibility records, or identifying case notes. Use verified external channels when a real project requires responsible communication.

BrightBlock privacy illustration for Device sensors and address books

09

Device sensors and address books

BrightBlock does not read from device sensors or personal directories.

There is no feature for taking a photo, recording audio, reading contacts, tracking location, scanning nearby devices, or importing a calendar. The app does not upload media or address-book information.

CHAPTER 4

Third parties

BrightBlock privacy illustration for Analytics and advertising

10

Analytics and advertising

No analytics, attribution, advertising, or crash-reporting SDK is included.

BrightBlock does not create advertising identifiers, marketing profiles, engagement events, or third-party analytics records. The app does not display advertisements or personalized promotions.

BrightBlock privacy illustration for Purchases and payments

11

Purchases and payments

BrightBlock has no billing or payment feature.

The app does not contain subscriptions, in-app products, payment forms, donation processing, grant disbursement, or a wallet. It does not collect payment-card or bank information.

BrightBlock privacy illustration for Sharing, sale, and disclosure

12

Sharing, sale, and disclosure

Saved planning marks are not sent to the developer or another company.

Because BrightBlock has no server connection, analytics SDK, advertising SDK, or account system, it does not sell, rent, or transmit the app’s saved planning marks to third parties.

CHAPTER 5

Your controls

BrightBlock privacy illustration for Local storage

13

Local storage

Planning marks are stored in Android app preferences on the device.

BrightBlock uses private application preferences for Hold, Act Next, Stack, Round, and Reduced Motion. The operating system controls the app’s private storage boundary and device-level access.

BrightBlock privacy illustration for Retention and deletion

14

Retention and deletion

Saved marks remain until you clear them or remove the app data.

The Clear planning marks control in Quilt removes Hold, Act Next, Stack, and Round choices while keeping the Reduced Motion preference. Android’s Clear storage control or uninstalling BrightBlock removes the app preference file, including that remaining preference.

BrightBlock privacy illustration for Backup and device transfer

15

Backup and device transfer

BrightBlock excludes its preference data from cloud backup and device transfer.

The application data-extraction rules exclude the shared-preference directory from Android cloud backup and device-to-device transfer. A new installation therefore begins without the planning marks from another installation.

CHAPTER 6

Care & updates

BrightBlock privacy illustration for Security boundaries

16

Security boundaries

The app minimizes exposure by keeping its saved state small and local.

BrightBlock relies on Android application storage protections and does not transmit planning marks. No device or software can be guaranteed completely secure, so device lock, system updates, and control of physical access remain important.

BrightBlock privacy illustration for Children and family use

17

Children and family use

BrightBlock is a general planning tool rather than a child account service.

The app does not create profiles or ask for personal details from children. When a child participates in a real community activity, a responsible adult should guide the activity, follow current safeguarding requirements, and keep identifying information out of planning marks.

BrightBlock privacy illustration for Policy changes and questions

18

Policy changes and questions

This policy should change when the shipped app behavior changes.

The current policy is dated September 2, 2026. If BrightBlock later adds a permission, connection, account, SDK, or new storage behavior, the policy and store disclosures should be updated before that version is released. Privacy questions can use the developer contact shown on the app’s store listing.