Privacy policy
How Involink collects, uses, stores, and shares personal data under Jordan's Personal Data Protection Law No. 24 of 2023.
Last updated 2026-10-21
1. Who we are
Involink (“Involink”, “we”) is a B2B invoicing and payment-collection platform operated from Amman, Jordan. We provide invoicing, quotes, credit notes, e-invoicing submission to the Jordan Income and Sales Tax Department through JoFotara, and CliQ payment collection to businesses in Jordan (“merchants”), and we process the payments their customers make (“buyers”).
This policy describes how Involink collects, uses, stores, and shares personal data on involink.jo, on the Involink web app (app.involink.jo), in the Involink mobile app, and on the public pages a buyer opens to view or pay an invoice. It is governed by the Personal Data Protection Law No. 24 of 2023 of the Hashemite Kingdom of Jordan (“the Law”) and other applicable Jordanian law.
Questions about this policy or about your data go to privacy@involink.jo.
2. Who this policy covers, and our role
Merchants and their team members: the people who register a business on Involink or are invited to work in a merchant's store. For this data Involink is the controller.
Buyers: the people a merchant sends an invoice to, who open a share link, scan a payment QR code, or pay through Involink. A buyer may also choose to create an Involink account to keep track of the invoices addressed to their email. For a buyer's own Involink account, and for what a buyer enters on our public pages, Involink is the controller.
Customer records kept by a merchant: the names, contact details, and invoices a merchant stores about its own customers. Here the merchant is the controller and Involink processes that data on the merchant's instructions under the Merchant Agreement. If your concern is about an invoice a merchant issued to you, contact that merchant first; we will assist them in answering you.
Visitors to involink.jo, and anyone who writes to us for support.
3. Data we collect
Merchant account and business data: your name, email address, mobile number (verified by a one-time code sent by SMS), password (stored only as a hash), and, if you enable two-factor authentication, the secret for your authenticator app. Business details: trading name, registered name, tax number, address, phone, email, and logo. JoFotara device identifiers and secrets, and the credentials of the payment accounts you connect (for example a UWallet merchant identifier and security key), which are stored encrypted.
Team data: the name, email address, and role of each person a merchant invites to its store, and the invitation itself.
Customer and contact records entered by merchants: contact name, email, phone, tax number, address, and notes, together with the invoices, quotes, credit notes, payment records, and receipts that relate to them.
Data a buyer enters on a public payment page: the CliQ alias or mobile number used to request a payment, and, if the buyer chooses to identify themselves or to receive a receipt, their name and email. A signed-in buyer may also choose to save a CliQ alias for later use; we never save one without that choice. Involink never sees a buyer's bank login, wallet PIN, or card details: the payment is approved inside the buyer's own bank or wallet app.
Subscription and billing data: the plan a merchant is on, the status of each plan payment, any trial an Involink administrator has granted, and, during a trial, the masked CliQ alias to which collected funds are forwarded.
Technical and usage data: IP address, browser or device type, operating system, app version, language, timestamps, and product events (for example “invoice created” or “payment initiated”) in our server logs. If you enable push notifications on the mobile app, the device token that lets us deliver them. If the mobile app crashes, a crash report that may include the device model and the state of the app at the time.
Records we keep as evidence: when you accept our terms we record the version accepted, the time, your IP address, and browser details. We keep similar records for data-subject requests, for changes to payment-account credentials and API keys, and for actions taken by Involink administrators on a merchant's account.
Support and contact data: what you send us at support@involink.jo, through the contact form on involink.jo, or by other means.
4. How we use the data, and on what basis
To provide the service you signed up for (performance of a contract): creating and sending invoices, submitting e-invoices to JoFotara, collecting payments, issuing receipts, running your subscription, and supporting you.
To meet legal obligations: keeping accounting and tax records for the period Jordanian law requires, responding to lawful requests from authorities, and keeping the audit records described above.
For our legitimate interests in running a secure service: preventing fraud and abuse, rate limiting, monitoring for errors and outages, securing accounts, and improving the product using aggregated usage data.
With your consent, where the Law requires it: analytics cookies on involink.jo (section 9), and any marketing communication to merchants, which you can withdraw at any time. We never send marketing messages to buyers.
5. How we contact you and your customers
Email: account and transactional messages (verification, password reset, invoice and payment notifications, receipts, data exports) are sent from Involink addresses through Microsoft Azure Communication Services.
SMS: one-time codes to verify a mobile number, and, where a merchant enables it, invoice and reminder messages to that merchant's customers. SMS is sent through a licensed messaging provider in Jordan.
WhatsApp: where a merchant enables it, invoice and reminder messages to that merchant's customers are sent through the WhatsApp Business Platform operated by Meta. The customer's phone number, name, invoice number and amount, the merchant's name, and a link to the invoice are transmitted to Meta for delivery, under Meta's terms.
Push and in-app notifications: sent to merchants and team members who enable them on the mobile app. Push messages are delivered through Expo's push service and may name an invoice and an amount.
Merchants decide which channels their customers receive. A customer who no longer wants to receive invoice messages from a merchant should ask that merchant.
6. Payments
CliQ payments are processed by licensed payment service providers (currently UWallet, with Network International planned) over the JoPACC CliQ network. Involink sends the provider the data needed to raise a Request-to-Pay: the buyer's alias, the amount, a reference, and the merchant's account identifier. The provider tells us whether the request was approved, declined, or expired.
In the normal case the merchant's own provider account receives the payment. During a trial that Involink grants to a merchant, the merchant's store uses an Involink-owned payment account: the payment request the buyer approves will name Involink, Involink receives the funds, and forwards them to the merchant. We say so on the payment page before the buyer approves. In that case, refund or dispute requests that the merchant cannot resolve should come to Involink support.
Merchants pay Involink's subscription fees by approving a CliQ Request-to-Pay from their own alias to Involink's account. There are no automatic charges.
Transaction records (amount, currency, alias used, provider reference, status, timestamps) are kept as part of the accounting record described in section 10.
7. Who we share data with
Payment service providers and JoPACC, as described in section 6.
Jordan Income and Sales Tax Department, through JoFotara: the invoice content, the merchant's tax-registration details, and the buyer's name, tax number, city, and phone number where the merchant has recorded them, as the e-invoicing rules require.
Service providers acting on our instructions, bound by contract to process data only as we direct: Hetzner Online (servers, database, and encrypted backups), Microsoft (email delivery through Azure Communication Services, and application telemetry through Azure Application Insights), Sentry (error reports from the web app and the API, and from the mobile app where enabled), Meta (WhatsApp Business Platform, where a merchant uses WhatsApp), a Jordanian SMS provider, and Expo (mobile push delivery). Google (Google Tag Manager, Google Analytics, and Google Ads conversion measurement) and Meta (the Meta Pixel) run on involink.jo only after a visitor consents (section 9).
Third parties a merchant authorises: a merchant may create API keys and webhook endpoints so that its own software or a partner can read its Involink data or receive event notifications. Data shared this way is shared on the merchant's instruction and under the merchant's responsibility.
Involink staff: authorised support staff may, with an audited session, open a merchant's account to help resolve a problem. Every such session is logged with the administrator's identity and time.
Authorities and courts: where Jordanian law, a binding court order, or a regulatory directive requires disclosure.
A successor: if Involink is sold or merged, personal data may transfer to the successor under the same commitments, and we will tell you before that happens.
Involink never sells personal data. The only data that reaches advertising platforms is the consent-based measurement on involink.jo described in section 9, which records visits and sign-ups but no names, email addresses, phone numbers, or invoice data.
8. Where data is stored and international transfers
Involink's servers and database, including the marketing site, run on Hetzner Online in Germany, in the European Union, and encrypted backups are kept on Hetzner storage in the European Union. Email delivery and application telemetry run on Microsoft Azure in the European Union, and Sentry stores error reports in its European Union (Germany) region. Your data is therefore stored outside Jordan, under the cross-border transfer rules of the Law, with contractual safeguards, encryption in transit and at rest, and access limited to authorised personnel.
Some of the providers in section 7 (Meta, Expo, Google) may process data in other countries under their own contractual safeguards. Payment providers and JoFotara process data in Jordan.
9. Cookies, local storage, and analytics
The Involink app sets only the cookies it needs to work: a session cookie that keeps you signed in (and a flag recording whether you asked to stay signed in), and two preference cookies for language and light or dark theme. There are no advertising or tracking cookies in the app, and the public invoice and payment pages load no third-party scripts.
The marketing site involink.jo uses Google Tag Manager to load Google Analytics, which tells us how visitors use the site, and Google Ads conversion measurement, which tells us whether a visit that started from one of our advertisements ended in a sign-up. Both run only after you accept analytics in the consent banner. Your choice is stored on your device and can be changed at any time. If you decline, no Google script is loaded and no Google cookies are set.
After the same consent, Tag Manager also loads the Meta Pixel, which tells us whether a visit that started from one of our advertisements on Facebook or Instagram ended in a sign-up, and lets us show our advertisements to people who visited the site. Meta receives the pages you view on involink.jo, the completed sign-up event, your browser and device details, and the cookies Meta sets on involink.jo (such as _fbp), and it may link them to a Facebook or Instagram account you are signed in to, under Meta's own privacy policy. We do not send Meta your name, email address, phone number, or any invoice data. If you decline, the Meta Pixel is not loaded and no Meta cookies are set.
When you arrive from an advertisement, the campaign identifiers in the link (such as the campaign name or an advertising click identifier) are carried along to the sign-up page so that a sign-up can be attributed to the advertisement. They identify the campaign, not you, and they are passed to Google and Meta only if you have accepted analytics.
The mobile app stores your session and preferences on the device so you stay signed in.
10. How long we keep data
Invoices, credit notes, transactions, receipts, and JoFotara submissions: for the period Jordanian tax legislation requires businesses to keep accounting records. Involink's retention schedule keeps these records for seven years from the end of the tax year they relate to, or longer where the law requires. These records are kept even after an account is closed, because they are part of the merchant's and the buyer's tax records.
Merchant, team, and buyer account data: for as long as the account exists, then until the retention period above has passed or a dispute or legal obligation is settled, after which it is erased or anonymised.
Customer contact records kept by a merchant: until the merchant deletes them or closes its account, subject to the accounting-record period above.
Store activity history: twelve months. API usage records: twenty-four months. Push device tokens: until you sign out, disable notifications, or remove the app.
Server logs, security records, and terms-acceptance and data-request records: for the period needed to secure the service and to evidence compliance with the Law.
Share links: a merchant can revoke a share link at any time; after that the page is no longer reachable.
11. Public invoice and payment pages
When a merchant shares an invoice, quote, or payment request, anyone who has the link or scans the QR code can see it: the merchant's business details, the invoice number, items, amounts, dates, and the buyer's name and email address as the merchant recorded them, plus a PDF of the invoice. Links are long random tokens, are not listed anywhere, and are marked so search engines do not index them. Treat a link you receive as you would the invoice itself, and ask the merchant to revoke it if it was sent in error.
12. Security
All traffic is encrypted in transit. Passwords are stored as salted hashes; payment-account credentials, JoFotara secrets, and API secrets are encrypted at rest; API keys are stored only as hashes. Two-factor authentication is available on every account. Access to production systems is limited to authorised personnel and logged. We rate-limit sign-in and payment endpoints, and we keep audit records of sensitive actions.
No service can guarantee absolute security. If a breach affects your personal data we will notify you and the competent authority as the Law requires.
13. Your rights and how to exercise them
Subject to the conditions and exceptions in the Law, you may ask for access to the personal data we hold about you, correction of inaccurate data, deletion where we are not required to keep it, restriction of or objection to certain processing, and a copy of your data in a portable form. You may withdraw consent at any time where processing is based on consent.
Merchants and buyers with an Involink account can exercise the two most common rights themselves, from the profile screen of the web or mobile app: “Export my data” sends a machine-readable copy of your account data to your email, and “Delete my account” closes the account immediately after you re-enter your password. On deletion we disable sign-in and revoke all sessions at once, and erase or anonymise your personal data once the accounting-record period in section 10 has passed. Invoices and transactions stay in the merchant's records because tax law requires it.
For any other request, or if you do not have an account, write to privacy@involink.jo. We will confirm your identity and respond within the period the Law sets. You also have the right to lodge a complaint with the competent authority under the Law.
If you are a buyer and your request concerns an invoice a merchant issued to you, please contact that merchant first: they control that relationship, and we will support them in answering you.
14. Children
Involink is a business service. We do not knowingly collect personal data from anyone under eighteen, and a merchant account may only be opened by a person entitled to represent a business.
15. Changes to this policy
Material changes will be announced inside the Involink app and by email to the merchant's primary contact before they take effect. The date at the top of this page shows the latest revision.
16. Contact
Privacy questions and requests: privacy@involink.jo. Support, refunds, and payment questions that a merchant could not resolve: support@involink.jo. For a refund or dispute about a specific invoice, contact the merchant who issued it first.