NOPECUBE Privacy Policy

Last updated: 29 September 2026 (draft)

Publisher: NOPECUBE · Contact: hello@nopecube.com
This policy: https://nopecube.com/privacy/

This policy explains how the NOPECUBE apps for Android, Wear OS, iPhone, iPad and Apple Watch handle information. NOPECUBE turns your choice to set a boundary (NOPE) or open again (OPEN) into a short ritual, and helps you close open loops yourself: something that keeps coming back, a request you are not ready to answer, or the end of a working day. You can use it offline, without an account.

Summary

Information stored on your device

The app stores:

On first launch, the first-boundary screen asks which moment is closest to yours, for example "Work doesn't end when my day does". Your answer is not saved as an answer. It only selects a door and, for a timed door, saves an if–then intention if you confirm one. From 1.1, the first screen also lets you try the slide once, to NOPE and back to OPEN. The try is not saved: it does not change your choice or start a session.

On Apple devices, the app also writes a small status file next to its saved data. It contains only your current choice, the selected ritual type, the planned end time and whether a session is active. It contains no intention text, Shortcut names or identifiers, and nothing from the cube, held requests or tomorrow's first step. No widget, control, lock screen or watch face reads it; from 0.8 the app gives the lock-screen view its content directly (see "Lock screen and ongoing views"). It is rewritten after every change, so after you delete local data it no longer contains a choice.

Unless you turn on the record, the app does not build a history of your choices, sessions or closed loops. Only the current and the most recent session are kept.

Saved data is kept in the app's private storage. The Android apps exclude this storage from Android cloud backup and device-transfer backup. The Apple apps apply operating-system file protection to saved files and mark their storage directory as excluded from backup. On Apple devices, this storage may be an area shared only between NOPECUBE's own app and its own extensions (an App Group); the same protection and backup exclusion apply there. NOPECUBE does not provide an account-based cloud recovery service. Removing the app or losing a device can therefore result in the loss of your local information.

The cube, held requests and tomorrow's first step

Put it in the cube, Hold a request and the line for tomorrow in Put the day down are available in the iPhone, iPad and Android phone apps only. Watches have no cube, no held requests and no line for tomorrow.

What is stored. When you put something in the cube, hold a request or write tomorrow's first step, the app stores the line you wrote (up to 280 characters), when you wrote it, when it is due, and whether it has already been kept in the cube once more. It keeps at most 50 such items. For a request, the app stores only your line and the answer time you picked. It does not ask for names or recipients and does not access your contacts or messages.

How it is protected. These items are kept in a separate file, not in the app's main saved data. On iPhone and iPad, the file uses the operating system's complete data protection: it is encrypted and cannot be read while the device is locked, so the cube asks you to unlock it before it shows anything. On Android phones, the app encrypts the file with AES-256-GCM using a key held in the Android Keystore on your phone. On both platforms the file is excluded from cloud backup and device transfer. NOPECUBE never includes these items in sync, backups, logs, the record or exports.

Where the text appears. Only inside the app: on the card where you wrote it, and when it comes back to you. It never appears on the lock screen, in a notification, on a watch, widget, complication or tile. No screen shows how many items are waiting. NOPECUBE does not analyse, score or use artificial intelligence on anything you write.

When it is deleted.

Add to calendar, Copy and Share (optional)

Add to calendar. When you plan something from the cube, or when tomorrow's first step appears, you can choose Add to calendar. NOPECUBE then opens your system's own calendar editor (on iPhone, the iOS event editor; on Android, the calendar app you choose) filled in with the step you wrote and the time. You decide whether to save it there. NOPECUBE does not request calendar access, cannot read your calendars or events and does not learn whether you saved anything. A saved event is kept by your calendar under its own settings and policy, which may include syncing it to your calendar account.

Copy and Share. Hold a request and Put the day down offer short reply lines, such as "I'll get back to you about this. I need a little time." You can edit a line before using it. Copy puts it on your device's clipboard; Share opens the system share sheet, where you choose an app. NOPECUBE never sends a message itself, does not choose a recipient and does not learn whether you sent anything. The app you choose handles the text under its own policy.

