ASAPBase Privacy Policy
1. Who we are
The data controller is ASAPCOMMERCE SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ (a Polish limited liability company), pl. Jana Kilińskiego 2, 35-005 Rzeszów, Poland, tax ID (NIP) 5170456078, REGON 540916650, entered in the Register of Entrepreneurs of the National Court Register (KRS) kept by the District Court in Rzeszów, 12th Commercial Division, under KRS number 0001155955, share capital PLN 10,000.
ASAPBase is a panel for managing online sales: marketplaces, online stores and analytics. Website: https://asapbase.com, application: https://panel.asapbase.com.
Privacy contact: asapdevs2016@gmail.com.
2. What data we process
- Panel user account data — email address, name, company details.
- Data from stores and marketplaces connected by the customer — orders, products, offers and buyer data. We process this data on the customer's behalf, as a data processor.
- Technical data — logs, IP address and the session cookies required to sign in.
3. Google user data
We access data from Google services only after the user gives explicit consent on the Google consent screen (OAuth 2.0), and only for the services the user chooses to select. The user picks the Google services to connect on one consent screen (Integrations list → Google), and we ask only for the scopes of the services selected there; Google Business Profile is connected through its own sign-in. Google user data is used solely to provide the user-facing features described below, inside the user's own panel.
Scopes we request and why
-
https://www.googleapis.com/auth/analytics.readonly— read aggregated traffic and sales statistics from Google Analytics 4 (sessions, users, purchases, revenue by day, channel, device and landing page) so we can show them in the panel next to order data. Used in: sales and traffic reports and the AI assistant answers about traffic. -
https://www.googleapis.com/auth/webmasters.readonly— read Search Console data (clicks, impressions, CTR, position by query, page and day) to analyse organic visibility. Used in: Search Console reports and the AI assistant answers about organic search. -
https://www.googleapis.com/auth/adwords— read Google Ads campaign statistics (cost, clicks, conversions, impression share, change history) for profitability reports. The application does not create, modify or delete campaigns, budgets or bids. We use this scope for reading only, even though Google does not offer a narrower read-only scope for the Google Ads API. Used in: Google Ads screens (campaign costs and recommendations) and profit reports per product. -
https://www.googleapis.com/auth/content— read the list of products and their statuses in Google Merchant Center so we can match advertising costs to products and show which products are missing from or disapproved in the product feed. Used in: Google Ads screens. -
https://www.googleapis.com/auth/business.manage— read Google Business Profile locations and reviews, and publish replies to reviews only when the user explicitly tells us to (the user writes or approves each reply and clicks Send). Used in: the reviews (comments) screen.
What we store
Access and refresh tokens (encrypted in our database), the identifiers of the resources the user selected (GA4 property, Search Console site, Google Ads account) and the aggregated statistics we have retrieved. We do not collect Google passwords. We do not collect personal data of visitors to our customers' websites — Google Analytics 4 and Search Console return aggregated data.
How we use it
Only to show reports and analyses to the user who connected the account, in their own panel. Each customer sees only their own data.
AI assistant
When a user asks the AI assistant in the panel a question, the aggregated figures needed to answer it (for example campaign cost and revenue, or the number of sessions) may be sent to the language model provider chosen and configured by the customer (OpenAI, Google Gemini or another OpenAI-compatible provider the customer configures), solely to generate that answer. We never send tokens or sign-in credentials. This feature is optional: it works only when the AI assistant is enabled for the customer's account and the customer has configured a provider.
What we do not do
- We do not sell Google user data.
- We do not share it with third parties, other than the AI assistant case described above and the processors required to run the service (hosting).
- We do not use it to serve, target or personalise advertising.
- We do not use it to train generalised AI or machine learning models.
- We do not use Google APIs or Google user data to create, generate or distribute non-consensual intimate imagery (NCII) or any other sexual or intimate content. ASAPBase does not generate images at all.
- We do not use it to determine creditworthiness or for lending purposes.
- Humans do not read this data unless the user explicitly asks us to (for example for support), it is necessary for security purposes, or it is required by law.
ASAPBase'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.
Revoking access and deleting data
You can disconnect a Google service in the panel at any time: Integrations list → Google → Disconnect. We then delete the stored key of that service and stop retrieving its data. When no other Google service connected in your shop still uses the same token, we also revoke it at Google. You can also revoke the application's access at https://myaccount.google.com/permissions.
Statistics retrieved earlier remain in the panel until you ask us to delete them or close your account. We delete them within 30 days of a request sent to asapdevs2016@gmail.com.
4. Legal bases and retention
- Article 6(1)(b) GDPR — performance of the contract for using the panel.
- Article 6(1)(f) GDPR — our legitimate interest in keeping the service secure and developing it.
- Article 6(1)(a) GDPR — consent, when you connect an integration.
We keep data for the duration of the contract and then for the limitation period for legal claims. Google user data follows the rules in section 3.
5. Recipients and processors
- A hosting provider based in the European Union.
- Providers of the integrations the customer chooses (marketplaces, stores, carriers, email provider, AI model provider) — only to the extent needed for the feature the customer has turned on.
6. Your rights
You have the right to access your data, have it corrected or deleted, restrict its processing, receive it in a portable format and object to its processing. You can also lodge a complaint with the Polish data protection authority (Prezes Urzędu Ochrony Danych Osobowych). To exercise these rights, write to asapdevs2016@gmail.com.
7. Security
- Connections to the panel are encrypted (HTTPS).
- Tokens and API keys are encrypted in the database.
- Each customer's data is isolated from other customers' data.
- Only authorised staff have access to data.
8. Cookies
The panel uses only strictly necessary cookies: session cookies and CSRF protection. There are no advertising cookies in the panel.
9. Changes to this policy
We may update this policy when the service or the law changes. The current version is always available at this address, and the date of the last change is shown at the top of the page.