This policy explains how Paffle Pay Inc. handles personal information when you visit our website, use Paffle, make or receive payments, contact us, or use our investor or affiliate portals. It also covers Invoices, Bills and Budgets, our add-in for Microsoft Excel.
Who we are
Paffle Pay Inc. is an Ontario corporation, number 1001404901. Our registered office is 2967 Dundas Street W., Unit 1035, Toronto, Ontario M6P 1Z2, Canada. “Paffle”, “we” and “us” mean that company.
Contact our Privacy Officer at privacy@paffle.com or write to our registered office.
Your business’s records and our responsibilities
We decide how to handle information for our website, accounts, subscriptions, support, portals, security and legal obligations. We are responsible for that processing, including as controller where that term applies.
A business generally controls the customer, supplier, employee and other personal information it puts into Paffle. We process those records on its instructions, including storing documents, sending invoices and making authorised filings. The business must have authority to supply and share that information.
Document notes and the files posted on them are part of the business’s records. Private messages between team members and conversations with our support team are treated differently: the business’s owners and admins cannot read them or download them through Paffle unless they are taking part in that conversation.
Payment partners may have separate responsibilities for verification and legally required records. If your information appears in a business’s records, contact that business first. For help directing your request, email privacy@paffle.com.
Information we handle
We handle account and business details, contact information, roles, preferences, subscription and billing records, and uploaded profile photos. Business records can include contacts, invoices, notes, bills, payments, budgets, stock, projects, timesheets, expenses, approvals and attachments.
Document notes. People in a business can write notes on a document, such as an invoice, bill or quote, tag a teammate and attach files. We keep the text, who wrote it and when, who was tagged, and each file.
Private messages. On plans that include them, two people in a business can message each other and attach files. We keep the text, who wrote it and when, each file, and each person’s own read position and whether they muted or archived the conversation. On the free plan, nobody can start a private conversation or send a private message, but people can still read the conversations they already have.
Support conversations. When you message our support team from inside Paffle, we keep your messages, our replies and any files. We also keep the kind of message you chose, the page you were on, your language, your business’s plan and the app version.
Shared screens. If you choose to share a browser tab or window in a support conversation, we use a relay provider to carry the live video to the Paffle support team member who last replied to you. You choose what to show and can stop at any time. A session lasts up to 20 minutes and carries no sound or remote control. Paffle does not record or store the video. If a staff member joins, we keep a record of the staff member, the business and when the session was active. This record contains no screen content and can remain after account erasure.
Files. We keep the file, its name, type and size, and a small preview of each image. When you add a picture, we remove details embedded in it, such as the place and time recorded in a photo. We do not change PDFs or workbooks, so any details inside those stay. Notes and private messages accept PDF files, Excel workbooks and PNG, JPEG and WebP images. Support conversations accept the same, except workbooks.
Sign-in information includes password hashes, Google or Microsoft account identifiers, names and verified email information. Google may also supply a profile-picture URL with its sign-in response; that is distinct from a photo you upload to Paffle. We do not receive your Google or Microsoft password or save their access or refresh tokens for sign-in. Two-step sign-in uses an encrypted secret and hashed recovery codes.
Enabled financial services involve identity, business, recipient, bank or wallet, billing, transaction and verification information. This includes personal bank details saved for reimbursements. Some verification documents go directly to a partner’s hosted process.
We also handle enquiries, support messages, technical error reports and security events. Some network-address records are hashed; they are not necessarily anonymous. Portal records include applications, access, referrals, commissions and payments. Signed confidentiality agreements can record your name, email, signature, signing time, IP address and browser information.
Information comes from you, your business, people transacting with it, connected services and relevant verification partners or lawful verification sources. Supported blockchain transactions create public records that we cannot edit or erase.
Why we use information
We use information to provide the service, follow authorised instructions, manage subscriptions, deliver documents and notices, administer portals, provide support, maintain security, investigate misuse and meet legal obligations. Optional marketing is not a condition of an account.
We obtain consent where required. Where GDPR or UK GDPR applies, relevant grounds can include a contract, steps requested before a contract, legal obligations, consent or legitimate interests such as security and support. Those grounds do not replace consent where another law requires it.
We do not sell personal information or give it to data brokers. We do not use business financial records for advertising or to train general-purpose AI models.
AI features
Using the assistant can send your question, conversation context and relevant business information to our AI provider. Document extraction can send the uploaded document to that provider to suggest a draft. Review answers and drafts before relying on them. You can use Paffle without the assistant or document extraction.
Assistant conversations are saved to your account. When you request human help or an unresolved question is escalated, the conversation may be emailed to support with your email address, business and role.
We use a business API whose inputs and outputs are not used for model training by default. We do not opt business records into training. Provider processing and retention remain subject to its service terms. Share only information you are authorised to provide.
The assistant and document extraction do not read document notes or private messages. They see such text or a file only if you put it into a question or upload it yourself.
Support replies. When a member of our support team asks for a suggested reply to your support conversation, we send our AI provider the words of that conversation, how many files of each kind it holds, and your business’s plan, country and the features its plan includes, together with our product guide. We do not send your name, your email address, your business’s name or the files themselves. The AI provider writes a draft for our team member, who reads and edits it and decides what to send. It sends nothing to you by itself and does not see your other records.
Security monitoring. We automatically check sign-ins, API keys, downloads and new payment recipients for signs of misuse, such as a burst of failed sign-ins followed by a successful one. When a check is triggered, we send our AI provider a summary of that activity: the kind of check, counts, times and internal reference numbers. We do not send names, email addresses, network addresses or the words of your records or messages. The AI provider suggests whether the activity looks like misuse. Our staff are alerted and decide what to do. The monitoring takes no action on your account by itself.
Recipients and service providers
People in your business receive access according to their permissions. Authorised sharing can disclose information to document or payment recipients, connected services and tax authorities. Links and exported files can be passed on, so check recipients and access before sharing.
Document notes and their files can be read by people in the business who can currently view the whole document. Someone who can see only part of a document cannot read its notes. The person who made an expense claim can read the notes on their own claim. Owners and admins can also download notes and their files in a business archive.
Private messages and their files can be read by the two people in the conversation, while they still have access to the business. No one else in the business can read or download them, including owners and admins. If one person leaves or is removed, the other can still read the whole conversation but can no longer send in it. The person who left cannot read it again, even if they rejoin the business.
Support conversations and their files can be read by the person who started the conversation, while they are in that business, and by our authorised support staff, who must use two-step sign-in. Our staff also see that person’s current name and email address and the business’s name. You may see the first name and profile photo of a staff member who replies. No one else in the business can read these conversations. When our team asks for a suggested reply, the conversation is also processed by our AI provider, as described in the AI features.
Paffle has no staff screen for reading document notes or private messages. Notes and private messages can create an in-app notice for eligible recipients. The notice does not contain their words, and we do not email these notices. Document notes, private messages and support conversations are not sent through API keys, webhooks, accounting connections or the Excel add-in.
When you start a support conversation or send the first reply after our team updates it, we try to email our support inbox with your email address, your business’s name and a link to the conversation. The email does not contain your words or your files.
Everyone in a business can see how much attachment storage it has used in total. Owners and admins can also see that total divided between notes, private messages and support requests. This does not show whose files they are or what they contain.
We use these service-provider categories:
Category | Purpose | Processing locations |
|---|---|---|
Website and application hosting | Operate the website, forms and application | International, including the United States |
Database and file storage | Store account records, business records and files | United States |
Email and support | Deliver messages and handle correspondence | Email delivery: United States; support depends on the service |
Technical monitoring | Diagnose errors and protect the service | United States |
AI | Answer questions, extract document drafts, draft support replies and assess security alerts | United States |
Payment, billing and verification | Process subscriptions, enabled payments and verification | United States and other relevant countries |
Tax-document services and authorities | Register and file documents where enabled | International, including the relevant authority’s country |
Screen-sharing relay | Carry live video for support screen sharing between the two browsers | International, including outside Canada |
For provider identities, relevant processing locations and safeguards, email privacy@paffle.com. Partners may issue their own privacy notices for processing they control.
We may disclose information to advisers, authorities or courts where necessary and lawful, or during a corporate reorganisation, acquisition or transfer with applicable protections. The Google-specific consent limits below still apply.
Google and other connections
Signing in with Google does not itself connect Google Sheets. Connecting Sheets requests Google’s drive.file permission. That permission generally covers files an app creates and files you explicitly open or choose for it; it is not limited to one spreadsheet.
Paffle creates a spreadsheet for each connection. Its connector does not browse your Drive or import your existing spreadsheets. It writes eligible invoice, credit-note and debit-note rows, and customer-credit allocation and removal rows. Each row holds the document's number and type, its dates, the customer's name and email address, the currency, the amounts and, where there is one, the tax authority's reference. It never sends customers' tax numbers, postal addresses, phone numbers or invoice line items. It also reads the credit-column heading cell, L1, and can add a missing heading. Sending depends on the connection, permissions, plan and delivery controls; it is not a promise that every row appears immediately or automatically. Previously created spreadsheets may remain within the Google authorisation.
We encrypt both Sheets access and refresh tokens and retain connection information such as spreadsheet references, the connecting member and token or grant expiry. These connection tokens differ from sign-in data.
Manual disconnect requests revocation of the Google grant on a best-effort basis and deletes the local connection and tokens. Removing the member who connected Sheets, or erasing that account, detaches the affected local connection without revoking Google’s overall grant, which could affect other businesses. Spreadsheets remain in Drive, and delivery and audit history may remain in Paffle. You can revoke Paffle’s access through your Google Account settings.
Paffle’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements. We do not use Google user data, or anything derived from it, to develop, improve or train AI or machine-learning models. We use it only for visible user-facing features and permitted improvements, never for advertising, sale, creditworthiness or lending. Transfers are limited to providing or improving those features with your consent, security, legal compliance, or a merger, acquisition or asset sale with your explicit prior consent. Human access requires your affirmative agreement for specific data, necessity for security or legal compliance, or aggregated internal operations permitted by applicable privacy and other law.
Other accounting connections may look up customers, tax codes, items or accounts to post records correctly. This does not import your existing ledger. We keep references, returned amounts, currencies and delivery information needed for the connection. Connected channels and webhooks can disclose notices to people outside your business.
API keys can allow business-wide access within their scope; they do not inherit an individual’s narrower allocation access. In the Excel add-in, your access follows the permissions on your own Paffle account. Disconnecting stops new requests; one already in progress may finish. Records already delivered remain with the destination.
Invoices, Bills and Budgets is Paffle’s add-in for Microsoft Excel. You can copy records you have permission to see into your workbook and upload worksheet rows to Paffle for review. The add-in sends information only to Paffle, and this policy explains how we handle it. Microsoft’s terms and privacy statement apply to Excel and Office.
You sign in to the add-in through Paffle’s own window, separately from your Excel account and Office single sign-on. Use any sign-in method available for your Paffle account, including Google or Microsoft if you use them for Paffle.
A business owner or admin creates a connection key in Paffle. We keep only a hash of the key and its last four characters. We show those characters so you can recognise the key.
The add-in saves your business ID and key in the storage Excel gives it on your device, outside the workbook. You can remove both in the add-in. A business owner or admin can revoke the key in Paffle and end the sessions that used it.
You need your own Paffle account as well as the connection key. Sign in through Paffle with the usual sign-in and two-step checks, then confirm your account and business. Your session lasts up to 15 minutes and stays in the add-in’s memory. Sign in again after restarting Excel. For each request, we check your current business membership, permissions, allocation access, seat and plan.
When you pull records, the add-in requests only the records you can access. It copies them to a new worksheet in your workbook. The copies stay wherever you store that workbook, even if you sign out, the key is revoked or your access changes. Loading a template sends nothing to Paffle.
When you sign in, choose whether to allow uploads. If you allow them, the add-in sends the rows you filled in to Paffle, which checks them against your current access. Rows that pass the checks become a proposal linked to you, your business and the connection. We discard refused values and keep a receipt showing which rows were accepted or refused and why.
Only the person who uploaded the rows can accept the proposal. Accepting it creates a record or draft in Paffle. Sending, filing and payments are separate steps, and your business’s usual approvals still apply.
The add-in writes each row’s result and hidden reference to the worksheet, along with a record of the upload. If Excel misses Paffle’s reply, the add-in can use this information to check what happened without sending the rows again.
Our Windows desktop add-in for Excel is separate from the add-in in Microsoft Marketplace. It uses the same connection keys and sign-in process. If you choose to remember the connection, Windows encrypts a file with your business ID and key for your Windows account. Disconnecting deletes that file.
The add-in also keeps a browser profile for Paffle sign-in and an encrypted upload record that includes the rows sent and Paffle’s reply. It uses that record to check a missing reply without sending the rows again. Both stay in your Windows user profile and can’t be deleted from within the add-in.
International processing
We are based in Canada and use providers internationally, including in the United States. Information may be processed outside your country, where authorities may have lawful access powers.
We remain responsible for protections required when providers process information for us. Where transfer restrictions apply, a permitted basis and required safeguards must be used. Email privacy@paffle.com to ask which safeguards apply and how to request details or a copy where available.
Retention
Business financial, tax, verification and transaction records remain while the business uses Paffle and for applicable legal periods afterwards. Canadian money-services records can require at least five years, with the starting point depending on the record. Canadian tax records generally require six years from the end of the last relevant tax year. Other laws and exceptions can differ.
Audit and portal logs currently have no automatic expiry and can identify people after account erasure. Budget history includes saved line names for as long as the business uses Paffle. Each time you agree to our Terms and Privacy Policy, we record which versions you agreed to, when, and how (when creating an account, when first signing in with Google or Microsoft, or on the agreement page). These records have no automatic expiry and stay linked to the account after erasure. Signed confidentiality agreements remain signed legal records; affiliate commissions and payments remain financial records.
We retain affiliate payout records, including the account holder’s name and where each payment was sent (such as a wallet address), and the investor register and recorded votes after account erasure as financial and company records.
Sign-in and account security events are kept for twelve months and then deleted. Email suppression records for unsubscribes, bounces and spam complaints are kept indefinitely to avoid restarting unwanted mail.
Security alerts, and our staff’s assessment of each one, are kept for twelve months, including after an account is erased, and then deleted.
Our daily cleanup removes Excel add-in sign-in and session records 30 days after they expire. The audit log keeps the time each session started. We keep proposals and upload receipts with your business records while your business uses Paffle. Your business data export includes them.
Assistant conversations, feedback and notifications remain while the account is open and are deleted from the active application at erasure. Copies emailed to support may remain for service or dispute records. Uploaded files generally remain with their associated records. Files in notes, private messages and support conversations are covered below.
Document notes and their files have no automatic expiry. They stay with their document and are deleted if the document is deleted. Private messages and their files have no automatic expiry while either person is still in the business under the membership they had when the conversation started. Once both of those memberships have ended, nobody can open the conversation. We delete it and its files through scheduled cleanup after two years have passed from the later of its last message and the first time our scheduled check sees that both memberships have ended. Once sent, people cannot edit or delete individual notes or private messages. We replace tags to an erased account as described in section 10.
Support conversations and their files have no automatic expiry. They remain after the person who started the conversation leaves the business. If that person’s account is erased, we delete those conversations and their files.
A file in a note, private message or support conversation can be deleted sooner (see section 11). The message stays and shows the file’s name and that it was deleted, and we keep when it was deleted and by whom. We then delete the file from our file storage through a scheduled clean-up. The business’s audit log records who deleted a file, its size and, for a note, the document, but not the file’s name or which private or support conversation it was in.
Encrypted database backups are kept for up to 24 months under our retention schedule. Backups and provider logs are not normally edited to remove individual records; their contents expire under their respective schedules. Legal holds, regulatory duties or unresolved disputes can require longer retention. Retained information remains protected and limited to justified purposes. Those backups include the words of notes, private messages and support conversations, and file names. Files are not part of these database backups.
Account erasure
A person reviews erasure requests, including the consequences for a business with only one owner. Erasure removes or replaces profile identifiers, clears personal reimbursement bank details, ends business and portal access, revokes sign-in and removes linked sign-in identities.
We delete two-step sign-in settings, assistant conversations, feedback, the person’s support conversations with our replies and every file in them, files they chose for a note or message but never sent, notifications and referral invitations sent by that account. Profile photos are removed from the account and deletion of stored photo files is requested. The Sheets connection treatment is described above.
Erasure does not delete what the person said to others. Notes they wrote and private messages they sent or received stay, and the people who can open those conversations can still read them. We remove the direct link from those messages to the person’s account, and their name no longer appears beside them. Where someone tagged them in a note, the tag then reads “@Former member”. Other words stay, including any name or detail someone typed, such as someone signing a message. Files they sent also stay, with their file names, under the deletion and retention rules in section 9. Internal reference numbers for their former account and membership stay with these records; they are not names, but they are not necessarily anonymous.
Leaving a business, or being removed from one, is not erasure. The person can no longer read the business’s notes or their private messages there, and their name stops appearing beside what they wrote, but those records stay. Their support conversations stay too, and they can read them again only if they rejoin that business.
Business documents, historical audit and portal entries, records of agreement to our Terms and Privacy Policy, signed agreements, commissions and legally required records can remain identifiable. We also retain the erasure request and outcome, suppression records and security events for their stated periods. Information already delivered to recipients or support and copies in backups follow the relevant retention arrangements. Erasure does not make all historical information anonymous.
Choices and rights
Depending on applicable law, you may request access, correction, a copy, deletion or restriction, object to processing, or withdraw consent. Legal retention, other people’s rights and business-controlled records can limit a request.
For privacy requests, email privacy@paffle.com. We may verify your identity and authority. We respond within the applicable legal deadline, usually 30 days, and explain permitted extensions or refusals as required.
Owners and admins can download a business archive; other exports depend on permissions and features. Archives include document notes and their files. They exclude credentials, private messages and their files, support conversations and their files, personal assistant workspaces, notifications and certain Paffle operational records. A file deleted from a note has no copy in the archive, but its name, who deleted it and when stay listed. A privacy access request is separate from these export features.
You can download a plain-text transcript of your own support conversation. While you have access to a business, Settings, Attachment storage shows which files you can delete, including eligible files you sent during your current membership, on any plan. Either person in a private conversation can delete any file in it while their original membership is still active. Once you leave a business, you can no longer delete files you sent there, even if you later rejoin. A business owner can delete any file in the notes they can open, and can delete files in private conversations that nobody still in the business took part in; for those, the owner sees only how many files there are and their total size. Nobody in a business can delete a file our support team sent. Archiving or muting a conversation changes only your own view of it.
A business owner can also delete customer support files when the membership under which they were sent has ended, even if the person rejoins. For older uploads that lack that membership record, the owner can also delete the files. The owner sees only how many files there are and their total size.
Use marketing unsubscribe links or email privacy@paffle.com. Weekly-statement opt-outs apply to the named business; referral opt-outs stop Paffle invitations. Bounces or spam complaints suppress statements and referral invitations to that address. These controls do not automatically stop a business’s own document emails. Essential service notices can continue.
You may complain directly to the competent authority, including Canada’s Privacy Commissioner, Nigeria’s Data Protection Commission, or the relevant UK or European authority.
Security and children
We use access controls, protected sign-in, encryption, business access restrictions and audit records. Files in notes, private messages and support conversations are kept in private storage with no public links, and we check the person’s access each time a file is opened. Notes, private messages and support conversations are not end-to-end encrypted: our systems can read them in order to show them to the people allowed to see them. Error monitoring is configured to remove credentials, cookies and unnecessary personal information. No system guarantees complete security. Report security concerns to support@paffle.com.
Accounts and programmes are for adults aged 18 or over. Businesses may lawfully hold information about younger people and must provide the necessary permissions and protections. Email privacy@paffle.com about improper collection.
Cookies and browser storage support sign-in, security, preferences and saved connections, including the Excel add-in's business ID and connection key. Our Cookies Policy explains these technologies. Browser controls may affect functionality; optional tracking requires consent where applicable.
Changes
The date above identifies this version. We give appropriate notice of material changes and seek fresh consent where required before using information for a new purpose.