Privacy and data: Attachment Exporter

Last updated: 12 November 2026

This page adds the details for Attachment Exporter to the privacy policy of Kayabyte apps for HubSpot. Kayabyte is the trading name of Caner Kaya, Stasjonsveien 64, 0771 Oslo, Norway. For the customer data in your HubSpot account you are the controller and Kayabyte is the processor. This app handles customer files, so this page is more detailed than for our other apps.

What the app reads

With the read-only permissions you grant: the records you choose to scan or export (contacts, companies, deals or tickets: the record ID and the properties that name it, such as name, email address, company name or ticket subject), the notes, emails, calls, meetings and tasks associated with them (the attachment IDs and the date, not the text), the file-type properties of those records, the metadata of each file (name, type, size, access level) and the file content itself, which is fetched from HubSpot and written into your zip. It also reads your HubSpot lists and their members.

What the app stores

• Zip files of your exports, in a private storage bucket. They contain the files themselves.
• Manifest CSV files, with record IDs and names, file names, sizes and paths.
• Job data in our database: for every export, scan or audit, the settings you chose, one row per record (ID and name), one row per file reference (record, engagement, file ID, date) and one row per unique file (name, type, size, status), plus progress counters.
• Account details: the HubSpot account ID and name, the installing user’s ID and email address, the app admins’ HubSpot user IDs, your settings, and the OAuth tokens, encrypted. The email address of the person who starts an export is kept on the job so the ready email can be sent.
• Credits: a ledger per account with purchases, reservations and refunds, and the Stripe checkout session and payment IDs of each purchase. If a payment is refunded or charged back, the unused credits of that payment are removed from the ledger (and put back if a chargeback is won).
• A short event log (what kind of action happened, for which account and job), counters of API calls and counts of install sources, with no file or record names.

We do not store card numbers or bank details; Stripe handles payment.

Retention

• Zip files and manifests: the download links work for 7 days. The storage bucket has a rule that deletes objects after 7 days, and a daily clean-up deletes the zips of finished jobs after 7 days and marks the job as expired.
• Job rows (records, references, files): 30 days after the job was created, then deleted.
• Event log, API counters and install-source counts: 90 days.
• Cancelling or deleting a job in the app removes its zips and manifest at once.
• Uninstalling (in HubSpot, or the disconnect button in the app): running jobs stop, all zips and manifests of the account are deleted, all job rows and settings are deleted and the tokens are removed. An uninstall in HubSpot is normally picked up within an hour. The tokenless account record is deleted 30 days later. Where the free export had been used, a bare record stays (the HubSpot account ID and that one fact, nothing personal), so that installing the app again does not give a second free export.
• Credit ledger: kept, so a reinstall finds the credits you paid for. Email us to have it deleted. Stripe keeps billing records as the law requires.

Email

When an export or audit finishes, the app emails the person who started it, from support@kayabyte.dev through Resend, with counts and the download links. The email contains no file or record names. You can switch it off in the app’s settings.

Who sees what

Only app admins can scan, export and buy packs. The record card is shown to every user of your HubSpot account on the record page, and downloads that record’s files as a zip (at most 300 files, 40 downloads a day per account). The app cannot see which records a HubSpot user is allowed to open, so the card works for every record of the account; if only some users may see some records, do not add the card to that layout. Anyone who holds a download link can download that zip or manifest until the link expires after 7 days. The links are signed and tied to your account and the export, and cannot be guessed. Treat them like a password.

Logs

Our logs hold account IDs, job IDs, counts and error codes. We do not write file contents, file names or record names to logs.

Sub-processors

See sub-processors: Cloudflare (hosting, database, storage, queues), Resend (email) and Stripe (payments).

Your rights and questions

support@kayabyte.dev. We don’t sell data, share it, use it for advertising or use it to train AI models.