The short version
Nudge shows no ads, embeds no third-party trackers or analytics, and never sells your data. Everything you create is stored in Apple iCloud (CloudKit) on Apple's infrastructure. We use a protected administration dashboard hosted on Vercel to review records in Nudge's shared CloudKit database and manage account restrictions, safety warnings and informational service messages. It does not access your private iCloud database. We do not keep a separate database of your content in this dashboard. What you share with friends is visible to those friends; what you keep personal stays personal.
What Nudge stores
- Profile: your display name, optional bio, optional avatar photo or emoji, and accent color. Your profile is visible to other Nudge users you interact with (for example, members of a shared countdown and your Nudge Mates). If you add your birthday, it stays in your private data and is not part of your public profile.
- Countdowns and their content: titles, dates, notes, categories, locations you attach, photos, nudges (taps and short messages), replies, emoji reactions, photo pings, and surprises (photos or messages that unlock on the day). For shared countdowns this content is visible to every member of that countdown. Personal countdowns, and secret countdowns you haven't shared, are not shared with anyone. In a shared countdown (not a secret one), Nudge also keeps, for each member, when they last looked at its nudges (as the time of the newest nudge from others when they last opened it), so the app can show how many of your nudges your friends opened; members of that countdown can therefore tell roughly when you last looked.
- App activity signals: the approximate time you last opened the app, your device's time zone identifier, the app version you run, and a running total of your countdowns (secret ones included, as a number only; countdowns deleted before you updated to Nudge 1.1.1 are not in it), shown as an all-time total in your profile starting with Nudge 1.5. Starting with the next app update, the app also shares an aggregate count of the ordinary Nudge Mates known on your device, excluding blocked people, sample contacts and people known only through secret countdowns. This count contains no contact identities. These signals are stored on your profile record, which other Nudge users' apps download along with your profile, although the app does not show the signals to them. We use them to operate the service and to understand how Nudge is used (for example, to know which app versions are still active and how many countdowns people make). They are never used for advertising or profiling.
- Invitation milestones, starting with Nudge 1.4: your profile also stores when invitation measurement began for your account and the earliest retained measured dates for opening a valid ordinary countdown invitation in Nudge, joining a measured countdown, and successfully sending a nudge after joining one of those countdowns. These are measured milestones, not a complete activity history; delayed device synchronization can make a recorded date later than the first actual action. We use these account-linked dates to understand whether invitations help people start using Nudge together. This summary contains no invitation codes, countdown identifiers, recipient lists, messages or photos. It is stored on your profile record in the shared database, so other Nudge users' apps can obtain it, although Nudge does not display these dates to them. It does not measure anonymous website visits or app installations.
- Service messages, starting with Nudge 1.5: we can send an informational message to selected accounts through our protected dashboard. Its identifier, text and issue time, plus your acknowledgement identifier and time, are stored on your account record in the shared CloudKit database. Updated apps show it when you next open Nudge. You can dismiss it immediately; it is separate from a safety warning and does not use its countdown or restriction rules. Saving a message does not prove that you have seen it. No phone push is sent by this service-message feature.
- Referrals, starting with Nudge 1.5: if you use a personal invitation link or code, or join an ordinary shared countdown using its six-digit code, Nudge records the referring and referred account identifiers, the invitation code and scope, original account creation time, and the membership and newly saved nudge identifiers needed to check qualification. If no referral is already confirmed, an invitation carrying a personal referral code credits that inviter; a countdown code without one credits the countdown owner. A confirmed referral stays linked to the same inviter. A protected Vercel service checks these steps against CloudKit and keeps at most one qualified referral credit per iCloud account for its lifetime. During the current extended normal-eligibility period, an unbound account can apply an invitation within 30 days of its original creation. This includes recent accounts created during the 30 days before the referral programme began, but the claim itself must occur at or after programme start and fresh participation is still required. Past activity is not automatically converted into credit. Accepted first attribution and lifetime credit remain valid if the normal entry window is reduced later. Starting with Nudge 1.6, completing Erase all data offers one lifetime eligibility exception for an account that has never qualified, even if the original account is older. The invitation must be applied within 15 days of the first reset's start. Updated apps carry that earliest reset date forward, and the service retains the earliest valid reset date it observes before an invitation is claimed. Later resets do not renew this invitation deadline. An existing first-inviter binding stays with that inviter; a fresh shared-countdown join and newly saved nudge are still required after a reset. Your inviter sees their qualified total, not a list of referred account identifiers. No message text or photos are copied into referral records. Links contain an invitation code, not your account identifier. A valid invitation link also lets its web landing show the inviter's existing public display name. That preview returns only the display name, without an account identifier, member list or countdown content, and it does not join a countdown. In Nudge 1.6, three verified referrals unlock Signature and five unlock Special messages. The ten-referral milestone remains marked Coming soon.
- Safety data: if you block someone, a hashed record of that block is added to your public profile so their app can hide your photo, emoji, bio and new activity from them. The record is hashed, but someone who knows both user identifiers, such as a member of a countdown you share, could check it. If you report someone, the report is stored so we can review it: the reason you chose, your optional details, your and their user identifiers, their display name, their bio and a copy of their recent nudges and replies (up to ten of each), including when each was sent and the title of the countdown it was posted in (secret countdowns included; a message that has already expired in a self-deleting countdown is left out).
- Suggestions you send: when you choose Send suggestions in Settings, we store your typed message, your Nudge account identifier, the app version and build, and the submission date in CloudKit so the Nudge team can review feedback and improve the app. We do not automatically attach countdown messages, photos or other countdown content to a suggestion.
- Personal invitation codes in Nudge 1.6: Nudge can generate a six-character code or let you choose six letters or numbers, including at least one letter. The protected service stores your selected code, its link alias, the latest change time and processing-request identifier to confirm your choice, prevent conflicting changes and limit later changes to once every six calendar months, measured from the latest saved custom choice. The first custom choice is immediate; saving the same code does not restart the interval. Changing the manual code keeps its separate QR/link alias unchanged. Old codes and links can remain usable by the same account until their original expiry; their reservations are not reassigned to another account. New six-character codes have no public name or availability lookup. Public invitation links use a longer alias for compatibility. The selected-code policy record grants no referral credit and is excluded from totals. Erase all data retains this service record with your referral identity; you can request deletion through support.
- Invites and notifications: when you invite a Nudge Mate, an invite with your name, the countdown's join code and (unless the countdown is secret) its title is stored for them. To deliver alerts such as nudges, replies, joins and invites, a small record with the sender's name and the alert text is written for each recipient and delivered through Apple's push notification service.
Where it lives
Nudge keeps your data on your device and in Apple's iCloud CloudKit service, in Apple's data centers and under Apple's security measures. Nudge's content remains stored in Apple CloudKit. We use a protected Vercel-hosted administration backend to fetch shared database records when needed to run the service, review reports, handle support and manage account bans. The dashboard does not keep a separate content database. Vercel processes these requests and normal hosting logs on our behalf; we do not send user content to third-party analytics or advertising services. To lift timed restrictions without keeping the dashboard open, Vercel Queues stores only the CloudKit account identifier, restriction status, end time and scheduling time for each expiry job. Warning messages, reports and countdown content are not included in these jobs. Queue messages expire within seven days; longer restrictions use successive expiry jobs. To decide whether an available update is optional or required, Nudge fetches a public release policy from our Vercel-hosted website without sending an account identifier or app content. Nudge also asks Apple's App Store whether a newer compatible version exists, including at launch and when returning to the app; that request contains only the app's identifier and your App Store country, plus what any web request carries, such as your IP address.
- Your private iCloud database holds your countdowns (secret ones included), settings and Nudge Mates, and your iCloud key-value storage keeps the list of shared countdowns you're in so they can be restored after a reinstall, and a short code for each countdown you have had so that none is counted twice in your countdown total. Starting with Nudge 1.4, a separate invitation ledger on your device and in private iCloud key-value storage holds the milestone dates and account-scoped hashed countdown references needed to associate invitation, join and send steps. It holds at most 256 countdown references per account and environment. The app removes these references during ledger maintenance after the account completes the measured steps, or after 90 days without a newer observation. Private iCloud copies are updated on a later synchronization, so an older copy may remain until then. The account milestone dates remain. We cannot read your private iCloud database or key-value storage.
- Nudge's shared (public) CloudKit database holds what other people's devices need to reach: shared countdowns and everything posted in them, profiles, invites, notification records and reports. As the developer we can access these shared records through Apple's CloudKit tools and our protected administration dashboard. We do so only to run and improve the service, review reports and handle support or deletion requests. The dashboard can change an account's restriction status, optional ban message and end time, send a safety warning, or send an informational service message to selected accounts. Warning and service-message acknowledgements are recorded separately by the app. The optional ban message appears only for an explicit ban. The dashboard also supports reviewing and correcting a missed pending referral using its retained account-owned request and saved participation evidence. Corrections preserve the original inviter and lifetime duplicate protections. Other record fields remain read-only in the dashboard.
Device permissions
- Notifications: requested the first time Nudge needs them (for example when you save a countdown with reminders, or share or join one), so Nudge can show your reminders and alerts such as nudges, replies and invites. Reminders are scheduled on your device.
- Calendar: only when you tap Suggest from Calendar or add a countdown to Calendar. Nudge reads your upcoming events on your device so you can pick one, and only removes calendar events it added itself.
- Location: only for "Remind me when I'm nearby". iOS detects your arrival on your device; your location is never uploaded.
- Camera: only to scan a join QR code. Nothing is recorded or stored.
- Photos: photos you pick are added to your countdown or profile; saving a share image adds it to your photo library.
- Maps: place search and maps use Apple Maps. Choosing Google Maps under Open in Maps opens the place in Google Maps.
What we never do
- No advertising, and no data shared with advertisers.
- No third-party analytics, tracking SDKs, or fingerprinting.
- No selling, renting, or trading of your information to anyone, ever.
- No reading of your private (non-shared) countdowns.
For referrals, the Vercel service also processes creator-owned CloudKit request records and reads the existing shared membership and saved-nudge data needed to validate participation. Request and referral records are stored in CloudKit with restricted permissions. The service derives the requesting account from Apple's creator metadata; account identifiers and content are not placed in the public service URL. Normal hosting infrastructure still processes connection metadata such as IP addresses. Personal invitations and membership do not prove that accounts belong to different people. Optional referral gifts in Nudge 1.6 do not change access to another person's countdown or profile.
Sharing and visibility
When you join or create a shared countdown, its members can see the countdown's content and your activity in it (nudges, replies, reactions, photo pings, photos and surprises), along with your profile. Any member can edit a shared countdown's details and photos. Leaving a countdown, or being removed from one, ends your participation, but what you already posted there stays visible to the remaining members. If you are removed, Nudge 1.1 or later deletes your copy of the countdown and its history from your devices and your private iCloud the next time it syncs, normally without telling you (if the countdown's creator still uses an older version of Nudge, you may see that it ended instead). If you leave, your own copy stays as a personal countdown, as long as all your devices run Nudge 1.1 or later. You can report or block anyone from their profile; the Terms of Use explain exactly what blocking hides and its limits. Accounts that post objectionable content or abuse others can receive a warning or a temporary or permanent restriction. We store the warning text, its issue time and acknowledgement status, and any restriction end time on the account record to apply these safety measures. Informational service messages and their acknowledgements are stored separately on that same account record. Acknowledged warnings stop appearing after devices sync.
For referral support, the protected dashboard can show the relevant invited account and qualification status to the administrator. A correction records the original evidence identifiers, an administrator-provided reason, server timestamps, a pseudonymous administrator-session identifier, the configured service administrator identity when present, and an intent and outcome history. The session identifier does not contain the login cookie or password and does not identify a named person. Support can resume an interrupted correction without issuing another referral credit. The support path can review an older saved processing request; this does not extend the normal invitation eligibility or qualification windows. Correction audit records do not grant credit themselves and are excluded from referral totals. No message text or photos are automatically copied into them.
Starting with Nudge 1.6, an administrator can also correct an account's displayed referral total using a positive or negative adjustment. The original qualified referrals and their lifetime protections remain intact. The protected service stores the account identity, original account creation time, adjustment and a bounded audit history in restricted CloudKit referral records. Each entry includes the reviewed genuine count, requested total, previous and new adjustment, reason, operation identifier, administrator-session identity and server time. Retrying the same saved operation does not apply it twice. The adjusted total affects optional gift access, including its removal after a downward correction, while later genuine referrals continue to add to it. This action does not invent an invited account or change who referred someone. Erase all data does not remove this service history; contact support to request deletion.
Timed countdowns can retain the creator's time-zone identifier, such as Asia/Hong_Kong, so members see the same deadline and calendar repeats use that zone. Shared countdown metadata includes this identifier. It is not a precise location or a location history.
Nudge 1.6 includes an Apple notification service extension. For supported reply notifications it can read the exact reply already shared with your account from CloudKit and provide its full text to iOS for the expanded notification. It checks account, membership, reset, expiry and safety state before enriching the preview. Secret replies remain neutral, and unavailable data or a system timeout can leave the shorter original preview. This extension does not send reply text to our Vercel service or save new content to CloudKit. iOS controls lock-screen previews and the expanded notification layout.
Retention and deletion
- Deleting a shared countdown you created removes it from Nudge's shared database, together with its nudges, replies, photos and surprises, and each member's app removes it from their device and private iCloud when it next syncs. Deleting a countdown you joined only takes you out of it: what you posted there stays visible to the remaining members.
- Single nudges, replies and surprises can't be deleted one by one in the app. The exception is a self-deleting secret countdown, an option when you create a countdown inside the secret space: there, nudges, replies, reactions and photo pings are deleted an hour after they are sent, on every device running Nudge 1.1 or later, and the countdown itself is deleted a day after its date. Photos added to it are not on that clock. A report filed before a message expires keeps a copy of it for review. Photo pings stop showing after 24 hours; expired pings are cleared from iCloud the next time someone pings a photo in that countdown, or when the countdown is deleted.
- Starting with Nudge 1.6, “Erase all data” deletes your countdowns and Nudge Mates, clears pending invitations and settings, resets your public profile and All time countdown count, and restarts setup. Shared countdowns you own end for everyone; you leave countdowns owned by someone else. Cleanup that needs iCloud can remain pending while offline and resumes when a connection is available. A reset marker and cleanup receipts prevent updated devices from restoring older private copies or repeating completed cleanup. Updated apps also keep account-scoped peer reset observations and fresh-connection receipts on the device and in private iCloud key-value storage, so an old mate connection is not restored after that person resets. A fresh shared-countdown connection can establish that relationship again. Your original account creation date, referral history and confirmed referral binding, block list, reports, safety restrictions and service acknowledgements remain. If the account has never qualified as a referred account, completing a reset can restore eligibility once without changing its original creation date. The invitation window lasts 15 days from the earliest retained reset start, including when no invitation has yet been claimed. Later resets do not start another invitation window. Any existing first-inviter binding remains; a pending binding can resume with fresh shared-countdown participation after the reset. A previously qualified account cannot generate another referral credit by resetting. Content you previously posted in other people's countdowns, copies retained by other users and records needed for safety or service operation are not all erased by this action. Contact support to request deletion of remaining shared-database data.
- A new informational service message replaces that account's current message on the server; this feature has no message-history queue. The app also keeps an account-scoped cached message and acknowledgement receipts on your device to remember dismissal and retry acknowledgement syncing. Pending acknowledgements are retried until confirmed or superseded by verified account data; older confirmed receipts remain in a bounded local history. Dismissing a message, changing iCloud accounts or using Erase all data does not immediately remove these local files or the service-message fields in CloudKit. Service messages and acknowledgements have no automatic time-based deletion. To request deletion of remaining records in Nudge's shared database, use the support address below.
- Referral processing requests expire for acceptance after 15 minutes. Pending referrals have a 90-day qualification window from their initial claim or an accepted restart after a completed reset; restarting preserves the original account, claim date and inviter, and requires fresh post-reset participation. Those limits do not automatically delete CloudKit records. We retain referral requests, invitations, credits and internal antiabuse and correction audit records while needed to operate the referral programme, avoid duplicate or reciprocal credit and investigate delivery problems. The policy records retain the earliest reset date and the reserved direction between two account identifiers; they grant no credit themselves and are excluded from displayed referral totals. These use existing restricted CloudKit referral records rather than a separate database. Erase all data does not remove these service records. You can request their deletion with your profile through the support address below; this can reduce a referring account's total. Deletion requests follow the same 30-day response period as other shared-database requests. Nudge 1.6 does not promise automatic timed deletion of referral records.
- To request deletion of your profile record and any remaining data in Nudge's shared database, email us (address below). We will honor the request within 30 days. Copies already downloaded to other members' devices and their private iCloud go away when the countdown they belong to is deleted or when that member is removed from it; a member who left keeps their copy.
Children
Nudge is not directed to children under 13 (or the equivalent minimum age in your region), and we do not knowingly collect data from them. If you believe a child has provided data through Nudge, contact us and we will delete what Nudge's shared database holds about them.
Your rights
Depending on where you live (for example under GDPR in Europe), you may have rights to access, correct, export, or delete your personal data. In the app you can edit or clear your profile, delete your countdowns and use Erase all data; see Retention and deletion for what those do not remove. For anything else, including data held in Nudge's shared database, email us and we will help.
Changes
If this policy changes materially, we will update this page and the effective date above.
Support & contact
Need help, found a bug, or want your data deleted?
Email us at jyl.iosapp@gmail.com. We read everything and aim to reply within a few days. Reports of objectionable content, whether sent from the app or by email, are reviewed promptly.