Privacy Policy

This Privacy Policy explains how RexiMemo handles information when you use the RexiMemo website, Flipnote Studio/DSi service, community features, API, network compatibility services, moderation tools and related features (together, the Service).

RexiMemo is currently an Open Beta and is intended only for users who are 13 years of age or older. Children under 13 may not use the Service.

1. Who is responsible for your information

RexiMemo is responsible for personal information handled by the service at reximemo.net and, where applicable, acts as the data controller.

For privacy questions, account-data requests, rights requests or complaints, email rekunote@gmail.com.

2. Information RexiMemo handles

Account and profile information

RexiMemo can handle your username, account identifier, protected password credential, account creation and sign-in times, profile text, avatar choice, preferences, account roles and statistics associated with your account. If you choose to use an age-restricted feature, RexiMemo can also store the Date of Birth you provide and the limited change-history metadata needed to enforce the self-service correction limit. RexiMemo does not intentionally keep your account password as readable plaintext after authentication is processed.

Passkeys and WebAuthn

If you add a passkey, RexiMemo can store an opaque WebAuthn user handle, the passkey credential ID, public key, signature counter, the name you give the passkey, authenticator transport information, device-type/backed-up indicators, and creation and recent-use times. This information is used to register, identify, verify, display and manage your passkeys.

The private key for a passkey stays with your authenticator or credential provider and is not sent to RexiMemo. RexiMemo also does not receive the biometric template, PIN or device-unlock secret that your device may use locally to authorize the passkey. Your browser, operating system, hardware authenticator or credential provider may separately handle or synchronize passkeys under its own terms and privacy practices.

Console and FSID information

RexiMemo can handle Flipnote creator FSIDs linked to your account, Primary Console status, console names, device models, first/last-seen information and temporary identity information used while signing in or linking a console.

Real-console sign-in can involve sending a small Flipnote so RexiMemo can verify the creator identity. RexiMemo can also identify whether a connection appears to be from a supported emulator so that emulator sessions can be handled differently from real-console identity sessions.

When a full Flipnote is posted from a supported emulator, RexiMemo can record that upload origin on the Flipnote. For emulator-posted copies, RexiMemo uses the account's current RexiMemo username and real Primary Console FSID as the posted creator identity while retaining the source Flipnote's original creator name and FSID as spin-off attribution.

Session, browser and network information

RexiMemo can handle session identifiers, account association, session times, IP addresses, browser/device information supplied by the client, linked-console information and security/session history.

When you use a RexiMemo account in a browser, a separate browser cookie helps enforce account suspensions. RexiMemo stores a hash of that random cookie alongside the accounts used in the browser, not the cookie value itself. While an associated account is suspended, the same browser cannot create another account. Verified console FSIDs can also be recorded with suspensions so the same DSi identity cannot be used to evade them.

When a DSi uses RexiMemo’s network compatibility services, RexiMemo can also receive DNS requests, connection information and technical request information needed to route, authenticate, troubleshoot and operate the Service.

API keys and API activity

When you generate a personal API key, RexiMemo shows the complete main key at creation time and stores a cryptographic hash of the key together with limited metadata such as a short prefix, creation time, expiry time and recent-use time. RexiMemo also generates a short-lived one-time client login code and stores only a hash of that code. If the code is redeemed, the client receives a separate random bearer credential linked to the parent API key; that credential is also stored only as a cryptographic hash. Generating, revoking or expiring the parent key invalidates credentials linked to it.

API requests can also produce ordinary operational and security information, including the account associated with a valid key, request time, IP address, method, requested path, user-agent or client information where supplied, response status, rate-limit state and abuse/security signals. RexiMemo may use hashed or shortened token identifiers for security and rate-limiting purposes instead of storing a plaintext API key.

Patreon connection and supporter rewards