The clip (from 1.1). On iPhone, iPad and Android phones, Settings → About → Share the clip (Tall or Square) opens the system share sheet with one of four four-second videos that come with the app: N slides to NOPE and back, with the NOPECUBE click. They are made in advance and are the same for everyone: nothing you wrote, no door, time, date, name, link or metadata. The first time, the app asks whether the clip should show NOPECUBE, with two equal answers and nothing preselected, and keeps that answer on the device. On iPhone and iPad, Save Video is not offered, so no photo library permission is asked. On Android, the app places a copy of the chosen video in its own cache so the app you choose can read it, and the next share replaces it; no storage permission is asked. NOPECUBE does not learn whether or where you share it and keeps no record of it. The app you choose handles the video under its own policy.

Notifications you turn on (optional)

This section covers notifications that signal a time. From 0.8, the silent view of a running moment on the lock screen, including Android's ongoing notification, is described under "Lock screen and ongoing views" below.

When offers appear (from 1.1). Every offer in this policy (the closing bell, the three reminders, the record, the lock-screen view, the Android tile and, on iPhone, the guide to the control) comes only right after you close a loop on that device: a timed moment you close there with OPEN, or an item you plan, let go of or answer there. It never comes while NOPE runs, on the first-launch screens, when you open the app from the closing bell, next to an "outside the app" line, or after Undo or a change from your paired device, and a device shows at most one offer a day. Each offer has one turn: one you leave unanswered does not come back on a later day, and its feature stays a setting. The app decides this from your answers, the offers it has already shown and the date of the last offer, never from how often you use it.

Closing bell

The closing bell is off unless you turn it on. NOPECUBE asks once, on the ritual screen, whether you would like one signal when your time is up: up to 1.0 the first time you started a timed ritual on a device, from 1.1 after you close a loop there, for your next moment. "Not now" is equally available, and the question is not asked again. You can change it at any time in Settings → Closing bell.

If you turn it on, the app asks the operating system for permission to show notifications at that moment, not before. When a session starts on that device, the app schedules one local notification with the operating system for the planned end time. Its title is "NOPECUBE" and its text is fixed: "Your planned time is complete. Slide to OPEN when you're ready." It does not show the ritual, your intention or any numbers. It does not repeat, has no action buttons and never changes your choice. If the session ends before the planned time (through OPEN, undoing its start, Delete local data or a newer choice received through sync), or you turn the bell off, the pending bell is cancelled.

The notification is scheduled and shown on your device by the operating system's local notification service. No push notification service is used and nothing about the bell is sent to NOPECUBE. On Android, the app uses the system alarm service with a delivery window of about one minute and does not request exact-alarm permission. Up to 0.7, if an Android device restarts during a session, the bell is scheduled again only the next time you open the app; from 0.8, the phone app schedules it again by itself once the phone is first unlocked after the restart (see "NOPE Mode on Android"). A session started on a watch schedules its bell on that watch. If you do not allow notifications, the ritual works the same way; the bell cannot ring.

Cube, answer-time and day-down reminders

On iPhone, iPad and Android phones, NOPECUBE can show three more kinds of local notification. Each is off unless you turn it on:

Together, these three reminders show at most two notifications a day; the closing bell is not counted. Answer times come first. If a day is already full, the cube or day-down reminder moves to the next day, and a request's answer time shows only inside the app.

Each offer has an equally easy "Not now", and once you answer it, it is not asked again. You can change each reminder and its time in Settings. The reminders use the same notification permission as the closing bell; if you have not given it, the app asks at the moment you say yes, not before. No other permission is requested.

