Help with connections, protected comments, and your data.

NoiseOff supports official connections for Instagram, Threads, YouTube, and Facebook. Instagram requires a Business or Creator account. YouTube requires a Google account with an accessible YouTube channel. Facebook works with eligible Pages, not a personal-profile inbox, and requires the Page access and permissions shown in the app. Provider review or testing restrictions can limit who can connect during a pre-release period.

Return to NoiseOff and open the platform connection screen. A provider may have denied a required permission, returned an account without an eligible channel or Page, or limited the NoiseOff app to approved testers. Try the reconnect action once, confirm the intended account, and approve the permissions shown. If it still fails, send support the platform, approximate time, iOS version, and the exact non-sensitive message shown in NoiseOff.

Read-only means the provider did not grant the management permission or Page role needed for hide or restore actions, or the item type does not support that action. Use the add-management-permission or reconnect action shown on that platform’s detail screen. NoiseOff cannot elevate your provider role. Threads nested replies and mention posts remain read-only even when eligible top-level reply management is available.

NoiseOff imports through official provider APIs after connection, when the app launches or returns to the foreground, and when you request a refresh. It is not guaranteed background real-time monitoring. Provider delays, rate limits, permissions, and temporary outages can also delay an import.

Quietly handled describes how NoiseOff keeps harmful original text out of the everyday NoiseOff feed. It does not automatically mean the source-platform comment is hidden. A source hide or restore occurs only when you explicitly choose that action, the target is supported, and the provider confirms it. Check the platform connection screen if the action remains pending or fails.

During an authorized import, plaintext briefly passes through an authenticated SW Cosmos service and is not written to the NoiseOff database. NoiseOff makes a best-effort attempt to mask common identifiers before sending the masked text to OpenAI’s moderation API for a safety signal. The returned envelope contains hashes, flags, and scores rather than the original or masked text. Your iPhone verifies the envelope, combines it with local rules and your settings, and makes the final display decision. Masking reduces exposure but cannot guarantee that every identifier or contextual clue is removed.

NoiseOff is being prepared for iPhone and requires iOS 17 or later. The app interface is available in English and Korean. The screening path is designed for multilingual comments, but accuracy can vary with language, context, sarcasm, and coded wording; uncertain or failed results are handled protectively rather than assumed safe.

You can choose seven days, thirty days, ninety days, or until deleted, subject to the platform’s stricter rule. A Threads evidence hold may remain until you remove it. Instagram and Facebook records follow the selected retention period. YouTube API records, including evidence, are deleted no later than 30 days after collection. Earlier manual deletion always takes priority.

Open the protected record and choose to reveal the original. NoiseOff requires a deliberate confirmation and, when available, device authentication. Recording or mirroring can relock protected content. Do not send protected originals to support unless support has provided a secure method and you have removed information you do not want to share.

A user-created evidence bundle can include PDF, image, JSON, and checksum files based on the encrypted NoiseOff record and source fields returned by the platform. Those exported files are plaintext outside NoiseOff, so save and share them carefully. They are not a certified forensic image, certified legal evidence, or legal advice; preserve the provider original and consult a qualified professional when needed.

Open Settings → Privacy & Storage → Delete NoiseOff account and confirm. NoiseOff then requests revocation of connected-provider access and removes the associated stored credentials, NoiseOff cloud records, anonymous authentication account, local imported records, settings, pending synchronization data, provider sessions held by the app, temporary evidence files, and the device-only encryption key. For Facebook, NoiseOff removes its encrypted Page token; Meta may keep the account-level app permission until you remove NoiseOff in Facebook Settings → Apps and Websites. Keep the app open until it confirms completion. Files you previously exported or shared are outside NoiseOff and must be deleted from their saved destinations separately.

Reopen NoiseOff and use the deletion recovery screen to retry. If a provider or network step cannot be confirmed, NoiseOff restricts access to the regular app and keeps only the data needed to finish safely rather than reporting false completion. An incomplete retry receipt may retain the anonymous Supabase authentication UUID, a one-way HMAC of the random deletion token, status, and timestamps for up to 60 days. After deletion completes, the retained receipt is identifier-free and contains only the token HMAC and completion timestamps for up to 60 days. If retry still fails, contact info@swcosmos.com without sending passwords, codes, access tokens, comment text, or device passcodes.

No. Full account deletion requests revocation for connected Instagram, Threads, and YouTube credentials and removes the stored Facebook Page token as part of the deletion flow. You can still use Disconnect when you want to stop one connector without deleting your NoiseOff account. Because Meta may retain Facebook’s account-level app permission, remove NoiseOff in Facebook Settings → Apps and Websites if you want to clear that permission too. Neither disconnecting nor deleting NoiseOff changes content or deletes accounts that remain on the source platform.