A useful distinction. Posts and their media are made for sharing. Normal chat text is handled by our servers. Secret direct text chats use client-side encryption, but metadata is still processed. Stories are limited to you and current followers for 24 hours in the app.
01 / CONTACT
Who handles your data
Inventar Studio operates Sealz and is the contact for questions about personal data handled by the service. Write to contact@sealz.net. This notice covers the Sealz app and the public sealz.net website. It is written for the current invite-only beta and will be revised if the product or its data handling changes materially.
02 / THE INFORMATION
What we collect
Account and invitations
Your email address, one-time-code records, account ID, username, profile photo, status, bio, website, and acceptance of the current Terms, Privacy Policy, and age-20 confirmation. When someone invites you, we keep the inviter, invited email, invitation status, and related dates. A user can invite up to five distinct addresses.
What you share
Posts, comments, photos, videos, hashtags, mentions, reposts, quote posts, follows, reactions, Stories, and their activity records. We keep information needed to show these features, such as who posted or viewed a Story and when.
Messages
Normal chat message text, attachments, recipients, and conversation activity are processed on our servers. For secret direct text chats, the app encrypts message text before it reaches our servers; we still process routing and account metadata, timing, membership, and encrypted content. Secret chats do not currently support attachments.
Devices and service activity
Push-notification registration tokens and installation identifiers if you enable notifications, plus technical information involved in delivery, security, errors, and support. The public website and API may generate ordinary request and security logs through our hosting and network providers.
Local drafts
Account-scoped drafts and queued posts are kept on your device until submitted or cleared; signing out does not publish or necessarily erase that account’s draft. Saving the full draft does not itself upload the draft text, but typing @ or # suggestions sends the active search fragment to our service, and GIF search sends a related request. A send attempt may upload chosen media before the whole post succeeds, and partial uploads can wait for technical cleanup.
03 / THE REASONS
Why we use it
We use the information above to verify invited accounts, provide feeds, profiles, search, social interactions, chats and Stories, deliver transactional email and optional push notifications, keep the service working and secure, respond to reports and support requests, and meet applicable legal obligations.
Some information is necessary to provide the feature you request: without an invited email we cannot create an account, for example, and without message routing details we cannot deliver a chat. Optional device permissions and push registration are used only when you choose those features. Where applicable law requires a separate consent for a particular use, we will ask for it. Accepting this notice at registration is not a blanket consent to unrelated uses.
04 / AUDIENCE MATTERS
Who can see what
Other members can find your profile, posts, reposts, quotes, comments, and public interactions through Sealz. Post-media links can be reachable without logging in and may be cached by a delivery network. If someone reposts or quotes you, their activity may remain visible even if your original later appears unavailable. Other people may keep screenshots or copies outside Sealz.
Stories are intended for you and people who currently follow you. Access is checked when a Story or its media is requested; it becomes unavailable through Sealz 24 hours after creation. Viewers can still capture what they saw. Normal chat attachments use an authenticated private media route and are intended for current conversation members. Secret direct text chats have the narrower encryption boundary described above; do not assume every chat is end-to-end encrypted.
System push notifications use generic text and identifiers. Detailed activity and, where eligible, media previews are fetched inside the authenticated app. A normal-chat preview may use a protected URL; private chat media is not published as public post media.
05 / SERVICE PARTNERS
Providers and locations
We use service providers to run Sealz. Our application infrastructure is hosted with Vultr in Singapore. Cloudflare provides network delivery, the public website Worker, and private R2 object storage; its network may cache public media. Resend handles transactional account and invitation email. Google Firebase Cloud Messaging delivers optional push notifications to registered devices. If you search or load GIFs, Giphy may handle GIF requests or media delivery.
These providers may process information in locations outside your country. The categories shared depend on the feature: email addresses and message templates for transactional mail; object files and delivery metadata for storage and network services; device tokens and generic notification identifiers for push; and GIF search or media requests for Giphy. We may also disclose information where legally required or reasonably necessary to protect rights and safety. We do not give a provider access to a secret chat’s decrypted text as part of server message routing.
06 / YOUR DEVICE
Device permissions
Photos, camera, video, and notification permissions are optional and requested when a related feature needs them. You can change permissions in your device settings, though the related feature may then stop working. Sealz does not require access to your contacts list or precise location for the features described here.
07 / TIME & REMOVAL
Retention and deletion
One-time login codes are short-lived; the current code window is about five minutes. Invitation links expire after seven days, although invitation and registration records may be kept longer to administer the invite limit and account. Stories stop being available through the app after 24 hours; background cleanup removes their stored media later. Expiry is a visibility rule, not an assurance that every technical copy has already disappeared.
Other account, post, chat, notification, and service records are kept while needed to provide the service, handle requests and safety issues, or satisfy applicable obligations. Exact periods for every operational log or backup are not fixed in this notice. Deleting content or closing an account can take time to propagate through caches and technical copies; law, disputes, and the rights of other people may limit immediate erasure. Content another person copied outside Sealz is not under our control.
08 / YOUR SAY
Your choices and rights
You may edit available profile fields, stop using optional permissions or push notifications through your device, and request help with access, correction, deletion, restriction, objection, portability, or withdrawal of consent where applicable. Email contact@sealz.net with enough detail to identify the account and your request. We may need to verify your identity before acting, and some requests are subject to statutory conditions or exceptions, including the rights of others and legal obligations.
Thai law may provide additional rights and complaint routes. The Thai Personal Data Protection Act (unofficial English translation) describes notice, access, objection, erasure, restriction, and correction rights. This policy describes our current service; it does not claim that every request will have the same outcome under every law.
09 / KEEPING CURRENT
Security and updates
We use account authentication and access checks for private media and Stories, plus transport and operational safeguards appropriate to the service. No online service can promise absolute security. Please protect your email account and device, and tell us if you suspect misuse.
We will update this notice when the product or data handling changes. The version and date above identify this edition. For questions about this notice, reach Inventar Studio at contact@sealz.net.
Last updated 27 September 2026 · Version 2026-09-27