If you choose to link Patreon for RexiMemo Supporter+, RexiMemo receives your Patreon user and membership identifiers, the Patreon display name made available to the integration, your membership status, current entitled tier identifiers, billing cadence, latest charge date/status and limited trial/gift indicators needed to determine supporter eligibility. RexiMemo requests only the basic Patreon identity scope for this connection and does not request your Patreon email address, payment-card details or bank details.

The temporary Patreon OAuth access token returned while linking is used to verify the connection and is not intentionally retained by RexiMemo after that request. RexiMemo stores a reward ledger containing the Patreon identity, charge date, configured tier and supporter rewards already issued so the same payment cannot award rewards twice and so earned Supporter+ Tickets remain attributable to the correct payment.

Flipnotes and community activity

RexiMemo can store and process uploaded Flipnotes and their associated creator/editor information, titles, descriptions, channels, timestamps, comment settings, public statistics, moderation state and upload-origin classification (for example, original DSi, supported emulator, external encoder, or RexiMemo Flipnote Editor). Flipnotes can contain animation frames, audio and creator metadata. While Flipnotes made with the Flipnote Editor tool technically go through an encoding process when they are prepared as PPM files, RexiMemo processes and records Flipnote Editor as a separate origin from the external Encoder origin.

Flipnote Editor and HD Music: if you create a Flipnote with RexiMemo Flipnote Editor and import eligible Music from a local MP3 or WAV file, RexiMemo can store the original imported MP3/WAV separately from the PPM, along with limited metadata such as the source filename or media type and timing information used to synchronise playback. This separate audio is used to provide HD Music on supported desktop web playback. The PPM keeps its own Flipnote-compatible audio separately for normal PPM playback, downloading and DSi use.

RexiMemo can create thumbnails, avatar images, memo-comment previews and other derived images needed to display or moderate content.

RexiMemo can also handle text comments, memo comments, replies, stars, colored-star balances, favorites, follows, channel activity, notifications, views, downloads, rankings and other community interactions.

Flipnote collaborations: RexiMemo can store which Flipnote a collaboration relates to, the inviting account, the invited collaborator, whether the invitation is pending, accepted or declined, and request/response times. If a collaboration is accepted, the collaborator attribution can be displayed publicly with the Flipnote and can be used when calculating collaboration-related creator statistics or ranking credit.

Blocking: RexiMemo can store which account created a block, which account was blocked and when the block was created. That relationship is used to enforce visibility and interaction restrictions in both directions, suppress relevant notifications, and apply other blocking behavior described by the Service.

For signed-in users, RexiMemo keeps enough per-account yellow-star information to enforce the limit of 10 yellow stars per user per Flipnote.

Recommendations and Watch next

RexiMemo uses information already held for the Service to generate Watch next recommendations. For all viewers, this can include information about the Flipnote currently being viewed and possible recommendations, such as creator, channel, title, description, upload time, views, stars, comments and other community-engagement information.

For signed-in users, Watch next can also use existing RexiMemo activity associated with the account, including follows and recent views, favorites, stars and comments. RexiMemo uses that activity to estimate which creators and channels may be more relevant, to prefer content the account has not already viewed, and to reduce repetitive recommendations. Older activity is given less influence than newer activity, and only a bounded amount of recent interaction history is considered for each recommendation request.

Watch next is produced by deterministic scoring and diversity rules. It does not use AI, does not send your recommendation history to an external AI or recommendation service, and does not create a separate persistent Watch next interest profile. Recommendation preferences are calculated when the page is requested from information RexiMemo already stores for the features described in this Policy. Signed-out viewers receive contextual recommendations without signed-in account-history personalization.

Watch next recommendations are used for content discovery only. They are not used to decide account eligibility, moderation action, bans, suspensions, or other decisions that have legal or similarly significant effects on a user.

Song Finder

RexiMemo can process a Flipnote's dedicated BGM track to try to identify commercially released or otherwise recognizable music. Recognition begins automatically after a Flipnote is uploaded and can also be retried later when a signed-in user views it or when an administrator runs maintenance recognition. Matched music information and correction tools are available to signed-in accounts.

