Data we collect
You provide message data when you use Sejiwo. Your login provider supplies account data. If you are a recipient, the message writer provides your email address.
- Account data: your email address, profile name, account identifier, and login session.
- Message data: message text, recipient email addresses, reminder intervals, and delivery dates.
- Service records: reminder dates, delivery attempts and results, and unsubscribe settings.
- Request data: hosting providers can process your IP address, browser details, and request logs when you use the service.
How we use your data
We use account data to check your login and give you access to your saved message. We use message data to store your choices, send reminders, and deliver your message.
We use service records to manage delivery attempts, apply unsubscribe requests, and find errors. When you enable Telegram, we also use account identifiers to prevent conflicting account links.
Optional Telegram features
When you link Telegram, Sejiwo receives your Telegram identifier and verified phone number. It stores your account and chat identifiers, reminder choice, and a protected hash of the phone number. The account record does not store the phone number itself.
A recipient must open a private link and press Start before the bot can deliver messages. Sejiwo then links the recipient email address to their Telegram chat identifier.
Telegram bot chats do not use end-to-end encryption. You can stop Telegram reminders or unlink your account in Account settings. You can remove recipient links in Delivery settings. A recipient can send /stop to the bot. These actions do not stop email delivery.
Message protection
Saved message text is encrypted in the database. With standard storage encryption, the service can decrypt the text to display it to you and send it to your recipients.
If you turn on message encryption before saving, your browser encrypts the message text before it is sent to Sejiwo. The password stays in your browser and is not sent with the saved message. Recipients need that password to read the text. Keep a separate copy and share it with them through a separate channel.
Password encryption protects message text. It does not hide account data, recipient addresses, or delivery settings. No storage or delivery system can guarantee complete security.
Data in your browser
Sejiwo uses local storage for your login session and message password. It uses session storage for draft text, recipient addresses, and temporary Telegram login data. Login providers can also use cookies on their own pages.
Draft text can remain readable in browser storage, even when the saved message uses password encryption. The Hide control only hides text on the screen.
Signing out clears the local login session, message password, and draft. You can also clear site data through your browser settings. Keep a copy of your message password before you clear it. Clearing browser data does not delete your saved message or stop delivery.
Storage and your choices
Sejiwo keeps saved messages, recipient details, and delivery records for the scheduled service. A message is not automatically deleted after delivery. Signing out or unlinking Telegram does not delete your saved message.
You can sign in to change your message, recipients, and timing. A recipient can use the unsubscribe link in an email to stop that message. Telegram delivery can be stopped separately with /stop.
You can request access, correction, or deletion of your data through the contact method below. There is no account deletion control on this website. Copies already sent to recipients or delivery providers cannot be recalled through Sejiwo.
Contact and policy changes
For a privacy question or data request, use the Sejiwo project issue page to ask the maintainer for a private contact method. Do not include message text, passwords, login tokens, or personal account details in a public issue.
We can update this policy when the service changes. The date above shows the last update.