Nanouri · Privacy
Last updated: 2026-09-24 · Eliary Inc. (a Delaware C-Corporation) is the controller.
Nanouri is an interactive-video service. This page describes viewing, optional accounts, notifications, creator uploads, safety tools, and account deletion. Contact support@currot.com about your data.
Your public comment name is separate from your email and Creator Studio name. We store current comment text, author and video references, reply relationships, edit markers, consent, and safety preferences. Ordinary edit history is not stored. Reported versions can be retained as case evidence until the author, creator, or account deletion removes their text. Minimal case categories, outcomes and times remain for one calendar year after the case or appeal closes. Unresolved cases remain until closed.
Creators can receive each new comment as an immediate notification after allowing device permission. Lock screens show a generic new-comment notice and video title, not comment text. After successful delivery we separately save an excerpt of at most 120 characters for the creator's management screen. If the creator deletes a comment, its full body is removed and this excerpt expires 30 days after deletion. Author or account deletion removes the excerpt earlier. Previously delivered notifications cannot be recalled.
Notification processing records without text and non-case action logs expire after 30 days. Write retry records remain while a comment exists; deletion leaves a 30-day deduplication marker. Requests older than 24 hours must be submitted again by the user. These records do not preserve deleted text. Cleanup jobs remove expired rows; reads enforce excerpt expiry immediately.
Comment drafts stay on this device for 7 days, are excluded from OS backup, and are cleared after a successful post, sign-out or account deletion. Drafts never post automatically. Minimal video deletion tombstones contain only the video ID to prevent an old deleted link from being reused. Nanouri accounts, content and databases remain separate from Currot; sharing a support address does not link accounts.
You can watch without signing in. The app creates a random viewer key for this installation and a temporary session ID. Playback events include the experience and published version, clips and choices, viewing duration, entry route, stalls, transition timing, delivery network, and video quality. They help us operate playback and understand how experiences are used. The viewer key is a pseudonymous installation identifier, not a name or an advertising identifier. It lets us recognize a returning installation; we do not describe it as anonymous.
Saved paths and answers also live on your device. New playback, including reopening a saved path, requires an online server check. Cached media does not allow a new offline playback.
| Data | Purpose and connection | Retention |
|---|---|---|
| Viewer key, session ID, playback events | Playback measurement and troubleshooting. Events refer to a random installation key, not an email column. | Playback events have a 90-day retention target. The deletion sweep is run by hand; overdue rows remain until it runs. The on-device key remains until Clear all or local app-data removal. |
| Catalogue/access tokens and request records | Access control, abuse prevention and troubleshooting errors for an installation or account; our application records a truncated IP address, app/browser family, token, and request type. Member tokens can be linked to an account. | Account-linked records are covered by account deletion. No deletion date set yet for unrelated installation tokens and request records. |
| Email, account ID, optional display name, login links and sessions | Sign-in, account features and support. Login links and sessions are stored as hashes. | Links expire after 15 minutes and sessions after 90 days; expiry is not deletion of the row. Account data is removed through the deletion process below. |
| Follows, bell settings and blocked creators | Account-wide preferences and safety. | Until changed or account deletion. Blocking preserves follow and bell settings. |
| Push registration token, platform, account binding and delivery-limit records | Send new-work notifications to the correct signed-in account and limit repeated sends. | Token bindings are revoked on sign-out/disable when reachable, replaced on account changes, and removed on account deletion. Server access checks stop delivery to a disabled account. |
| Reports and moderation | Reporter account, reported work and exact version, one of six reasons, optional text up to 1,000 characters, decision and processing times. Creators also have notices and appeals. | Unresolved reports and appeals remain until closed. Report and moderation details are retained for one calendar year after closure; an appeal starts that period again when its handling is completed. On reporter account deletion, we remove the reporter link, submitted text and identifying notes, keeping the case reason, target version and outcome for the remaining period. When a creator deletes their account, we remove their email, name and related free-text details from reports, notices and appeals. We retain the internal account ID, case type, enforcement decision and processing times to connect that account's incident history. Pending cases remain until closed, and case history is retained for one calendar year after closure, including completion of an appeal. These account-linked records are not anonymous. We do not keep permanent violation-count profiles. A minimal record of the work, version and withdrawn status is retained indefinitely to keep that version unavailable. It does not retain the creator identity, reason, operator or incident timestamps. |
| Creator uploads | Original and converted video, audio, images, drafts and published versions, linked to the creator account. | Until removal through the applicable content or account process. Account deletion hides all owned content immediately and removes these files within 30 days, as described below. |
| Deletion request and receipt | Verify and complete deletion, retry interrupted work, and let you check the result after sign-out. | While pending, then 90 days after completion. The completed receipt is no longer linked to an account row. |
| Deleted-email block | A keyed hash (HMAC) of the normalized email, plus a key version, prevents the same email from registering again. The block stores no raw email. | Retained indefinitely. It is pseudonymous personal data, not anonymous data. |
Signing in is optional for viewing and is required for following, reporting, blocking and account settings. Our email provider sends a one-time six-digit code and sign-in link. They share a 15-minute lifetime; using either consumes the request, and a new email invalidates the previous code and link. Codes and links are not stored in plaintext by Nanouri. You may set a public comment name.
Following starts with the creator’s bell on. Notification permission is requested when you use Follow or the bell, not just when you open the app. You can turn a creator’s bell off or change notification permission in your device settings. Firebase Cloud Messaging and Apple Push Notification service deliver notifications; this uses push tokens and Firebase installation identifiers. Registration is bound to your signed-in account.
Notifications announce eligible newly published work, with a creator-to-follower limit of one notification per week. They are not guaranteed: a failed or uncertain delivery can be skipped, and missed notifications are not sent later. Opening one checks current access again.
Without the app, visit nanouri.com/delete-account. Enter your account email, open the five-minute deletion-only link, then confirm on the website. Opening a link alone never deletes an account. A web receipt is stored for the current browser tab; download the status-only receipt file to check later. The same deletion and retention rules apply.
In the app, open Profile → Delete account. Both viewers and creators can delete their accounts. Confirm using a deletion-only email link, valid for 5 minutes and one use, then confirm in the app. Opening the email link alone does not delete anything.
The configured no-inbox review account can use its existing sign-in passcode instead of email in the app. This issues the same five-minute, single-use deletion authorization and still requires a separate final confirmation. The same deletion and retention rules apply; the account is not automatically recreated.
When deletion is accepted, account sessions and new access to owned content stop immediately. The app clears this device’s saved paths, answers, queued events and old viewer key. Account records and original and converted media are removed within 30 days of the request; our backups expire within at most 7 additional days after that removal. Use the deletion receipt in the app to check completion after signing out; keep it private.
The report, receipt and deleted-email exceptions in the table still apply. Playback events that are not linked to your account follow the playback retention period; deleting an account does not identify every viewing session made without an account. A delivered file or a copy saved outside Nanouri cannot be remotely erased by this process.
The 30-day and additional 7-day periods describe data under our deletion process. On this device, the app requests deletion of the FCM push token and Firebase installation ID when you delete your account. On another device, it requests deletion when the app next runs and confirms that the account session is no longer valid. If that device never runs the app again, we cannot send its installation-ID deletion request. We do not remotely delete an installation based on an unverified ID. Firebase’s published period is up to 180 days after each installation-ID deletion request; it does not start when you delete your Nanouri account on a different device. That provider period is separate from our 30-day and 7-day periods. See Firebase’s privacy information. Contact us for access, correction or other deletion requests.
Opening a project application page sets an nk cookie: a random ID with a one-year
browser lifetime. It is set simply by opening the page. We record that page view and,
if you apply, its structured answers and truncated IP. Campaign counters record link, step and
time without an IP or token. These site records have no deletion date set yet.
Our application truncates IP addresses to an IPv4 /24 or IPv6 /48 before writing its request records. Network providers necessarily receive the full IP address to deliver requests and may retain their own logs. A truncated IP can still be personal data.
Clear all in Where you left off clears local paths, answers and pending events and rotates the viewer key. It does not erase events already received by the server. Uninstalling or clearing local app data removes the local files. Browser cookies can be removed through browser settings. For an export, correction, or a request concerning server records, email support@currot.com. Our first-response window is 24 hours to 7 days.
We do not sell data or use it for tracking across other companies’ apps or websites, and we do not use advertising identifiers or advertising SDKs. The app does not request access to your location, contacts, camera or microphone, and does not send heart-rate or health data. Optional report text and support correspondence may contain information you choose to provide.
If you are in the EU, EEA or UK, applicable rights include access, correction, erasure, restriction, objection, portability and a complaint to your supervisory authority. We use account information to provide the features you request and limited service and safety data to operate and protect Nanouri. Contact us about the basis for a particular use or retention exception.
Nanouri is intended for people aged 13 and older, or the higher minimum age required in their country. If you are under 18, you need a parent or legal guardian’s permission. Nanouri does not offer a supervised account service for younger children. Sexually explicit and NSFW content is prohibited. If you believe a child below the applicable minimum age has provided personal information, contact support@eliary.com. When this policy changes, the date at the top changes.