Privacy Policy
How Invoice-It collects, uses and shares personal data, and the rights and choices available to you.
Last updated
1. Who we are and scope of this Policy
1.1 PENUEL AYOMIKUN AKOMOLAFE, trading as Invoice-It in Nigeria (“we”, “us” or “our”), operates the Invoice-It website and invoicing service. Contact support@invoice-it.org for privacy enquiries.
1.2 This Policy covers personal data handled through our website, account creation and authentication, workspaces, document links, communications and support. It applies to visitors, account holders, people contacting us and recipients whose information appears in customer documents. Personal data means information relating to an identified or identifiable individual.
1.3 Invoice-It operates from Nigeria and serves international users where available and lawful. The Nigeria Data Protection Act 2023 applies where relevant, together with other applicable requirements. This Policy is information about processing, not blanket consent to all processing or a claim of certification under every jurisdiction’s law.
2. Our role and customer-controlled information
2.1 We determine purposes and means for account administration, website operation, service security and support information and act as controller for that processing. For business/client records submitted by a customer, the customer generally determines their business purpose and acts as controller; we process those records to provide the requested features on that customer’s instructions.
2.2 Customers are responsible for appropriate notices, lawful bases and permissions for personal data they enter, including client contact information, documents, bank instructions and attachments. Uploading a person’s details is not a consent-collection mechanism. Our own processor and security obligations still apply.
2.3 Document recipients should normally contact the issuing business for transaction questions, corrections and requests involving its client records. You may contact us about our processing; where a request concerns customer-controlled data, we may coordinate with the customer and assist as applicable. A public link does not make all underlying workspace records public.
3. Personal data collected and its sources
3.1 Account and profile data: names, email addresses, account identifiers, profile details, authentication-related information and verification/security events. Google sign-in supplies permitted identity/profile information through Google and Supabase; we do not receive your Google password. Password verification and session handling are provided through Supabase Auth.
3.2 Customer records: business/client names and contacts, addresses, registration and tax identifiers, user-selected VAT preferences, bank/payment instructions, logos, and other information entered into the workspace. A blank tax preference is not a verified exemption. Invoice-It does not require you to supply unrelated identity documents or sensitive information.
3.3 Financial/document data: invoices, quotes, line items, prices, discounts, taxes, dates, notes, public-link permissions, recorded invoice-currency credits, received-payment amounts/currencies, conversion evidence, receipts, reversals, expenses, attachments and reporting/activity data. These can contain personal data about customers, clients or recipients.
3.4 Technical and communications data: IP/network information, browser/device details, browser identifiers, timestamps, approximate country hints, request/error records, support and account-access messages, claimed account/reply email addresses, email recipients/content and delivery/open/click/view events where available. Some security and abuse-limiting information is represented by hashes or masked values.
3.5 Optional article feedback: article identifier/revision, helpful or not-helpful vote, optional structured reason, timestamps and a hash of an independently generated browser key for that article revision. This feature does not require sign-in or attach your account email, workspace records or a free-text support message. Request network information is used in hashed abuse-limiting records; feedback is pseudonymous, not a promise of complete anonymity.
3.6 Sources include information you provide, records a customer enters about another person, browser requests and storage, Google sign-in, email-delivery events and infrastructure/security providers. Do not submit passwords, verification codes, card security codes or unnecessary sensitive personal data in documents, attachments or support messages.
4. How we use personal data
4.1 Provide the requested service: create and authenticate accounts; save and resume onboarding; store and manage client and business details; prepare and display documents; generate PDF/XML downloads; record payments and expenses; and calculate receipts and reports from saved records.
4.2 Carry out authorized communications and automation: deliver account verification/recovery and service emails, send documents and receipts, run configured recurring schedules and eligible payment reminders, and display delivery/document activity. Scheduling, a queued message or an activity event is not a guarantee of delivery or payment.
4.3 Review optional article feedback to identify unclear, missing or outdated guidance and improve the knowledge base. This feedback is not a support ticket, financial action or account-access request.
4.4 Protect and operate the service: apply access controls, signup and public-recovery verification, request limits and duplicate handling; maintain secure document links; diagnose failures; investigate misuse; preserve appropriate audit evidence; and handle support or account-access requests. Authentication identifies account access; a signed-out recovery request does not prove that an account exists or that the requester owns it.
4.5 Personalize functional defaults and maintain usability: remember appearance preferences, offer an editable approximate country and related currency/phone-country suggestion, recover local drafts where supported, and notify signed-in users of a newer deployment. Country suggestions do not establish a business address, citizenship or tax liability; city/state are not currently supplied as location hints.
5. Legal bases for processing
5.1 Depending on the purpose and applicable law, we rely on processing necessary to provide the service under a contract; legitimate interests in proportionate security, maintenance and support where not overridden by individual rights; compliance with legal obligations; or consent for an optional activity that requires it.
5.2 Where consent is the basis, it may be withdrawn for that activity without affecting earlier lawful processing. A required security or account function is not treated as optional marketing consent. Customers must establish the legal basis for customer-controlled records and communications they ask the Services to process.
5.3 We do not represent that one legal basis covers every data category or that this Policy alone supplies any required customer data-processing agreement. Contact us for the contractual arrangements and transfer information applicable to your use, particularly where your organization has specific regulatory requirements.
8. Email delivery, tracking and document activity
8.1 The service can record email delivery, rejection, bounce, failure, open and click events and authorized document views and decisions. Where enabled, a tracking image or tracked link can signal an open/click. The issuing business can see available activity to manage documents and diagnose delivery issues.
8.2 Scanners, preview tools, mail privacy features and blocked images can create or suppress events. Delivery and view records do not reliably prove that a particular person read a message, had authority to accept a quote or paid a balance. Retention and access to these records follow the service and legal purposes described here.
9. Cookies, local storage and security checks
9.1 Functional browser storage can contain sign-in/session information, theme preferences, a device/browser identifier, authentication cooldown information and local invoice drafts. Local storage may persist after browser closure; session storage normally belongs to a tab session. Restricting or deleting it can sign you out, reset preferences or remove unsaved drafts.
9.2 Optional article feedback uses an independent random browser-storage key for each article revision to support repeat-vote updates. Only its hash is sent into the feedback ledger; the submission necessarily sends the key to our backend for hashing, but it is not stored there as plaintext. Clearing or restricting browser storage can permit another key and does not prove that a voter is a unique person. A lightweight local proof calculation and server request limits protect this feature; they do not authenticate a user or contact an AI provider.
9.3 Turnstile may process browser/device and technical challenge signals and use provider-managed technology to assess signup and signed-out account-access requests. Signup can obtain a short-lived, email-bound authorization after successful server validation. Public account-access help uses a separately named challenge action, exact-hostname validation, cooldowns and hashed account/network rate identities; Turnstile tokens are single-use and are not stored in the request ledger. Verification reduces automated abuse but does not prove that a requester is genuine or owns an account.
9.4 Ordinary sign-in, password-reset and resend forms do not use the public account-access-help challenge; their Supabase authentication/request controls remain separate. Optional Google sign-in follows Google’s own flow. We do not treat security verification as consent to advertising, proof of identity or proof of tax status.
9.5 Invoice-It does not currently operate a newsletter signup. Optional analytics, marketing technology or subscriptions introduced later will require appropriate information and any legally required choices before the relevant processing. User-controlled browser settings can affect provider scripts and cookies.
10. International processing and safeguards
10.1 The Operator is based in Nigeria; providers and recipients may process data in other countries. Processing locations depend on configured infrastructure, delivery networks, provider operations and the recipients you choose. Use of a country field does not confine all processing to that country.
10.2 Applicable transfer requirements must be addressed for the processing concerned. Available mechanisms depend on the law and circumstances and may include appropriate contractual safeguards or another permitted basis. This Policy does not claim that a particular adequacy decision, certification or transfer contract covers every provider or visitor. Contact us for relevant destinations and safeguards before using the service for data with special requirements.
11. Retention, deletion and account closure
11.1 Retention depends on the category and purpose: account activity, service delivery, customer instructions, legal recordkeeping, security investigation, disputes and pending rights/support requests. There is not a universal retention period for all records. Temporary signup authorizations expire after two minutes; expired authorization/limiter entries are eligible for cleanup. Expiry is not a promise of erasure from every infrastructure log at that instant.
11.2 Article-feedback votes are retained for editorial review until administratively removed; they are not automatically erased after a fixed short period. Hashed feedback rate-limit windows older than ten minutes are eligible for bounded cleanup when requests arrive, so lack of traffic can leave expired windows stored longer. Browser feedback keys remain subject to your browser-storage controls.
11.3 Public account-access-help requests are scheduled for deletion 30 days after receipt. Their private staff-notification outbox is deleted with the request. Cleanup runs in bounded batches, so operational delay can leave an expired record stored briefly beyond its scheduled deletion time. Provider email delivery metadata may follow the provider’s own applicable retention.
11.4 You may request account closure or deletion through the contact below. We assess applicable retention duties and explain limitations where relevant. Deletion from active use may not immediately erase backups, security logs or legally retained material, and does not remove recipient-held downloads/emails. We do not promise instant erasure from every system.
11.5 Keep legally required copies and use available downloads/exports before requesting closure. Removing a client record may leave historical document snapshots or activity needed for the customer’s records. We coordinate customer-controlled-data requests with the relevant business where required.
12. Security, incidents and automated decisions
12.1 Measures include authentication, owner-scoped access restrictions, protected backend operations, controlled document links, signup challenge validation and request controls. These measures are designed to reduce risk; no service or network is guaranteed completely secure. This Policy does not claim end-to-end encryption, an independent certification or an uptime guarantee that has not been established.
12.2 Protect account credentials and devices, review document recipients and report suspected misuse promptly. We assess reported incidents and make notifications where required by applicable law. Never send passwords, full verification codes or unrelated identity documents to support.
12.3 Automated security checks can delay or reject a request. The service does not decide creditworthiness, collect debts or determine a business’s tax liability. Roadmap assistant and microphone illustrations are not working AI or recording controls: those demonstrations do not record your voice or send prompts to a model provider. Future live AI functionality would need its own accurate processing explanation before introduction.
13. Your rights, requests and complaints
13.1 Subject to applicable law and its conditions, rights may include information about processing, access, correction, deletion, restriction, portability, objection, withdrawal of consent and protections relating to qualifying solely automated decisions. Not every right applies to every record or lawful processing purpose.
13.2 Send requests to support@invoice-it.org with the relevant information and requested action. We may ask for proportionate identity verification to protect your and other people’s information; do not send your password. We will handle requests within applicable legal timeframes and explain lawful limitations. For customer-controlled records, the issuing business may need to act as controller.
13.3 You can complain to the Nigeria Data Protection Commission or another competent supervisory authority where applicable, without first obtaining our permission. International use does not waive rights that local applicable law preserves.
14. Children and age limits
14.1 Accounts are intended for adults aged 18 and above acting for themselves or a business. The service is not directed at children. Customer records may include information about other people; customers must meet any additional obligations applicable to such information.
14.2 Contact us if you believe a child has opened an account or information has been submitted unlawfully so it can be investigated and handled appropriately. Do not provide more sensitive information than needed to describe the concern.
15. Policy updates and contact
15.1 We may update this Policy when the Services, processing or applicable requirements change. The displayed date identifies the version. Material changes will receive appropriate notice, and consent or other steps will be requested where required.
15.2 The current responsible Operator is PENUEL AYOMIKUN AKOMOLAFE trading as Invoice-It in Nigeria. Contact support@invoice-it.org for privacy enquiries and rights requests. The Terms of Service explain the agreement for using the Services.