For recognition, RexiMemo extracts the BGM audio from the Flipnote, corrects its playback rate, and creates several short audio excerpts. Those excerpts are sent from RexiMemo's server to the Shazam music-recognition service using the ShazamIO client. RexiMemo does not send the full Flipnote, the viewer's password, API key, browser session, or intentionally the viewer's browser IP address to Shazam as part of Song Finder. Shazam can receive the submitted audio excerpts and ordinary connection or request information associated with RexiMemo's server.

RexiMemo creates Song Finder excerpts temporarily for recognition and does not intentionally save those excerpt files as a permanent audio library. RexiMemo can cache recognition status and metadata for a Flipnote revision, including a matched title and artist, a recognition-service track identifier, consensus/sample counts, timing or sample-rate information, check time, and limited error information. RexiMemo also stores the currently published track title and artist on the Flipnote so the same result can be shown consistently on supported web and DSi views. The Flipnote owner can add, correct, or remove that published title and artist when they have access to Song Finder.

Search

Search terms are processed to return matching creators, Flipnotes, channels and jump codes. Search text can appear in page addresses and can therefore also appear in ordinary browser or server request history.

Moderation and safety information

RexiMemo can keep bans or suspensions, reasons and dates, private moderator notes, moderation incidents, linked evidence, case updates, staff actions and other records reasonably necessary to enforce the Terms, protect users and maintain moderation consistency.

When you submit a Flipnote report, RexiMemo can store the reported Flipnote and its identifiers, the reporter username and account association where signed in, the reason and additional details, evidence links, uploaded image/video evidence, device/browser information supplied with the request, submission time and staff review status. These report records are restricted to staff moderation tools rather than normal public community pages.

RexiMemo can use automated profanity filtering and human moderation. Moderators may review account information, content, linked-console information, session information and relevant diagnostics when reasonably necessary to investigate a report, enforce the rules or protect the Service. Moderators may also classify otherwise-allowed Flipnotes as Sensitive 16+ when their subject, intensity, context or presentation is considered distressing or mature, including certain non-graphic self-harm, suicide-related, injury, blood, violence, horror or medical themes. That classification affects content visibility and age-restricted access. The content rules continue to prohibit realistic/graphic gore and realistic medical-distress depictions, including exposed or detailed veins, muscles, bones, organs, severe wounds, spasms or convulsions, and reenactments of medical emergencies such as heart attacks. Sensitive 16+ does not make prohibited content acceptable.

Diagnostics

When needed to diagnose networking, compatibility, reliability or security problems, RexiMemo may temporarily record additional technical information about connections. Depending on what is being diagnosed, this can include network metadata, DNS traffic, request information and data sent through legacy DSi connections.

Because parts of the DSi service use old, unencrypted networking, diagnostic material from those connections can contain sensitive information sent during the affected request, including account credentials or uploaded content. Diagnostic information is used for troubleshooting and should not be treated as public information.

3. What can be public

Unless an interface clearly says otherwise, you should assume that information intentionally published through RexiMemo community features can be public. This can include:

• username, profile text and avatar;
• uploaded Flipnotes and public creator/editor information, including accepted collaborator attribution and Flipnote upload-origin notices where applicable, including a Flipnote Editor origin notice;
• for a published Flipnote that uses HD Music, the separate HD Music audio needed for supported desktop web playback;
• Flipnote titles, descriptions, comments and memo comments;
• channels and public community activity;
• aggregate views, downloads, stars and other public statistics;
• favorites, followers and following;
• linked FSIDs and Primary status when shown in a Creator’s Room;
• device-model information where the DSi interface displays it.

Other users may download, save, screenshot or redistribute public content outside RexiMemo.

4. Information not intended to be public

The following are not intended to be public through normal RexiMemo community pages:

• password credentials;
• WebAuthn/passkey credential identifiers, public-key verification material and passkey-management metadata;
• full API keys and API authentication credentials;
• full session identifiers;
• IP addresses and browser/device request information;
• temporary sign-in/linking information;
• pending or declined collaboration invitations and their private response records;
• user block relationships and block timestamps;
• private moderation notes and case details;
• submitted report details and uploaded report evidence;
• staff audit information;
• private diagnostic and security logs.

