Privacy policy
Last updated: 17 October 2026. PullRows is designed so that your data passes through it and is not kept by us.
Who we are
PullRows is operated by [LEGAL NAME], [ADDRESS], Denmark, CVR [CVR NUMBER] ("we"). We are the data controller for the limited personal data described below. Contact: privacy@pullrows.com.
What the add-on accesses
Google user data
PullRows is a Google Sheets add-on. When you authorise it, it requests these Google permissions and uses them only as described:
| Permission | Used for |
|---|---|
See, edit, create and delete your spreadsheets (spreadsheets) | Writing synced rows into the spreadsheet where you enabled PullRows, including on a schedule while the sheet is closed. PullRows only writes to spreadsheets in which you configured a sync, and only to the tabs it creates. |
Connect to an external service (script.external_request) | Calling the Wrike API and, for licence checks, the Paddle API. |
Run when you are not present (script.scriptapp) | Creating the scheduled refresh trigger on Pro. |
Display sidebars (script.container.ui) | Showing the PullRows sidebar. |
See your primary email address (userinfo.email) | Matching your Google account to a Pro licence. |
PullRows' use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, do not sell it, and do not allow humans to read it except with your permission for support, for security, or as required by law.
Wrike data
You connect Wrike through OAuth with the read-only scope. PullRows reads tasks, folders, contacts, workflows and custom fields of the folders you choose, and writes them into your spreadsheet. We never see your Wrike password.
What we store, and where
| Data | Where | How long |
|---|---|---|
| Your Wrike OAuth access and refresh tokens | Google Apps Script user properties, inside Google's infrastructure, readable only by the add-on and only for your account | Until you click "Disconnect and delete tokens" or uninstall |
| Sync configuration (folder ID, chosen columns, filter) | Developer metadata on your spreadsheet, visible only to the add-on | Until you remove the synced tab in the sidebar |
| Licence status (Pro or free) with your email | Apps Script user cache and properties | Cached up to 6 hours; refreshed on demand |
| Your Wrike tasks | Only in your spreadsheet. PullRows has no server and keeps no copy. | Controlled by you |
PullRows runs entirely on Google Apps Script. There is no PullRows server that receives your Google or Wrike data. Script execution logs held by Google may contain error messages, which we avoid filling with personal data.
Payments
Pro subscriptions are sold by Paddle.com Market Ltd (or Paddle.com Inc. for some regions) as merchant of record. Paddle collects your payment details and email and handles VAT; see Paddle's privacy policy. To match your licence, the add-on sends the email address of your signed-in Google account to Paddle's API and receives back whether an active subscription exists. We do not receive card details.
Support email
If you email us, we keep the correspondence to answer you and improve the FAQ, for up to 24 months.
Legal basis and your rights (GDPR)
We process the data above to perform the service you asked for (Article 6(1)(b)) and, for support records, on our legitimate interest in running the product (Article 6(1)(f)). You can access, correct, export or erase your data and object to processing: use "Disconnect and delete tokens" in the add-on for the tokens, remove synced tabs for configuration, and email privacy@pullrows.com for anything else. You can complain to Datatilsynet, the Danish data protection authority.
Sub-processors
- Google LLC — Apps Script runtime, properties and caches (your data stays in your Google account's region handling).
- Paddle — payments and licence lookup by email.
- Wrike, Inc. — the source of the data, under your own Wrike agreement.
Changes
We will post changes here with a new date. Material changes to what Google user data we access will be re-consented through Google's permission flow.