Privacy
Sending an SMS means handling someone's phone number, so this page says plainly what we store, for how long, and who can see it. We process personal data under Georgian personal data protection law. Two roles matter here: you are responsible for the recipients you choose to message, and we process those messages on your behalf.
What we store about the people you message
| Data | Why | How long |
|---|---|---|
| Recipient phone number | To deliver the message and answer status questions | Kept with the message record until you delete your account |
| Message text | To support delivery and diagnose failures | Encrypted at rest and erased after 30 days |
| Which template and language rendered the message | To say on your dashboard what kind of SMS it was, once the text is erased | Kept with the message record until you delete your account |
| Delivery status and timestamps | To report honest delivery state | Kept with the message record until you delete your account |
| Verification record: the number, the outcome and the attempts, with their times | To check a code NOTIFY made, and to answer questions about a check | Deleted after 30 days |
| Verification code | NOTIFY makes it and sends it by SMS | Never stored. We keep only a keyed hash of it (an HMAC) until the verification ends (at most about an hour after the code expires), and the text of the SMS that carries it is never stored either |
Our API never returns a full phone number, and neither does the dashboard's message log:
both show a masked form such as +9955••••••67. Message text is never returned at all, and neither is a
verification code. Our logs show numbers only
in that masked form, and never message text. Messages sent with a test key are never
delivered, but they are stored in the same way. If nobody claims the test project they were
sent from, they are deleted 30 days after they were sent.
What we store about your team
A project's team alerts go only to numbers its owner added on the dashboard and confirmed with a code we texted to the number: the person holding the phone reads the code to the owner, which is how they agree to receive the alerts. You add to your team only people who agreed; you decide whom to add, and we hold these numbers for you, as we hold every recipient's number.
| Data | Why | How long |
|---|---|---|
| The team member's phone number, and the name you give them, if any | To send the alerts the person agreed to receive, and to tell your team apart | 24 hours while it waits for its code; once confirmed, until you remove it, the person asks us to, or you delete your account |
| Whether the number is confirmed, and when it was added and confirmed | The time of confirmation is the record of the person's agreement | As long as the number |
| The confirmation code | NOTIFY makes it and sends it by SMS | Never stored. We keep only a keyed hash of it (an HMAC) until the number is confirmed or the code ends (at most about an hour after it expires), and the text of the SMS that carries it is never stored either |
The alerts themselves, and the code SMS, are messages like any other, and are kept as the first table says. The dashboard shows a team member's number masked, never in full, and our logs only ever show it masked. Anyone who no longer wants a project's alerts can write to contact@n0t1fy.dev from anywhere: we remove the number from every team it is on, and tell each project's owner.
What we store about you as a developer
- Your sign-in identity: the verified email address and the account id that GitHub or Google gives us when you sign in. We use the email address for support and service notices only. We do not store passwords, because we do not use them.
- Your sign-in sessions: stored only as a one-way digest of the session token. A session ends when you sign out, or after 30 days.
- Your project: its name, its credits, and its usage.
- Your API keys: stored only as a one-way hash. We cannot read your key, recover it, or show it to you again after it is created.
The internet address your requests come from is used only in memory: to limit how many instant test keys one address can request, and to notice one address sending many requests with invalid API keys. We do not store it, and it never appears in our logs or alerts. Railway, which hosts the service, keeps its own request logs, and they include that address.
Who else sees this data
- GoSMS.ge, our Georgian delivery provider, receives the recipient number and the message text, a verification code included, because it delivers the message.
- Railway runs our servers and our database.
- GitHub or Google, whichever you sign in with, tells us your verified email address and account id. Their own privacy policies cover what they do.
- Google Workspace hosts our email, so it holds the messages you send to contact@n0t1fy.dev.
- Resend delivers our operator's alert emails about unusual traffic and failed backups. An alert names a project and the non-secret start of an API key, with counts; it never contains phone numbers, message text or internet addresses.
- Backblaze stores our database backups. They are encrypted before they leave our servers, with a key only the operator holds, so Backblaze cannot read them.
We do not sell personal data, and we do not use your message content for advertising or for training machine-learning models.
Security
- All traffic is encrypted in transit (HTTPS).
- Message text is encrypted at rest with a key held only in our deployment configuration.
- API keys are stored only as a one-way hash; the plaintext exists only in the moment it is shown to you.
- A verification code is never stored: only a keyed hash of it, until the verification ends, and at most about an hour after the code expires. Each code works for 10 minutes and five attempts, once.
- Access to production is limited to the operator.
- The database is backed up twice a day. Each copy is encrypted before it leaves our servers and is deleted within 14 days.
- We watch for unusual traffic: a sudden rise in a project's or an API key's live sends, repeated requests with invalid API keys, the per-minute rate limits hit again and again, and verification codes that look guessed. The operator is alerted and contacts the project's owner where there is one; nothing is blocked or suspended automatically.
Deleting your data
Write to us from the email address you sign in with, so we know the request is yours, and we delete your account: your email address, your GitHub or Google account id, your sessions, and your project's message and verification records, with every recipient number in them, and your team's numbers and names. Your API keys stop working at once. We keep only an anonymous record of the project, its id and its credit counts, so that free credits stay counted correctly; it holds no personal data. Data we delete or erase stays in the encrypted backup copies made before, until those copies are deleted, at most 14 days later.
If one of your recipients contacts us directly about their data, we will refer them to you, since you decided to message them — but we will act on a lawful request either way.
Contact
Data questions and deletion requests: contact@n0t1fy.dev.