Who this policy covers
This policy describes how Wrote handles information when you use Wrote, wrote.sh, and our support services. Contact contact@wrote.sh or choose Privacy & data on our contact form with questions or requests.
Information we handle
- Account details: your confirmed email or phone, user ID, username, profile name, photo, bio, and settings. Email is the available sign-in method while SMS is paused.
- Content and relationships: messages, uploads, posts, stories, highlights, comments, reactions, follows, group memberships, and reports you submit. Content visible to others can be copied or reshared by them.
- Device and service data: device/session identifiers, push tokens, app/device details, connection information, security events, and limited technical records needed to run the service. Location is used only for a feature you enable and with the permissions that feature needs.
- Purchases: product and transaction identifiers, entitlement status, and your Grams ledger. Apple processes App Store payment details; the app does not receive your full payment-card information.
- Support: your name, email, optional username, selected department, message, and a reference number. Do not send passwords, one-time login codes, payment-card numbers, or unnecessary sensitive information.
Why we use this information
We use information to create and secure accounts, deliver content and notifications, maintain the features you choose, process entitlements, prevent abuse, respond to support and legal requests, and diagnose service failures. We request device permissions in context; you can change them in iOS Settings.
Visibility and communication privacy
Your profile and content follow the audience controls available in the app. Public posts, profiles, and public-channel content can be visible to others. Group participants receive content shared with that group. Stories you add to highlights remain available until removed, subject to your audience settings.
Do not assume every Wrote feature or uploaded file is end-to-end encrypted. Protection depends on the feature and the app’s explicit security indicators. Publicly shared content, service metadata, abuse reports, and recipients’ own copies can still be processed or retained. Avoid sharing sensitive files unless the feature’s access controls meet your needs. No system can prevent a recipient from taking a screenshot or making a copy.
Public profiles and public group/channel details may appear on wrote.sh links, including the display name, username, biography, photo, verification badge and public member count. Private profiles and direct/private chat URLs do not expose these details. A valid private group invitation allows its holder to preview the group name, photo and description before joining; do not post private invitation links publicly.
Service providers and optional features
Wrote uses Supabase for account, database, and storage operations, PHP hosting for wrote.sh, and Apple services for supported App Store transactions and push delivery. Resend is the selected provider for account and website-support email when mail delivery is enabled. Each provider receives the information needed for the feature it supplies. We do not send your message history to an email provider to deliver a sign-in code.
Optional integrations, when enabled and disclosed in the app, can include LiveKit for calls, Tenor for GIF search, and an AI provider for requests you choose to submit. Review the in-app notice before sending content to an optional provider. Only submit content you intend to share with the provider identified in that notice.
We may disclose relevant records where legally required, to address a credible safety or security issue, to enforce our rules, or as part of a business transfer with appropriate protections. We do not publish support messages or make the contact-submission database publicly readable.
Website cookies and technical records
The website uses essential session cookies for contact-form security and staff sign-in. Staff sign-in uses a verified work email, a one-time email code or link, and an account password when enabled. Cookies are not used for advertising. This website does not install advertising pixels, cross-site analytics, or third-party fonts. Hosting infrastructure can record ordinary request logs. The contact system uses a keyed hash of your network address for rate limits rather than storing the raw address in support tickets.
Retention and deletion
We keep account information and content while needed to provide the service and follow your instructions. Archives and highlights persist until you remove them or delete the account, subject to operational cleanup. Necessary security, transaction, dispute, and legally required records may be retained for the applicable purpose. Backups and recipients’ independent copies may remain for a limited period or under their control.
Contact-form records and their delivery queue are automatically removed after 90 days when the scheduled mail worker runs. Support emails and necessary case records may be kept longer while resolving your request or meeting legal obligations. Rate-limit records are regularly cleared. Contact us for further information about records retained for your request.
Staff sign-in codes become unusable after expiry or successful verification. Codes are removed from the active challenge after use, and expired challenge records are cleaned up as new sign-in requests are processed. Administrative actions are recorded to investigate misuse and support moderation accountability.
Your choices and requests
Use the app’s controls to change profile visibility, mute notifications, block/report accounts, and remove content. You can start account deletion inside Wrote under Settings > Privacy and Security. See the Account deletion page for details. You can also contact us about access, correction, deletion, a copy of your data, or other rights available in your region. We may need proportionate proof of account ownership before responding.
If processing relies on your consent, you may withdraw it without changing the lawfulness of earlier processing. You may have the right to object, restrict processing, or complain to your relevant privacy authority. We assess requests according to applicable law and explain any lawful limitation.
Age and international use
Wrote is intended for people who meet the minimum age shown in our Terms and the requirements of their region. If you believe a child has provided information in violation of those requirements, contact us so we can investigate.
Our providers may process information in countries other than yours. Contact contact@wrote.sh to ask where information for your account is processed or to request information about applicable international-transfer safeguards.
Changes to this policy
We update this page when our practices change, and identify the effective date below. Material changes that require notice or consent will be communicated through an appropriate channel before they take effect.