Each reminder's title is "NOPECUBE" and its text is fixed. It shows nothing you wrote, no door name and no numbers. It has no action buttons; tapping it opens the matching door ready in the app and never makes a choice for you. There is no "missed" notice. Only the two daily reminders, when the cube opens and your day-down time, can pause. If one of them rings and you do not use that door the same day (opening the cube or starting to put the day down; putting something in the cube does not count), the app notes this on your device. After three such days in a row, that reminder pauses by itself; the door keeps working in the app, and Settings shows that the reminder is paused. Turning it on again resets the count. The answer-time reminder does not pause; it comes once for each request.

Reminders are scheduled on your device by the operating system's local notification service; no push service is used and nothing about them is sent to NOPECUBE. On Android, the app uses the system alarm service with a delivery window of about one minute and does not request exact-alarm permission, so a reminder can arrive a few minutes late. Up to 0.7, if an Android phone restarts or its time zone changes, reminders stay silent until you next open the app. From 0.8, the app sets them again by itself when the clock or time zone changes, and after a restart once the phone is first unlocked. Like other phone notifications, they may also appear on a paired watch, depending on your watch settings; they still show no personal text. If notifications are off, the doors work the same way in the app.

Record of closed loops (optional)

The record is off unless you turn it on. After a closed loop, NOPECUBE asks once, on that screen, whether you want to keep a record on this device (up to 1.0 after your first closed loop; from 1.1 not before the next day); "Not now" is equally available. You can turn it on or off in Settings → Record of closed loops.

An entry contains only the date and time, the door, how the loop closed (with OPEN, planned, let go or answered) and, if you answered the optional "Did it help you get to what you meant?" question, your answer (yes, partly, or something else mattered more). That question appears only while the record is on. An entry contains no text you wrote, no durations or minutes, and there are no totals, percentages, charts or streaks. The app keeps at most 200 entries; when a new one is added, the oldest is removed.

You can delete one entry or the whole record at any time. When you turn the record off, the app asks whether to keep or delete the entries you already have. Export creates a JSON file with the same fields and hands it to the system share sheet; the app or place you choose handles it under its own policy. The record stays on this device: it is not synced or backed up, and it is lost when you change phones or remove the app.

Opening a ritual from Siri, Shortcuts or the app icon (optional)

On iPhone, the "Prepare a ritual" action in Siri and the Shortcuts app opens NOPECUBE ready on the ritual you pick. On Android, long-pressing the app icon offers the five rituals. A nopecube://ritual link does the same on each platform. These entry points carry only the ritual type, for example "focus". They never carry your intention and never make the choice for you: you still slide. When you use Siri, Apple processes your voice request under Apple's privacy policy; NOPECUBE receives only the resulting action and ritual type.

Setting NOPE or OPEN outside the app (optional, from 0.8)

From 0.8, you can make your choice without opening the app, but only with a deliberate press:

A press sets NOPE for your selected ritual, or OPEN if a moment is running; "Set NOPE now" only sets NOPE. The choice is saved on the device before any feedback or other effect. If your device asks you to unlock it before NOPE, it asks the same before OPEN. When you next open the app, within 30 minutes and before your next choice, the ritual screen shows once "Started outside the app." or "Closed outside the app.", with Undo. When a press outside the app starts NOPE, NOPE Mode (if you set it up) starts 5 seconds later; if OPEN or Undo comes first, it does not start. A press outside the app never opens a Shortcut or link you connected, even if the app is open at that moment. Instead, the next time you bring NOPECUBE to the front, it offers that Shortcut or link once, below the "outside the app" line, and opens it only if you tap it. A press outside the app also never saves a first step for tomorrow that you had typed but not yet slid.

Everything else only prepares. The "Prepare a ritual" action, a Focus filter, opening the app and nopecube:// links open NOPECUBE ready on a ritual and never make a choice, whatever starts them: a time, a place, a Focus or another app. NOPECUBE never makes a choice from sensors, location, mood, usage or inference, and it never creates an automation. If you put "Set NOPE now" into an automation you build in the Shortcuts app, that automation counts as your press; add it only to automations you want to commit.