RexiMemo staff may access non-public information when reasonably necessary to operate, secure and moderate the Service, or where disclosure is required by applicable law.

5. How information is received

RexiMemo receives information directly from you when you create an account, sign in, change settings, upload content, import content into Flipnote Editor or interact with the Service. Information is also received automatically from your browser, DSi or emulator when it connects, from metadata contained in Flipnotes, from other users when they interact with you or your content, and from staff when moderation records are created.

6. Why RexiMemo uses information

RexiMemo uses information to:

• create, authenticate and secure accounts, including registering and verifying passkeys;
• keep users signed in and manage sessions;
• authenticate API clients, record API-key status and recent use, enforce rate limits, and investigate API abuse or security incidents;
• link verified DSi identities to accounts and provide console-related features;
• provide DSi network and authentication compatibility;
• host, display, play and manage Flipnotes and comments, including providing Flipnote Editor origin information and HD Music playback where applicable;
• identify music in Flipnote BGM after upload or a later authorized check, cache sufficiently reliable recognition results, and let eligible Flipnote owners correct published track metadata;
• send, receive and manage Flipnote collaboration invitations, display accepted collaborator credit, and calculate collaboration-related statistics;
• apply user blocks, hide affected content or profile information, suppress blocked interactions and notifications, and maintain the relationship controls requested by users;
• provide stars, favorites, follows, channels, notifications, search, rankings and statistics;
• personalise Watch next recommendations using the current Flipnote, community signals and, for signed-in users, existing RexiMemo interaction history;
• enforce feature limits, age-restricted feature eligibility and community rules;
• remember user preferences;
• moderate content, investigate abuse and keep appropriate safety records;
• diagnose networking, compatibility, reliability and security problems;
• operate, test, improve and develop RexiMemo during the Open Beta;
• comply with applicable legal obligations and valid requests.

7. Legal bases where required

Where data-protection law requires a legal basis, RexiMemo may rely on:

• Contract / requested service for information needed to provide features you request;
• Legitimate interests for operating and securing the Service, preventing abuse, moderation, diagnostics and improving the Open Beta, balanced against users’ rights;
• Legal obligation where processing is required by law;
• Consent where RexiMemo specifically asks for consent for an optional use and consent is an appropriate basis.

RexiMemo does not use consent as a blanket justification for all core Service processing.

8. Age requirement

RexiMemo is for users aged 13 and over only. Children under 13 may not create an account, sign in, link a console, upload content or otherwise use the Service, even with parental permission.

RexiMemo does not require every user to provide a date of birth. A Date of Birth is requested only when an account chooses to use an age-restricted feature such as the Sensitive 16+ channel. The stored date is private, is used to calculate age eligibility, and is not displayed publicly. Sensitive 16+ eligibility is determined automatically from the Date of Birth supplied to RexiMemo; this calculation is an access-control check and is not independent identity or age verification. Users may correct a stored Date of Birth once through Settings after the initial save; further corrections require support. If we reasonably believe an account is being used by a child under 13, it may be suspended, terminated or restricted as appropriate.

Do not publish your home address, school, phone number, precise location, passwords or other sensitive information in public content.

9. Cookies and web sessions

RexiMemo uses an essential web-session cookie to keep users signed in and protect account actions. RexiMemo also uses an appearance cookie to remember the selected web theme for signed-in users (Dark, Light, Cosmos, Classic, or Sudotheme when that private theme has been specifically granted to the account). If you change the language inside the Support Center, a small support-language preference cookie scoped to /support remembers whether you selected British or American English.

These cookies are used for RexiMemo functionality and preferences, not advertising. RexiMemo does not currently use advertising cookies, targeted-advertising trackers or third-party analytics.

10. Third parties

