Privacy notice
This notice says what personal data Nasfam Business handles, why, who receives it, how long we keep it and what you can ask us to do. "The Act" means the Nigeria Data Protection Act 2023.
Effective
On this page
1. Who is responsible
Nasfam Technologies, which provides Nasfam Business ("we", "us"), is responsible for the personal data this notice describes, except where section 3 says we act for a business. For anything in this notice, write to support@nasfampay.com with "Privacy" in the subject line.
2. Whom this covers
- People at our customers: the person who opens an account, and anyone else who uses it.
- A business customer's representative, and its owners and directors where we are told who they are.
- People who send a deposit: the holder of the wallet or exchange account a deposit comes from, where we can identify them.
- Recipients: people whose Telegram username a business sends us so that a product can be delivered to them.
- Visitors to our website, and people who write to us.
If you bought something from a business that uses Nasfam Business, that business's own privacy notice explains how it uses your data. This notice covers only what we receive.
3. When we decide, and when we act for a business
- We act for the business when it sends us a Recipient's Telegram username so that we can check it, deliver the order and report back. The business decides why that data is used, and questions about it are best sent to the business first.
- We decide for ourselves when we handle data to run accounts, carry out checks, screen for sanctions and fraud, credit deposits, keep financial records, secure the service and meet our legal duties. That includes keeping order records, which name the Recipient's username, as our own financial and fraud records.
4. What we collect
When you visit the website
The public pages and the documentation send nothing you type to us or to anyone else. The website loads nothing from any other company: no analytics, no advertising, no fonts or scripts from elsewhere. What our hosts record is in section 7.
When you open an account and sign in
| Data | Where it is held |
|---|---|
| Your name, email address and password | Google Identity Platform, the sign-in service we use. It keeps them, checks your password when you sign in, and sends the email that confirms your address and any password-reset email you ask for. Your password goes nowhere else |
| The account number Google gives you, and whether your email address is confirmed | Our servers, which record you by that number, without your name or email address |
| Your workspace, its name and your role in it | Our servers |
| The email address of a person you invite | Our servers, with the invitation. An invitation can be accepted for seven days |
| A session code | A cookie, and our servers keep only a hash of it (section 13) |
When you use your workspace
- Its API keys, as a keyed hash and never the secret itself, and its webhook endpoints, with their signing secrets encrypted.
- Its quotes, orders and balance movements, including the Recipient usernames they name.
- The country, account type and intended use you declare. Each declaration is kept, with who made it and when.
- The display currency you choose, kept with your account along with a record of earlier choices.
- A log of actions in your account: who did what, and when. Secrets are never recorded in it.
- What you write to us, if you write to us.
When your server calls the API
We keep a short record of each request made with one of your keys, so that you can see it in the dashboard: when it was made, the key and the operation it used, the result, how long it took, and any idempotency key sent with it. That record holds no body, no other header and no IP address. From those records we count your requests per day, by operation and result. Our hosting provider may log the request separately (section 7).
When you ask for Live
| Data | Where it comes from |
|---|---|
| Your legal name, or your business's registered name and its representative's legal name | You |
| The last four characters of a business's tax identifier. For an individual in Nigeria, the National Identification Number you declare as your tax identifier, encrypted so that it cannot be read in ordinary use. We do not verify it | You |
| The funding source you declare: a TON address, or the name of an exchange | You |
| The country or region your request came from | Our load balancer, at the time of the request. We use it to refuse a request from a place we do not serve |
| A hash of each name we screen, the list versions we screened it against, the result, and a copy of any list entry it may match | Our screening, against sanctions lists we download |
| Each decision: the rules applied, their results, the policy version, and what you were told | Our systems |
An automated identity check is built but is not running, and no identity provider receives your data. If we switch one on, we will first update this notice to name the provider and what it receives. Such a check keeps the provider's answer, the last four digits of the number and a keyed hash that lets us recognise the same person again, and not the number itself.
When a deposit is sent
For a Live deposit we record the address it came from, the transaction, the amount, the time and the rate used, and who sent it, as far as the business has told us. Blockchain records are public and permanent, and we cannot change them.
About Recipients
| Data | Where it comes from | Notes |
|---|---|---|
| Telegram username | The business that places the order | Kept with the quote and the order |
| The display name Telegram shows for that username | Our Telegram delivery provider, when a business asks for a quote | Shown to the business in the quote so it can confirm the right person, and kept with the quote. It is not put on orders or sent in webhooks |
| What was ordered for the username: the product, its quantity or length, the time and the status | Our order records |
We do not ask for any other information about Recipients, and businesses are told not to put personal data in order references.
In the sandbox
The sandbox uses test usernames and simulated money, and it makes no lookup against Telegram. Businesses are told not to submit a real person's username there. If the dashboard cannot reach its servers, its sign-up and sign-in pages work as a preview instead: so that you can look around the sample workspace, the preview keeps the email address and the answers you enter in your browser's local storage until you sign out of it. It never keeps a password, and none of it is sent to us.
5. Why we use it, and our lawful basis
Section 25(1) of the Act sets the lawful bases. These are the ones we rely on.
| Purpose | Lawful basis |
|---|---|
| Open and run your account, sign you in, keep it secure | Contract, section 25(1)(b)(i), where you are the customer. Otherwise legitimate interests, section 25(1)(b)(v), in providing the service the business contracted for |
| Deliver orders and report on them, for the business | We act for the business, which needs its own basis (section 3) |
| Check a person or business asking for Live, and screen against sanctions lists | Legal obligation, section 25(1)(b)(ii), where a law requires it of us. Otherwise legitimate interests, in preventing financial crime and fraud |
| Credit deposits, screen where they came from, and record them | Contract, and legal obligation where one applies |
| Keep financial records of balances, deposits and orders | Legal obligation where one applies. Otherwise legitimate interests, in keeping an accurate record |
| Detect and stop fraud, misuse and attacks | Legitimate interests |
| Answer questions and complaints, and send service and security messages | Legitimate interests |
| Establish or defend legal claims, and answer lawful requests | Legal obligation or legitimate interests |
We do not rely on legitimate interests where they override your rights, or where you would not reasonably expect the processing. We do not sell personal data, and we do not use it for advertising.
6. Automated decisions and sensitive data
A request for Live is checked against a versioned set of rules on our servers. It may be decided automatically: approved, asked for more, or declined. We record the rules and the inputs used. A possible sanctions match is never cleared automatically. Rate limits also refuse requests automatically when they come too fast.
Section 37 of the Act lets you ask a person to review a decision made solely by automated means that has legal or similarly significant effects on you, to give your view and to contest it. Write to us (section 17) to ask. We may be unable to give every reason where the law stops us.
We do not collect biometric data. If a check ever needs it, we will first update this notice and meet the conditions in section 30 of the Act.
7. Who receives it
We share only what each recipient needs.
| Recipient | What they receive | Why |
|---|---|---|
| Google Cloud | Everything on our servers, stored for us: the database, its backups, encrypted secrets, and request logs including IP addresses | To run the API and the dashboard's servers |
| Google Identity Platform | Name, email address and password | To sign you in, and to send sign-in emails |
| Vercel | Request records, which usually include your IP address, the time, the address asked for, the page that linked to it, and your browser type | It serves this website and the dashboard's pages, and forwards the dashboard's requests to our servers |
| Our Telegram delivery provider, and through it Telegram | A Recipient's username, the product and its quantity or length | To check the username and deliver the product. In Live only |
| TON Center and TonAPI | Deposit addresses and transactions we ask about | To read the TON network and confirm deposits |
| Telegram, for our staff chat | An alert's type, an internal reference and its time. No name, email address or username | To tell our staff that something needs attention |
| The business that placed an order | The order's status, the Recipient username it sent us and, at quote time, the display name | The order is theirs |
| Webhook addresses a business registers | Order and balance events for that business | The business asked for them |
| Professional advisers | What they need | To advise us |
| Courts, regulators and law enforcement | What the law requires | To meet a legal duty |
| A buyer of our business | The records needed to continue the service | Only on terms that keep this notice in force |
The sources of our market rates and the publishers of the sanctions lists we screen against (the United Nations, Nigeria, the United States, the United Kingdom and the European Union) send data to us. We send them no personal data, and names are compared on our own servers.
8. Where your data goes
Your data may be handled outside the country you are in:
- Our servers and database are in Google Cloud's europe-west1 region, in Belgium. Backups of the Live database are in europe-west4, in the Netherlands.
- Google Identity Platform and Vercel run on their own networks in several countries.
- For a Live order, a Recipient's username goes to our Telegram delivery provider and to Telegram, which may be outside Nigeria and outside your country.
- People and providers who work for us, including in Nigeria, may handle your data wherever you are.
For data that leaves Nigeria, section 41 of the Act requires that the recipient gives adequate protection, or that a condition in section 43 applies. We rely on the data protection terms in our providers' contracts where they give that protection, and otherwise on section 43, including that the transfer is needed to perform a contract with you or to deliver what you or the business asked for.
9. How long we keep it
| Record | How long |
|---|---|
| API request records | 7 days, and at most 1,000,000 for one organisation |
| Daily counts of API requests | 400 days |
| Signed-in sessions | A session ends after 30 minutes without use, and after 12 hours at most |
| Request logs on Google Cloud | 30 days |
| Request records on Vercel | For the period Vercel's service sets |
| Name, email address and password at Google Identity Platform | Until your sign-in account is deleted. Ask us to delete it when you close your account |
| Orders, quotes, balance movements, ledger entries and deposit records, which name Recipient usernames and source addresses | For the life of the account and afterwards as financial records. The ledger is built so that entries are never edited or removed, and we have not set an end date |
| The log of account actions | The same. Each entry is linked to the one before it, so it cannot be changed or removed without that being detected |
| Declarations, Live applications, screening results, decisions and earlier display currency choices | For the life of the account and afterwards as compliance records, for at least five years where anti-money-laundering law applies to us. We have not set an end date |
| The input to an identity check, if one ever runs | Erased once the check is answered or has expired |
| Database backups | Live: 14 daily backups, and 7 days of point-in-time recovery. Sandbox: 7 daily backups, and 7 days of point-in-time recovery |
| Sandbox data | Until it is reset. We may reset it at any time |
| What you write to us | As long as we need it to deal with what you wrote |
We cannot change or delete what is recorded on a public blockchain.
10. How we protect it
- Sandbox and Live are separate systems, with separate databases, sign-in projects and keys.
- API keys are stored only as a keyed hash, and each is shown once.
- Dashboard sessions use a cookie that page scripts cannot read, with idle and absolute time-outs.
- Each business can see only its own records, and the database enforces that on every row.
- Webhook signing secrets are stored encrypted, and our own keys and passwords are held in a secret manager that gives each service only what it needs.
- Actions are recorded in a log that can only be added to.
Two-step sign-in is planned and is not available yet. No system is perfectly secure: these measures reduce risk, and they do not remove it.
11. If something goes wrong
If a breach of personal data we are responsible for is likely to result in a risk to people's rights and freedoms, section 40(2) of the Act requires us to notify the Nigeria Data Protection Commission within 72 hours of becoming aware of it. Where it is likely to result in a high risk to you, section 40(3) requires us to tell you immediately, in plain language. Where we hold data for a business (section 3), we will tell that business without undue delay so that it can meet its own duties.
12. Your rights
Under sections 34 to 38 of the Act you may ask us:
- whether we hold personal data about you, and for a copy of it in a commonly used electronic format, with why we use it, who receives it and how long we keep it;
- to correct data that is wrong, out of date, incomplete or misleading;
- to erase data we no longer need or have no lawful basis to keep;
- to restrict use of your data while a request or an objection is resolved;
- to stop using your data where we rely on legitimate interests, and to stop direct marketing at any time;
- to withdraw consent where consent is the basis, which is as easy as giving it;
- for a person to review a decision made solely by automated means (section 6);
- for your data in a portable form, where the law provides for it.
Limits. We cannot delete records the law requires us to keep, remove a username from an order record we keep, or change a public blockchain. Where we hold data for a business (section 3), we may pass your request to that business and help it answer. If we refuse a request we will say why, unless the law stops us.
How to ask. Write to support@nasfampay.com with "Privacy" in the subject line. We may need to confirm who you are first. We aim to answer within 30 days. There is no charge, unless a request is plainly unfounded or excessive.
Complaints. Section 46 of the Act lets you complain to the Nigeria Data Protection Commission. If the General Data Protection Regulation or the UK GDPR applies to you, you have similar rights and may complain to your local data protection authority. We would like the chance to put things right first.
13. Cookies and browser storage
| Item | What it is | Needed? |
|---|---|---|
| __Host-session | One cookie, set by the dashboard's servers when you sign in. It holds a random session code and nothing about you. Your browser sends it only to the dashboard that set it, and page scripts cannot read it. It has no expiry date, so your browser normally deletes it when it closes, and signing out deletes it at once. The sandbox and Live dashboards are separate, and each sets its own | Strictly necessary: it keeps you signed in |
| Display preferences | Settings such as the colour theme, kept in your browser's local storage and not sent to us. You can clear them in your browser settings. Your display currency is different: it is kept with your account (section 4) | Remembers how you like the site |
| nb.preview.session | Kept in your browser's local storage only while you use the sandbox dashboard's preview (section 4), and removed when you sign out of it | Needed for the preview |
The website's own code sets no other cookie, and it contains no analytics, advertising or tracking from any other company.
14. Children
Nasfam Business is for people acting in the course of a trade, business or profession. Nobody under 18 may open an account, and we do not knowingly collect data about children through accounts. A Recipient's username tells us nothing about their age.
15. Marketing
We send account and security messages because they are part of the service. We do not send marketing email. If that changes, we will ask for your consent first, as a separate choice from accepting the terms, and you can withdraw it at any time.
16. Changes to this notice
We update this notice when our practices or the law change. Each version is dated at the top of this page. If a change materially affects how we use your data, we will post it here and tell account holders where we can before it takes effect.
17. Contact
Nasfam Technologies, provider of Nasfam Business. Privacy questions and requests: support@nasfampay.com.