These surfaces show very little. The control shows no state. The Android Quick Settings tile shows only whether a moment is running and its planned end time. The Wear OS tile shows NOPE or OPEN and the planned end time; pressing it saves the choice on the watch and, if sync is on, sends it like any choice made on the watch. The "NOPECUBE state" action returns only your current choice, the selected ritual and the planned end time to the shortcut on your device that asked for it. None of them shows your intention or anything from the cube, and nothing about a press is sent to NOPECUBE.

Lock screen and ongoing views (optional, from 0.8)

NOPECUBE asks once, on the ritual screen, whether a running moment should show on the lock screen (up to 1.0 at your first timed NOPE on a device; from 1.1 after you close a loop there, about your next moment): "Only NOPE and the planned end time. It stays silent and ends with OPEN." "Show it" and "Not now" are equally available and the question is not asked again. You can change it at any time in Settings → Show on the lock screen.

On iPhone. If you choose "Show it", a Live Activity appears on the Lock Screen and in the Dynamic Island while a moment runs on that iPhone. It shows NOPE, the planned end time (a fixed time, not a countdown) and one OPEN button. It shows the ritual's name only if you turn on Settings → Also show the ritual's name, and only while your iPhone is unlocked; the name is marked as private, so it is not shown while the iPhone is locked. It never shows your intention or anything from the cube, plays no sound and sends no alerts. The app gives the Live Activity its content directly on the iPhone through Apple's ActivityKit; no push service is used and nothing is sent to NOPECUBE. NOPECUBE's widget extension, which draws the Live Activity and the control, reads no saved data. With iOS 18 and watchOS 11 or later, iOS may also show the Live Activity in the Smart Stack of your paired Apple Watch. The Live Activity ends with OPEN, Undo, Delete local data, a reset from your paired device, when you turn the setting off, or if the app's saved data can no longer be read. iOS can end a Live Activity after about 8 hours; your moment continues in the app. If you turn off Live Activities for NOPECUBE in iOS Settings, only this view goes away.

On Android phones. If you choose "Show it", one silent notification appears while a moment runs: "NOPE", "until" with the planned end time, and one OPEN action. On Android 16 and later, Android may show it as a Live Update, with the end time in the status bar; on earlier versions it is an ongoing notification. On Android it never shows the ritual's name, locked or unlocked, because Android cannot promise to keep a name off a locked screen; the "Also show the ritual's name" setting exists only on iPhone. It never shows your intention or anything from the cube. It uses a low-importance channel, named "NOPE on the lock screen" in Android's notification settings, and makes no sound. It needs notification permission; without it, nothing is shown and the ritual works the same way. If you swipe it away, it does not come back for that moment. It is removed with OPEN, Undo, Delete local data, a reset from your paired device, or if the app's saved data can no longer be read. To be shown as a Live Update, the app declares Android's POST_PROMOTED_NOTIFICATIONS permission, which Android grants without asking.

On Wear OS. A moment you start on the watch can show NOPECUBE's icon on the watch face and in Recents while it runs (an ongoing activity), tied to a silent notification on the watch. It shows no ritual name, intention or anything from the cube, and it ends with OPEN.

These views are drawn by the operating system from what the app gives it on your device. Like any lock-screen content, they can be seen by someone holding your device.

Focus filter on iPhone (optional, from 0.8)

In iOS Settings → Focus → a Focus → Focus Filters → NOPECUBE, you can choose a ritual for that Focus ("Prepare this ritual"). When that Focus turns on, iOS gives NOPECUBE the ritual you chose; the app saves it on the iPhone and, if no moment is running, has that ritual ready the next time you open NOPECUBE. When the Focus turns off, the saved ritual is cleared. A Focus filter never starts NOPE and never changes your choice: you still slide. iPhone does not let apps turn a Focus on or off. NOPECUBE's Settings explain how you can connect a Focus through your own shortcuts, which run in Apple's Shortcuts app.

NOPE Mode on Android (optional, from 0.8)

On Android 15 and later, you can set up NOPE Mode in Settings → NOPE Mode. It lets Android quiet your phone while NOPE runs, through a Do Not Disturb mode that belongs to NOPECUBE. It is off unless you set it up. On earlier Android versions it is not available, and on Apple devices and Wear OS it does not exist.