RexiMemo can rely on third parties that are necessary to operate parts of the Service:

• DNS requests that RexiMemo does not answer itself can be forwarded to an upstream DNS provider;
• the web Flipnote player can load a playback library from a third-party content-delivery provider, which can receive ordinary browser connection information when your browser requests that library;
• RexiMemo pages that display the community widget can request the public RexiMemo Discord server widget from Discord to show current community presence information. When that widget data is requested, Discord can receive ordinary browser connection information such as your IP address, browser information and request time;
• when a Flipnote report is submitted, RexiMemo stores it in the moderator portal and can also send a staff alert through the RexiMemo Discord bot. That alert can include report details, the reported Flipnote information, reporter information supplied with the report, evidence links and uploaded evidence files. Discord therefore processes that copy under its own terms and privacy practices;
• if you opt in to Discord notifications, RexiMemo creates or reuses a private channel in the official RexiMemo Discord server for your linked Discord account and sends copies of your RexiMemo notifications there. RexiMemo stores whether delivery is enabled and the channel identifier used for delivery. The notification messages copied into Discord are also processed by Discord under its own terms and privacy practices;
• if you choose to link Patreon for RexiMemo Supporter+, your browser is redirected to Patreon for authorization and RexiMemo then uses Patreon's API and signed webhooks to verify the membership and later membership/payment-status changes. Patreon processes membership, payment and account information under its own terms and privacy practices. RexiMemo does not receive the payment-card or bank credentials used to pay Patreon;
• when Song Finder performs recognition after upload or a later check, RexiMemo sends short BGM audio excerpts to the Shazam music-recognition service from RexiMemo's server. Shazam can process those audio excerpts and server-side connection/request information under its own terms and privacy practices. The Song Finder browser page does not contact Shazam directly for recognition; ShazamIO is the client software RexiMemo uses on the server to make the recognition request;
• hosting, network, certificate, backup and other infrastructure providers can process information necessary to host, route, secure or deliver the Service.

RexiMemo does not sell personal information and does not use personal information for targeted advertising.

11. Diagnostic information

RexiMemo may enable additional diagnostic logging or network capture when necessary to troubleshoot difficult DSi, networking, compatibility or security problems. Diagnostic material can include IP addresses, DNS requests, protocol/request information, session information and data sent through the affected connection.

The legacy DSi service includes unencrypted traffic. If diagnostics are active during such traffic, information sent through that connection can be visible in the diagnostic material. This can include usernames, passwords, comments or uploaded Flipnotes. For this reason, use a password unique to RexiMemo and do not send unrelated confidential information through the DSi connection.

Diagnostic information is restricted to operational use and is retained only for as long as reasonably needed for troubleshooting, safety, security or related legal obligations.

12. Security and legacy DSi networking

RexiMemo uses reasonable account, session and web-security measures designed to protect the Service. The public website uses HTTPS. Where supported, WebAuthn passkeys provide public-key authentication without sending the passkey’s private key to RexiMemo. However, no system is perfectly secure.

Unmodified Flipnote Studio depends on obsolete Nintendo/Hatena-era networking, and parts of the DSi connection do not provide modern encrypted transport. Information sent over those legacy portions of the connection may be visible to someone able to observe the network path. Use a unique RexiMemo password and do not reuse an important password.

13. Retention

RexiMemo does not use one universal retention period for every category of information. Information is kept for as long as reasonably necessary to provide the relevant feature, protect users and the Service, maintain moderation consistency, resolve disputes, diagnose problems or meet legal obligations.

