Privacy Policy
Nexbureau is a Canadian bank-data platform operated by Nexbureau, Inc. ("Nexbureau", "we", "us"). Businesses that work with us ("partners") add our Connect window to their apps and websites. Through it, people ("end users") link a bank account so the partner can see account and transaction information they agreed to share. Partner staff ("contacts") use the Nexbureau Client Dashboard to view that information.
This policy explains what personal information we handle, why, who we share it with, how long we keep it and the choices you have. It is written for Canada's federal privacy law (PIPEDA) and, where it applies, Quebec's private-sector privacy law as amended by Law 25.
Our role
When you link a bank account through Connect, you do so to use a partner's service. We collect and process that information to provide the service to the partner, under our agreement with them. The partner's own privacy policy also applies, and the partner decides how it uses the information we deliver. When partner staff sign in to the Client Dashboard, we handle their sign-in information to run and secure the dashboard.
Information we collect
End users who link a bank account
- What you give us in Connect: the bank you choose, your online banking username and password (and a PIN or similar field if your bank asks for one), one-time verification codes, answers to security questions and the accounts you choose to share.
- What we retrieve from your bank: account names and types, account, transit and institution numbers, account holder names, balances, credit limits, loan and payment details, and transactions (date, amount, description and running balance). If the partner asks for identity information, we also retrieve the name, date of birth, gender, employment details, email addresses, phone numbers and postal addresses that your bank holds.
- From the partner: the identifier the partner uses for you in its own systems.
- Technical information: IP address and browser details that reach our servers, and events from the Connect window (such as which step you reached and any error) that help us fix problems.
- Records of the bank sign-in: when we connect to your bank's website for you, we keep screenshots and copies of the pages and the data and files the bank returns, so we can find and fix connection errors.
Partner contacts who use the Client Dashboard
- Account details: your work email address, the partner organizations you belong to, your role, and your email notification choices.
- Google sign-in: if you sign in with Google, we receive a signed token from Google and use your email address, whether Google has verified it, and your organization's Google domain. We do not store your Google profile name or picture.
- Email sign-in codes: if you sign in with an emailed code, we store the code, your email address and your IP address only as one-way hashes, to check the code and prevent abuse.
- Session and technical information: a session identifier, your IP address (used to limit repeated sign-in attempts) and server logs.
Partner organizations
We keep the partner's name, contact email, country, webhook settings, branding and API keys. API keys are stored only as hashes.
How we use information
- To connect to your bank, retrieve the accounts and transactions you agreed to share, and keep them up to date for the partner.
- To deliver that information to the partner through our API, webhooks, the Client Dashboard and connection emails, including summaries the partner can use to understand income, spending, balances and other financial patterns.
- To sign partner contacts in, keep their sessions secure and send them sign-in codes and the connection notifications they choose.
- To secure our services, prevent fraud and abuse, and diagnose and fix errors.
- To meet legal obligations.
We do not sell personal information and we do not use it for advertising.
Consent
Connect normally asks for your agreement before you enter your bank details. Some partners ask for it in their own app instead. By continuing, you consent to us collecting, using and sharing your information as described in this policy and in the partner's policy. You can withdraw your consent at any time by asking the partner, or us, to delete your connection. Once a connection is deleted, the partner stops receiving new data from it.
Who we share information with
The partner you are connecting with. The partner receives the account, transaction and identity information you agreed to share. Partner contacts can see it in the Client Dashboard, and the partner can receive it through our API and webhooks.
Service providers. We use the following companies to run our services. They may only use the information to provide services to us.
- Amazon Web Services (AWS) hosts our servers, databases, file storage and backups in the Canada (Central) region, sends our emails (Amazon SES) and stores our secrets. The files that make up the Connect window are delivered through AWS's worldwide CloudFront network.
- Cloudflare provides our domain name service, encryption in transit and protection against attacks. Traffic to our websites and API passes through Cloudflare's global network.
- Google provides "Sign in with Google" for partner contacts who choose it, and serves the fonts used by the Client Dashboard, which means Google receives your IP address when the dashboard loads.
- Bank-data providers. Depending on your bank, we may pass your bank sign-in details and verification answers to Flinks or Sophtron, which connect to the bank and return your account information to us.
- Network providers. When we connect to a bank's website ourselves, the encrypted connection may be routed through a proxy network operated by Oxylabs or Bright Data. If the bank shows a "prove you are human" check, the check (the page address and puzzle image, not your sign-in details) may be sent to 2Captcha.
- Anthropic. If an automated step on a bank's website breaks, we may send a redacted outline of that web page to Anthropic's Claude AI models, directly or through AWS, to help repair the step. Passwords, verification answers, names, account numbers, amounts, dates and contact details are removed first, and no screenshots are sent. This processing takes place in the United States.
Legal reasons. We may disclose information when the law requires it, to protect our rights or the safety of others, or as part of a merger, sale or reorganization of our business, subject to this policy.
Where information is stored
All user data we store stays on servers in Canada. Our databases, file storage, backups and logs are all hosted in AWS's Canada (Central) region, and we do not store user data anywhere else. To connect to your bank and run our services, some of the service providers listed above process information outside Canada, including in the United States. Information processed in another country is subject to that country's laws and may be accessible to its courts, police and national security authorities. Before information about Quebec residents is communicated outside Quebec, we assess whether it will be adequately protected.
How we protect information
- Information is encrypted in transit with TLS.
- Bank sign-in credentials, security-question answers, bank-data provider responses and stored webhook payloads are encrypted with AES-256-GCM, using a separate encryption key for each partner.
- Our databases, file storage and backups are stored on encrypted disks and in encrypted storage.
- Partner data is separated in the database so that each partner can only reach its own records.
- API keys, dashboard session tokens and sign-in codes are stored as one-way hashes. Dashboard session records are encrypted and expire automatically.
- Access to our systems is limited to authorized staff.
No system is perfectly secure, but we work to protect your information and review our safeguards as our services change.
How long we keep information
- Account, transaction and identity information is kept while the partner keeps the connection, until the partner or you ask us to delete it, and for no longer than 365 days after our agreement with the partner ends.
- Bank sign-in credentials are kept, encrypted, until your connections are deleted, so that we can refresh your data. When the partner deletes your data, we erase them along with your account, transaction and identity information and your security-question answers.
- A record that a connection existed (identifiers, bank and status, without credentials or financial data) is kept for 365 days after deletion.
- Security-question answers are deleted after 180 days.
- Bank-data provider responses are deleted after 14 days.
- Screenshots, page copies and files from bank sign-ins are deleted after 7 days. Related diagnostic records are deleted within 90 days, and records of automated repairs within 180 days.
- Failed webhook payloads are deleted after 14 days and webhook delivery records after 30 days.
- Security audit records are deleted after 365 days.
- Server logs are deleted within 45 days and performance traces within 14 days.
- Backups are deleted within 30 days, so deleted information can remain in a backup for up to 30 days.
- Email sign-in codes expire after 10 minutes. Dashboard sessions end after 8 hours or when you sign out.
- Partner contact accounts are kept while the contact has access to a partner workspace and for 365 days afterwards.
Cookies and browser storage
We do not use advertising or analytics cookies.
- Client Dashboard session cookie keeps you signed in for up to 8 hours. It cannot be read by page scripts and is only sent to the dashboard.
- Google sign-in cookie is a short-lived value, valid for 10 minutes, that protects the Google sign-in step.
- Display preferences: the dashboard saves your theme and background choices in your browser.
- Google: the "Sign in with Google" button is provided by Google, which may set its own cookies under Google's privacy policy.
- Connect uses no cookies. It keeps a temporary session and a random troubleshooting identifier in your browser tab's session storage, which is cleared when the tab is closed.
Your rights
You can ask to access the personal information we hold about you, to correct it, or to delete it, and you can withdraw your consent. Quebec residents can also ask for their information in a structured, commonly used technology format, and ask about how it was collected and used. Because we handle end-user information for partners, we may refer your request to the partner, or work with them to answer it.
To make a request, contact us at the address below. We may need to confirm your identity first. We will answer within 30 days, or tell you if we need more time as the law allows.
Analysis and automated decisions
We calculate summaries such as income, cash flow, balances and risk signals from your transactions, so the partner can understand your finances. The partner decides how to use them, including in any decision about you, and is responsible for telling you when it makes a decision based only on automated processing.
Privacy incidents
If a privacy incident creates a risk of serious harm, we will notify the people affected, the partner, and the Office of the Privacy Commissioner of Canada or Quebec's Commission d'accès à l'information, as the law requires, and keep a record of every incident.
Changes to this policy
We will post any change on this page and update the effective date. If a change is significant, we will give notice to partners, and through them to end users, before it takes effect.
Contact us
For questions about this policy or to make a privacy request, contact us at:
Nexbureau, Inc.1207 Delaware Ave #2116
Wilmington, DE 19806, United States
privacy@nexbureau.com
If you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada or, in Quebec, the Commission d'accès à l'information du Québec.