Setting it up. NOPECUBE first explains the mode. When you continue, it opens Android's settings screen where you can allow NOPECUBE Do Not Disturb access (notification policy access). This is the only new access 0.8 asks for, and the app asks for it only here. With that access, NOPECUBE creates one Do Not Disturb rule named "NOPE", described as "When you slide to NOPE" in the app's language (the description follows if you change the language). By default, starred contacts, repeat callers and alarms still get through; you decide what gets through in Android's settings. You can also turn on a gray screen and a dimmed wallpaper during NOPE; both are off unless you turn them on. The app keeps the rule's identifier and these settings on your phone.

When it is on. After your NOPE is saved (5 seconds later if you pressed outside the app), NOPECUBE turns its rule on. OPEN, Undo, Delete local data and a reset from your paired device always turn it off, and so does the app if its saved data can no longer be read. It is also set to turn itself off 5 minutes after the planned end, even if NOPE is still on. Because NOPECUBE does not use exact alarms, Android can delay this: usually by up to about a minute and a half, but by up to about an hour if Android has not seen you use NOPECUBE recently. So that this happens while the app is closed, the app sets a system alarm, as it does for reminders. While a moment runs, the ritual screen shows one line saying that NOPE Mode is on, or that it could not turn on; your ritual is saved either way. If you change or snooze the rule in Android's settings, NOPECUBE follows your choice and tells you so.

After a restart or a clock change. A restart clears system alarms. So that NOPE Mode does not stay on after a restart, the app declares Android's RECEIVE_BOOT_COMPLETED permission, which Android grants without asking, and listens for Android's notices that the phone has restarted or that its clock or time zone has changed. These notices are used only to turn off a NOPE Mode that is past its end and to set NOPECUBE's reminders and alarms again. They never make a choice, and nothing about them leaves your phone. After a restart, Android sends this notice only once the phone is first unlocked, so until then a NOPE Mode that is past its end can stay on.

Removing it. Settings → Remove NOPE Mode deletes the rule, and Delete local data removes it too. You can withdraw Do Not Disturb access in Android's settings at any time.

What NOPECUBE learns. Nothing about your calls, messages or notifications. NOPECUBE uses this access only to create, turn on, turn off and remove its own rule. NOPE Mode quiets your phone according to the Do Not Disturb settings you choose; it does not close or block apps and does not change your other Do Not Disturb schedules. Nothing about NOPE Mode is synced or sent to NOPECUBE.

NFC tags (optional, from 1.0)

Writing a tag on Android. In Settings → Connect an NFC tag to NOPE on an Android phone, you can write a blank, writable NFC tag that you own. The app writes only while that screen is open and you hold the tag to your phone. It writes two records and nothing else: a NOPECUBE record (type application/vnd.nopecube.tag) whose only content is {"v":1}, a format version; and an Android application record naming the NOPECUBE app (com.nopecube.app), so that Android opens NOPECUBE or, if it is not installed, may offer its Play Store page. The tag holds no personal information: no ritual name, no intention or other text you wrote, no identifier and no web address. NOPECUBE does not lock the tag, so you, or anyone with an NFC phone, can read, erase or rewrite it, and anyone who reads it can see that it is for NOPECUBE. For this feature the app declares Android's NFC permission, which Android grants without asking.

Tapping the tag. A tap opens NOPECUBE and counts as a deliberate press, like the Quick Settings tile (see "Setting NOPE or OPEN outside the app"). It sets NOPE for your selected ritual, or OPEN if a moment is running, and the choice is saved on your phone before any feedback. The app then shows once "Started outside the app." or "Closed outside the app.", with Undo. A tap never opens a Shortcut or link you connected by itself; the app offers it once and opens it only if you tap it. If you set up NOPE Mode, it starts 5 seconds after a tap that starts NOPE, so an accidental tap can be undone first. On Android 16 and later you choose which apps NFC tags may open; if NOPECUBE is not allowed, a tap makes no choice and Settings shows a note with a button that opens that Android setting. On newer Android versions, a tag opens NOPECUBE only after you have opened the app once since installing it. Writing or tapping a tag never contacts a server and sends nothing to NOPECUBE.