Active sessions expire or end when logged out or revoked, while limited session history may be kept for account security. Registered passkey records are generally kept while the passkey remains attached to the account and can be removed through the available account controls; limited security records may remain where reasonably necessary. Personal API keys expire automatically or end when revoked; RexiMemo can retain limited key metadata and API request/security records for as long as reasonably needed to operate the API, enforce limits, investigate abuse, diagnose incidents, and protect the Service. A linked Patreon connection is generally kept until it is unlinked or the account is removed, while Patreon reward-ledger records can be retained after unlinking so already-issued transferable rewards are not duplicated and earned Supporter+ Tickets remain attributable to the correct RexiMemo account. Song Finder recognition caches can remain for the relevant Flipnote revision or until they are replaced, cleaned up or no longer reasonably needed; these caches can contain recognition status and match/diagnostic metadata, but RexiMemo does not intentionally retain the temporary Song Finder audio-excerpt files after recognition. HD Music companion audio and its timing metadata can be retained with the associated staged or published Flipnote for as long as reasonably needed to provide that feature, and can remain for a limited period in backups or other operational copies after the associated content is removed. Collaboration records can remain while needed to provide the collaboration, preserve the resulting attribution/statistics, resolve disputes or maintain content integrity. Block relationships are generally kept while the block remains active and are removed when the block is removed, subject to limited backups, security records or legal obligations. Public content and related community records may remain until deleted, removed or no longer needed. Moderation records, including report submissions and report evidence, may be retained longer where needed to investigate abuse, identify repeat behavior, preserve evidence, maintain moderation consistency or resolve disputes.

Watch next does not create a separate persistent recommendation profile. Its recommendation preferences are calculated on demand from existing content and account-interaction records. Those underlying records, such as views, favorites, follows, stars and comments, follow the retention rules that apply to the feature or record itself rather than being kept under a separate Watch next retention period.

Deleting or hiding content does not necessarily remove every associated copy immediately. Backups, caches, moderation evidence, diagnostic records and copies made by other users can remain for a period after the public content is removed.

14. Deletion and public copies

Deleting or hiding a public post does not guarantee deletion of screenshots, downloads, reposts or other copies made by users. RexiMemo may also retain limited information where reasonably necessary for security, moderation, backups, diagnostics, legal obligations or the rights of other people.

For an account-data or deletion request, email rekunote@gmail.com.

15. Your choices and controls

Depending on the feature, signed-in users can change profile information, appearance and notification preferences, manage linked consoles and Primary Console status, change passwords, add or remove passkeys, review or revoke sessions, manage favorites/follows, block or unblock users, manage collaboration invitations or accepted collaborations where applicable, mark notifications read and edit or delete certain owned content.

Watch next uses signed-in account interaction history only while recommendations are being generated for a signed-in viewer. If you use RexiMemo while signed out, Watch next can still recommend content from the Flipnote being viewed and general community signals, but it does not use a signed-in account's interaction history for that request.

You can stop using RexiMemo and log out at any time.

16. Your privacy rights

Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection or a portable copy of personal information, and to withdraw consent where processing is based on consent. These rights can have legal exceptions, including where information must be retained for security, moderation evidence, legal obligations or another person’s rights.

To make a request, email rekunote@gmail.com. RexiMemo may need to verify that you control the relevant account before acting on a request. Where applicable, you may also have the right to complain to your local data-protection authority.

17. International processing

RexiMemo can be accessed internationally, and service providers used to operate RexiMemo may be located in a different country from you. Where applicable law requires safeguards for international transfers, RexiMemo will use the safeguards required by law.

18. Open-source and third-party software

RexiMemo publishes a reduced public edition called RexiMemo Open Source Edition (OSE). The live production service is not fully open source, and OSE does not contain production credentials, private keys, production data, or the production-only security, privacy, identity, moderation and operations systems used by reximemo.net.

Publishing source code does not give repository contributors or the authors or maintainers of third-party software access to RexiMemo user information. They do not receive or control RexiMemo user information merely because their software is used or because OSE is public. Third-party software remains subject to its own licences and privacy practices where applicable.

19. Changes to this Policy

We may update this Privacy Policy as RexiMemo changes. The current version will be published here with an updated effective date. If a new use of personal information materially differs from what users were previously told, RexiMemo will make reasonable efforts to provide notice before or when that processing begins.

20. Contact

For privacy questions, account-data requests, rights requests or complaints, email rekunote@gmail.com.