Privacy Policy

What changed since edition 7

42 lines added, 20 removed

1. −Removed: Last updated 14 October 2026.
2. +Added: Last updated 22 October 2026.
3. Summary
4. −Removed: We collect the minimum needed to run the service: an email address, what you ordered, what you paid, and the addresses you connected from. We keep the messages your numbers receive so we can show them to you. We do not sell personal data. We do keep records that identify an account responsible for abuse, and we hand those over when properly asked.
5. +Added: We collect the minimum needed to run the service: an email address, what you ordered, what you paid, and the addresses you connected from. We keep the messages your numbers receive so we can show them to you. We do not sell personal data. We do keep records that identify an account responsible for abuse, and we hand those over to platforms and authorities when lawfully asked — see our Terms.
6. What we collect
7. −Removed: Account data — your email address, a hashed password (we never store the password itself), and an optional display name.
8. −Removed: Order data — the numbers issued to you, the service and country, timestamps, and the messages those numbers received.
9. +Added: Account data — your email address and an optional display name. You sign in with a one-time email code or a passkey through Atlas, so we hold no password.
10. +Added: Order data — the numbers, rentals and email accounts issued to you, the service and country, when each was issued, renewed and ended, when each code arrived, and the messages those numbers received.
11. Financial data — your balance, a ledger of every credit and debit, and the blockchain addresses and transaction ids of deposits. Deposits are pseudonymous; we do not collect card or bank details.
12. −Removed: Technical data — IP address and user agent at sign-up, sign-in, and order, recorded in a tamper-evident log.
13. −Removed: Referral data — if you signed up through someone's referral link, which account referred you. They see a masked version of your email address and the commission your deposits earned them; nothing else.
14. +Added: Technical data — the IP address and user agent (browser or device) at sign-up, sign-in, sign-out, each order, rental and renewal, and each API key change, plus which API key made each API call. These are recorded in a tamper-evident, hash-chained log, so a record cannot be altered or removed later without that being detectable.
15. +Added: Referral data — if you signed up through someone's referral link, which account referred you. They see a masked version of your email address and the commission your first deposit earned them; nothing else. Referrals are tracked for us by Referally, our processor for the referral programme. When you sign up, Atlas (which runs our sign-in) tells Referally your account id, your email address, the referral code you arrived with (if any), when you signed up, the IP address and browser you signed up from, and Atlas's assessment of whether the sign-up looks automated or fraudulent, so a referral can be credited and fake ones refused. Referally then holds those and, if you deposit, the amounts of your deposits. Every account can refer others, so it also holds you as a referrer with your own referral code.
16. We do not ask for identity documents, a real name, or an address, and we do not run third-party advertising or analytics trackers.
17. Message content
18. Messages sent to a number you hold pass through our systems so we can display them and extract the verification code. They are stored against your order and are visible to you in your dashboard and in your data export.
19. Treat these numbers as a non-private channel. They are temporary, they are recycled to other customers afterwards, and in the case of numbers labelled shared the inbox is a public web page. Do not have anything sensitive sent to one.
20. −Removed: Message content is excluded from what we disclose in response to abuse complaints — it is not needed to identify who placed an order.
21. +Added: Message content is excluded from what we disclose in response to abuse complaints — it is not needed to identify who placed an order. We disclose it only where a court order or other legal process compels us to.
22. Docs, guides, blog, community and status pages
23. Our documentation, guides, blog, community forum, status page and these legal pages (everything under numestri.com/docs, /guides, /blog, /community, /status and /legal) are hosted for us by Forumulate, which acts as our processor for them.
24. ⋯
25. Infrastructure providers — hosting (including Forumulate, for the pages above), email delivery, and public blockchain explorers used to confirm deposits.
26. Cookie Munch, our processor for cookie consent and for privacy requests: it records the choice you make in the cookie banner, and if you file a request through the form below, it holds that request and passes it to us, to Atlas (which runs our sign-in) and to Forumulate.
27. −Removed: Atlas, which runs sign-in for numestri.com and holds your sign-in identity.
28. +Added: Atlas, which runs sign-in for numestri.com and holds your sign-in identity. It also reports each sign-up to Referally (below), and passes on changes to your email address and name, a ban or its lifting, and the deletion of your account.
29. +Added: Referally, our processor for the referral programme: which account referred whom, each account's email address, the IP address, browser and fraud assessment of its sign-up, and deposit amounts, so it can calculate referral commission and refuse fraudulent referrals (see Referral data above).
30. Chatly, our processor for support chat. It holds the conversations you have with us there, and — if you are signed in when you open the chat — your account id, email address and name, so we know who we are talking to. Its assistant answers from our public docs, guides and legal pages.
31. −Removed: Platforms and law enforcement, in response to a specific, properly-scoped request about a number and a time. We disclose the account, the addresses it used, and when it held the number. We do not disclose message content, and we do not provide bulk access.
32. +Added: Platforms and law enforcement. We comply with subpoenas, court orders, warrants and other valid legal process, and answer specific, properly-scoped requests from platforms investigating abuse of their services about a number and a time. We disclose the account, the addresses and devices it used, and when it held the number; message content only where legal process compels it. We do not provide bulk access. Where the law requires it, or to prevent fraud or serious harm, we may disclose without telling you first, preserve records on request, and report suspected illegal activity to the authorities.
33. We do not sell personal data, and we do not share it for advertising.
34. How long we keep it
35. ⋯
36. Community posts and reader profiles — until you delete them or close your account; closing your Numestri account removes your reader profile too.
37. Sessions — 30 days, or until you sign out.
38. +Added: Legal holds — records covered by a preservation request, a legal hold or an open investigation are kept until it ends, even after the periods above.
39. Your rights
40. Depending on where you live you may have the right to:
41. ⋯
42. An erasure request is refused, with the reason, while your account still has a balance or an order waiting for a code — so that money isn't lost. Ask us for a refund first and the request goes through.
43. Security
44. −Removed: Passwords are hashed with bcrypt. Sessions are carried in signed, HTTP-only cookies and can be revoked everywhere from settings. API keys are shown only to you and can be revoked at any time. The audit log is hash-chained, so alteration is detectable.
45. −Removed: Payment addresses are derived from an extended public key, so no spendable key exists on our servers.
46. +Added: We hold no passwords: sign-in is by one-time email code or passkey, through Atlas. Sessions are carried in signed, HTTP-only cookies and can be revoked everywhere from settings. API keys are shown only to you and can be revoked at any time. The audit log is hash-chained, so alteration is detectable.
47. +Added: Bitcoin, Litecoin and USDT payment addresses are derived from an extended public key, so no spendable key for them exists on our servers. Solana works differently: each top-up gets its own one-time address from a dedicated deposit key held as a server secret, and the payment is forwarded to our cold storage within minutes of arriving.
48. International transfers
49. Suppliers and infrastructure are located in several countries, so your data is processed outside your own. Where required we rely on appropriate safeguards such as standard contractual clauses.
50. Cookies
51. The first time you visit, a banner asks for your choice; More in the banner, or Cookie settings in the footer, lets you choose category by category and change your mind at any time.
52. −Removed: We set one optional cookie, in the Marketing category: numera_ref, which remembers the referral link you arrived from so whoever invited you is credited if you sign up on a later visit. It is set only if you allow marketing cookies (or, where your law works on an opt-out basis, unless you object), and removed if you withdraw that choice. You don't need it to get the invite bonus: signing up straight from the link carries the referral with the sign-in itself, without storing anything.
53. −Removed: On numestri.com:
54. +Added: One optional cookie, in the Referrals category: referally_ctx, set by our referral processor Referally's script. It remembers the referral link you arrived from (and a random visitor id, so a later sign-up can be matched to that link) so whoever invited you is credited if you sign up on a later visit; the script also tells Referally which page you landed on. It is set on numestri.com and its subdomains, so our sign-in pages on auth.numestri.com can read it when you sign up. The script is loaded only if you allow referral cookies, the sign-in pages read the cookie only with that same permission, and the cookie (with its copy in your browser's local storage) is removed if you withdraw that choice. You don't need it to get the invite bonus: signing up straight from the link carries the referral with the sign-in itself, without storing anything.
55. +Added: Everything else below is strictly necessary, or remembers a choice you made yourself (your language, light or dark, the dashboard sidebar, a partner's prices you followed a link for), and is never used to track you.
56. +Added: The list our consent tool shows in the banner, kept up to date as we declare each cookie:
57. +Added: On numestri.com, in detail:
58. Cookie
59. Why
60. How long
61. −Removed: smsjew_session
62. +Added: numestri_session
63. keeps you signed in (signed, HTTP-only)
64. 30 days, or until you sign out
65. +Added: numera_signed_in
66. +Added: tells the page you are signed in, so it shows the right menu before it loads (holds no identity)
67. +Added: 30 days, or until you sign out
68. atlas_state, atlas_verifier, atlas_provider, atlas_next
69. protect a sign-in while it is in progress
70. −Removed: minutes; removed when sign-in finishes
71. +Added: 10 minutes; removed when sign-in finishes
72. +Added: __session, __atlas_rt, __atlas_uat, __atlas_sessions
73. +Added: set by Atlas, which runs our sign-in (from auth.numestri.com, for all of numestri.com): your Atlas session, the token that renews it, a "signed in" hint (__atlas_uat) and which accounts are signed in on this browser
74. +Added: __session about a minute, renewed while you are signed in; the others as long as your sign-in lasts (at most 30 days); all removed when you sign out
75. forumulate_return
76. the docs page to take you back to after signing in there
77. 15 minutes
78. −Removed: numera_ref
79. −Removed: optional (marketing) — the referral code from a link you followed, so the referrer is credited if you sign up later
80. −Removed: 30 days
81. +Added: NEXT_LOCALE
82. +Added: the language you chose
83. +Added: 12 months
84. +Added: theme
85. +Added: light or dark, if you chose one (also kept in local storage)
86. +Added: 12 months
87. +Added: dash_sidebar
88. +Added: whether you collapsed the dashboard sidebar, so it opens the way you left it
89. +Added: 12 months
90. +Added: numera_pcode
91. +Added: the partner code from a link you followed (?code=…), so that partner's prices apply once you sign in or sign up
92. +Added: 30 days; deleted as soon as it has been used
93. +Added: referally_ctx
94. +Added: optional (referrals), set by Referally's script — the referral code from a link you followed and a random visitor id, so the referrer is credited if you sign up later (also kept in local storage)
95. +Added: about 400 days, or until you withdraw consent
96. CookieMunch
97. remembers your cookie choice, so the banner doesn't ask on every visit
98. 12 months, or until you change your choice
99. −Removed: Support chat loads only when you click the chat button (or, if you have chatted with us before, when you return so our replies can reach you). Once it has loaded, Chatly keeps a visitor token in your browser's local storage so your conversation survives a reload, and records the campaign tags (utm_…) of the page you opened it on. Nothing is stored for visitors who never open the chat.
100. −Removed: On the pages listed above (docs, guides, blog, community, status, legal), Forumulate sets a separate session cookie only if you sign in there, and reads the same CookieMunch choice.
101. +Added: Support chat loads only when you click the chat button (or, if you have chatted with us before, when you return so our replies can reach you). Once it has loaded, Chatly keeps in your browser's local storage a visitor token so your conversation survives a reload (chatly:vt:…) and a note that this browser has visited before (chatly:seen); once you have a conversation, also a note of which replies in it you have already seen (chatly:vr:…); if you are signed in, also a check of which account the chat belongs to (chatly:vh:…) and that account's id (chatly:xid:…). It keeps the campaign tags (utm_…) of the page you opened it on in session storage (chatly:utm), which is cleared when you close the tab, and those tags are sent to Chatly when the chat loads. We keep a note in local storage of which account the chat is linked to (numera:chat-user). None of these is a cookie, and nothing is stored or sent for visitors who never open the chat.
102. +Added: On the pages listed above (docs, guides, blog, community, status, legal), Forumulate reads the same CookieMunch choice and remembers the language you read them in (forumulate_lang, 12 months). Only if you sign in there, it sets its own session cookies: forumulate_session (30 days), fm_signed_in (a readable hint, 30 days) and cflx_vis_… passes (12 hours).
103. We do not set advertising, analytics or cross-site tracking cookies.
104. Children
105. ⋯