On iPhone. The iPhone app does not read or write NFC tags. Settings → Connect NOPE to your iPhone explains how to create an automation in Apple's Shortcuts app that runs the NOPECUBE action "NOPE or OPEN" or "Set NOPE now" when you tap a tag you own. The Shortcuts app reads the tag under Apple's policy, and the automation counts as your press. NOPECUBE receives only the action, nothing about the tag.

Watches have no tag feature.

What we based this on. Settings → What we based this on shows short notes on the research the design is built around, starting with "NOPECUBE itself has not been studied." The notes, their grades and the names of their sources come with the app, so showing them needs no connection and sends nothing. The "Why this?" links in the door headers open the matching note inside the app.

Links that open your browser. The source link under a note, "Sources and dates on nopecube.com" and the cube link in Settings (from 1.1, at the end of Settings → About) open in your browser, outside the app. Source links lead to publishers' or authors' websites (for example doi.org), which receive technical connection data such as your IP address under their own policies; for nopecube.com, see "Website". These links carry no tracking parameters, and NOPECUBE does not learn whether you opened them.

The cube in Settings. From 1.1, Settings → About ends with one line on the physical NOPECUBE cube and a plain link to nopecube.com; up to 1.0 this was a short section of its own, Settings → The cube. The line never appears during a ritual, in an offer, in a notification or on the first-launch screens.

On iPhone, you can enter the exact name of a Shortcut you created. After a ritual starts on that iPhone, or when OPEN closes a session started there, the app asks iOS to open Apple's Shortcuts app with that name. On an Android phone, you can enter an HTTPS link; after the same events, the app hands the link to Android, which opens it in the app or browser it chooses. That app or website receives the link and handles it under its own policy. From 0.8, when the choice was made with a press outside the app, nothing is opened by the press; the app offers the Shortcut or link once when you next open it, and hands it over only if you tap it.

Only the configured Shortcut name or link is handed over. Your intention, session and choice are not added to it, and no clipboard content is used. Undo, sync, relaunching the app and the feedback preview never run these actions. Undo cannot reverse what another app has already done. Watches do not run phone Shortcuts or links.

Optional phone and watch sync

Sync is off by default. You can enable it in Settings on a supported Android phone and Wear OS watch, or on an iPhone and its paired Apple Watch; both devices must enable it. The ritual works without sync or a connected phone.

When enabled, sync transfers only the current choice, random installation and event identifiers, version counters, reset markers and delivery acknowledgements. It transfers replaceable current snapshots rather than a choice history. Your ritual plans, intentions, sessions, Shortcut names, links, anything in the cube, held requests, tomorrow's first step, reminder settings, the record, the closing bell setting, undo information and other preferences are not included in sync messages.

On Android and Wear OS, sync uses the Wear OS Data Layer API provided by Google Play services. Data can travel directly over Bluetooth or through Google's servers, and the platform can retain sync data to deliver it when devices reconnect. Google documents encrypted Bluetooth transport and end-to-end encryption for Data Layer traffic through Google Cloud. The app's sync payload is available only to the same signed NOPECUBE app on the connected devices; NOPECUBE does not receive it on a developer-operated server. See Google's Data Layer overview and DataClient persistence documentation.

On iPhone and Apple Watch, sync uses Apple's Watch Connectivity framework to send a replaceable current snapshot between the paired NOPECUBE apps. The operating system controls when this data is delivered and may retain a pending snapshot until it can deliver it. NOPECUBE does not send this data to a developer-operated server or an iCloud database. See Apple's Watch Connectivity documentation. The Apple Watch complication opens the ritual and does not show your choice or intention. Up to 0.7, the Wear OS Tile does the same; from 0.8 it shows NOPE or OPEN and the planned end time and sets your choice with a press (see "Setting NOPE or OPEN outside the app"), still without your intention. From 0.8, none of the new fields (the receipt, the lock-screen, tile and Focus filter settings, NOPE Mode) is included in sync messages.

