Privacy policy
How Paysweep handles your data. Last updated 25 October 2026. This policy covers the service at paysweep.atesensoftware.com.
This policy is written to describe what the software actually does. It is not legal advice. If anything here is unclear, ask us.
Who we are
Paysweep is operated by Samet Ateşen, trading as Atesen Software, Sakarya, Türkiye (“we”, “us”). You can reach us at support@atesensoftware.com.
What we keep, and for how long
You choose a CSV or Excel file in your browser. An Excel file’s first sheet is turned into CSV text in the browser; that CSV text is sent to our server over HTTPS to build the preview, and the file itself is not stored. What we keep is the mapped rows needed for the preview and the payments: invoice numbers or IDs, amounts, dates, account codes, references and currency rates.
| Data | How long |
|---|---|
| Sign-in details. Your Xero user ID, name and email address, received from Xero when you sign in. | While the account has an organisation connected. Deleted within 30 days of disconnecting the last organisation, or on request. |
| Xero tokens. The access and refresh tokens Xero issues when you authorise a connection. Encrypted at rest (AES-256-GCM). | Deleted the moment you disconnect the organisation in Paysweep. Disconnecting also asks Xero to revoke the connection. |
| An unused preview. The payments Paysweep would record from your mapped rows (invoice ID, amount, date, account, reference, currency rate and the amount due at the preview), stored as encrypted records. A preview that is never run. | Deleted after 24 hours. |
| Run records. Once you run a preview, the same encrypted payment records stay so that Undo can work, together with one row per payment: its file row number, the Xero IDs of the invoice and of the payment, and its step and outcome. | The encrypted records are deleted 30 days after the run starts, or immediately when the organisation is disconnected. |
| Audit log and run rows. Invoice ID, payment ID, file row number, outcome and reason codes, timestamps and the idempotency key. No contact names and no amounts. | 12 months. |
| Billing records. Paddle customer, subscription and transaction IDs, the plan and the period. We never receive card data. | As long as the plan needs them and our legal and tax obligations require. |
| Thank-you email record. After a purchase, the purchase key (a Paddle transaction or subscription ID), whether the one email was sent, and when. Neither your address nor the message is stored. | Kept with the billing records. |
| Server logs. IDs and codes only. Never tokens, names or amounts. | See “Hosting” below. |
Cookies
The pages you are reading load no scripts and nothing from other sites, and Paysweep uses no analytics or advertising service. The server sets three cookies of its own, and these are the only cookies Paysweep sets:
| Cookie | What it is for | Lasts |
|---|---|---|
| cl_session | Keeps you signed in. Essential. | 14 days |
| cl_oauth | Carries the sign-in handshake with Xero from start to finish. Essential. | 10 minutes |
| cl_src | Set on your first visit only. It records the website you came from (its host name), the page you landed on and any utm_ tags in the link, so we know which guide or link brought you. It is not set when your browser sends Do Not Track or Global Privacy Control. | 30 days |
The thank-you email
Paying happens at Paddle’s checkout, which is governed by Paddle’s own terms and privacy notice. After a purchase Paddle sends you its receipt. We may also send one plain-text thank-you and quick-start email to the address on your Paddle payment record, through Resend. We read that address from Paddle at that moment and we do not store it, or the message. The email has no tracking pixel, image or redirect link, and it is sent once per purchase.
What we do not do
We do not sell your data and we do not use it for advertising. We do not use Xero data to train AI or machine-learning models. Xero data is used only to do what you asked Paysweep to do.
What we ask Xero for
Your sign-in identity (the scopes openid, profile, email and offline_access); accounting.invoices, which Paysweep uses to find the invoices and bills named in your file and read the amount still due on each; accounting.payments, which Paysweep uses to record the payments you confirm and, for Undo, to read them and set them to deleted; and accounting.settings.read, read-only access to the organisation’s settings, which lets Paysweep check that the bank or clearing account in your file can take payments. Paysweep does not change invoice lines, contacts or bank statement lines. We do not ask for access to bank feeds or reports.
Why we process it
To provide the service you signed up for (contract), to keep it secure and working (legitimate interest), and to meet our legal and tax obligations (legal obligation).
Service providers
- Cloudflare provides the hosting and the database. It processes data on our instructions.
- Paddle takes payments as seller and merchant of record, under its own terms and privacy notice.
- Resend delivers the one thank-you email described above, under its own terms and privacy notice.
- Xero is the source of the data. You authorise the connection, and you can remove it in Xero at any time.
Hosting
Paysweep runs on Cloudflare. Like any host, it processes technical request data, such as your IP address, to deliver pages. Our own server logs hold IDs and codes only.
International transfers
Our providers may process data outside the country you are in. We rely on the contractual safeguards those providers offer.
Retention and deletion
- Disconnecting an organisation deletes its Xero tokens at once and removes its stored previews and run records. Undo is no longer possible after that.
- A preview you never run is deleted after 24 hours.
- The encrypted payment records of a run are deleted 30 days after it starts.
- The audit log and job rows are kept for 12 months, then deleted.
- Sign-in details are deleted within 30 days of disconnecting the last organisation, or on your request.
Security
Xero tokens, previews and run records are encrypted at rest. Everything travels over HTTPS. Besides the sign-in identity, we ask Xero for the invoices and payments permissions, plus read-only access to settings. If we become aware of a breach affecting your data, we will notify you and Xero promptly.
Your rights
Depending on where you are (for example under the GDPR and UK GDPR, the Australian Privacy Act, the New Zealand Privacy Act, or Türkiye’s KVKK) you may ask for access to your data, correction, deletion, or a copy in a portable form. Email support@atesensoftware.com from the address on your account and we will answer within 30 days. If you are not satisfied, you may complain to your local data protection authority.
Children
Paysweep is a business tool and is not directed at anyone under 18. We do not knowingly collect data from children.
Changes to this policy
We will post updates on this page and change the “last updated” date above. If a change is material, we will email you before it takes effect.
How to ask us something
Email support@atesensoftware.com. The support page explains what to include so that we can answer on the first reply.
Every payment recorded against the right invoice or bill in Xero, with a result CSV, a link to each document and Undo for 30 days.
Who it is for: Bookkeepers, accountants and finance teams on Xero with a list of payments to enter: a remittance advice, a batch of bills paid outside Xero, or a clean-up of old open invoices.
Start free with XeroCompare plans
Free to connect and preview. First 3 payments free, then $39 for 7 days or $19 a month, excl. VAT/sales tax.
Three steps

Sign in with Xero
You sign in on Xero’s own page and choose the organisation. Paysweep never sees your Xero password.

Upload and preview, free
Choose a CSV or Excel file with one row per payment. Every row is checked against your invoices, bills, accounts and lock date. Nothing is written yet.

Type PAY to record
Type PAY and the number of payments. You get a result CSV, a link to each invoice or bill in Xero, and Undo for 30 days.