Turning sync off stops new choice transfers from that device. It does not itself delete snapshots or acknowledgements already retained by the platform. A reset requested while sync was enabled can continue to be transmitted until acknowledged, as described below.

Deleting information

Use Settings → Delete local data on each device. This clears that device's choice, every ritual plan and intention, everything in the cube, held requests and tomorrow's first step (including the encrypted file and, on Android, its key), the record, the current and most recent session, connected Shortcut names and links, the closing bell and reminder settings with any pending notifications, your preferences and undo information. From 0.8 it also clears the receipt and your lock-screen, tile and Focus filter settings, ends the lock-screen view and the Android ongoing notification, and on Android turns NOPE Mode off and removes its Do Not Disturb rule. Deleting here does not reverse actions already performed in other apps, and does not remove calendar events you saved or messages you sent from another app. A control or tile you added stays in Control Center or Quick Settings until you remove it there; it holds no data. From 1.0, an NFC tag you wrote is not changed by Delete local data, because it is not stored in the app; erase or rewrite the tag if you no longer want it to open NOPECUBE, and remove a Shortcuts automation in the Shortcuts app.

To prevent an old choice from being restored by another device, the app keeps its random installation identifier and a minimal reset marker. If sync was enabled, the app sends this marker through the same sync service, retrying until the receiving app confirms it has saved it. When the other app processes the reset, its shared choice and sessions are cleared, and from 0.8 its lock-screen view ends and its NOPE Mode turns off; its own ritual plans, intentions, preferences, reminders, record, anything in its cube and, from 0.8, its lock-screen, tile, Focus filter and NOPE Mode settings remain on that device. Delete local data on that device as well if you want to clear them.

On Apple devices, recovery from damaged saved data is a separate operation. If recovery succeeds, it clears the local personal fields and keeps a reset marker, but it may not send that marker to the other device. Delete local data separately on both devices when clearing information after a storage error.

Deletion does not promise immediate removal of every platform transport copy or acknowledgement. The retained reset information contains no intention text, nothing from the cube, held requests or tomorrow's first step, and no previous OPEN/NOPE choice.

What NOPECUBE does not do

Google Play, Apple's distribution services and your device's operating system may process their own service and diagnostic information under their respective policies. If you have allowed your device to share diagnostics with app developers, Apple or Google may provide NOPECUBE with crash and performance reports. These reports are prepared by the platform; they do not include your choices, plans, intentions or anything you wrote in the app.

Website

nopecube.com is a static website hosted on Cloudflare Pages. When you open it, including through the links in the app's Settings, which open in your browser (Privacy policy, What we don't do and, from 1.0, the science and cube links), Cloudflare processes technical connection data such as your IP address and browser details to deliver and secure the pages, under Cloudflare's privacy policy. NOPECUBE does not use analytics, advertising or tracking cookies on the website.

Children

NOPECUBE is designed for adults and is not directed at children. The apps do not send personal information to NOPECUBE, so NOPECUBE holds no information about any user, including children. Anything a child enters stays on the device and can be removed with Delete local data.

Your choices and rights

Because your information stays on your devices and is not sent to NOPECUBE, you can view, change, export (the record) and delete it directly in the app. NOPECUBE holds no copy that it could access, correct, export or delete for you. You can still contact us with any privacy question, and you may have the right to lodge a complaint with your data protection authority.

Changes to this policy

We will update this policy before a change in the apps' data handling is released, and change the date above. New data leaving your device, or a new permission, will also be stated in the release notes of the version that introduces it.

Contact

For privacy questions or support, write to hello@nopecube.com. If you email us, we use your address and message only to reply to you, do not add them to any list, and delete the conversation when it is resolved or when you ask us to. Please do not send us anything you put in the cube, a held request or other private notes; we never need them to help.