Parties
- Burst Inc. (Burst株式会社), 1-4-3 Sengencho, Nishi-ku, Yokohama, Kanagawa 220-0072, Japan ("Burst", "we"). Contact: info@burst-tech.com.
- The business that installed Rekotto from the Shopify App Store for its Shopify store (the "Merchant", "you").
This addendum forms part of the Rekotto terms of service (the "Terms") between you and Burst. It sets out how Burst handles personal data of your shoppers when it runs the Rekotto quiz for you, as Article 28 of the EU GDPR and of the UK GDPR requires.
1. Scope and definitions
1.1 This addendum applies when you are established in the United Kingdom or the European Economic Area (the EU, Iceland, Liechtenstein and Norway), or when your use of Rekotto is otherwise subject to the EU GDPR or the UK GDPR.
1.2 In this addendum:
- "Data Protection Law" means the EU GDPR (Regulation (EU) 2016/679), the UK GDPR, the UK Data Protection Act 2018, and the national laws that implement or supplement them, each as amended.
- "Shopper Data" means the personal data described in Annex 1 that Burst processes for you when a shopper uses a Rekotto quiz on your store.
- "Personal data", "controller", "processor", "processing", "personal data breach" and "supervisory authority" have the meaning given in Data Protection Law.
- "Services" means the Rekotto app, the hosted quiz, the dashboard and related support, as described in the Terms.
1.3 This addendum covers Shopper Data only. Information about your own staff and account (names and emails of people who use the dashboard, billing and support records) is handled by Burst as a controller. It is described in Burst's privacy notice, not here.
2. Roles
2.1 For Shopper Data, you are the controller and Burst is your processor. You decide whether to use Rekotto, what the quiz asks, and which optional features you switch on.
2.2 You are responsible for having a lawful basis for the processing, and for telling shoppers about it. Burst supplies text you can use (Annex 1, part 6). If you ask shoppers for information that falls in a special category of data under Article 9 of the GDPR (for example, a question about a health condition), you are responsible for the lawful basis, including explicit consent where needed. Burst does not design the standard quiz to collect special category data and does not ask you to.
2.3 Burst will not process Shopper Data as a controller. If a law or a court requires Burst to do something with Shopper Data that goes beyond your instructions, Burst will tell you first, unless the law forbids it.
3. What is processed
3.1 The subject matter, duration, nature and purpose of the processing, the categories of data and of people, and the optional features are in Annex 1.
3.2 Burst processes Shopper Data for as long as you use the Services, and afterwards only as clause 11 says.
4. Burst's instructions and limits
4.1 Burst processes Shopper Data only on your documented instructions. Your instructions are: this addendum, the Terms, and the settings you choose in the app, including switching an optional feature on or off. Running the quiz as configured, producing your dashboard and reports, giving you support, fixing a fault in your store's use of Rekotto, keeping the Services secure, and counting your plan's monthly quiz usage are all within your instructions.
4.2 If Burst believes an instruction breaks Data Protection Law, it will tell you without delay and may pause that instruction until you confirm or change it.
4.3 Burst does not use Shopper Data for its own purposes. In particular, Burst does not:
- use Shopper Data to improve or tune its products, scoring rules, recommendation packs or any model;
- create, publish or share statistics, benchmarks or reports from Shopper Data, including statistics from which you cannot be identified;
- include your Shopper Data, or counts or rates derived from it, in any comparison with, or total across, other merchants' stores (Burst leaves a store out of those figures on the basis stated in clause 4.6);
- combine your Shopper Data with other merchants' data, or with data from any other source, to build profiles;
- sell, rent or disclose Shopper Data for advertising, or use it for advertising.
4.4 Clauses 8(2) and 8(4) of the Terms, which allow Burst to use answer data for quality improvement and to create and publish statistics, do not apply to Shopper Data of merchants covered by this addendum. If they conflict with this addendum, this addendum wins.
4.5 Burst may rely on information that is not Shopper Data to run its business, for example information about how its own dashboard is used, or billing records. That is outside this addendum.
4.6 How Burst knows a store is covered. Burst goes by the country of the store's own address, as Shopify reports it when you open the app. A store whose address is in the UK or the EEA is left out of every figure Burst's operator console builds from shoppers' quiz activity, and its age and gender estimate (Annex 1, part 6) is off until you switch it on. If your address is elsewhere but your shoppers are in the UK or the EEA and you want the same treatment, tell Burst and it will apply it. Burst also applies it on its own when your store's Shopify shipping settings, which the app reads when you open it, include the UK or an EEA country.
5. Confidentiality
5.1 Burst allows only those of its people who need Shopper Data to deliver the Services to access it, and holds each of them to a duty of confidentiality that continues after they stop working with Burst.
6. Security
6.1 Burst applies technical and organisational measures appropriate to the risk, as Article 32 requires. The measures in force are in Annex 2. Burst may change them if the protection does not get worse, and will tell you of a material reduction.
7. Sub-processors
7.1 You give Burst a general authorisation to use the sub-processors listed in Annex 3 for the purposes and in the locations stated there.
7.2 Burst will tell you before it adds or replaces a sub-processor, at least 30 days ahead, by email to the contact address on your account and by updating Annex 3. You may object on reasonable data protection grounds within that period. If the parties cannot resolve the objection, you may end your use of the affected part of the Services before the change takes effect, and Burst will refund the unused part of any prepaid period.
7.3 Burst has a written contract with each sub-processor that requires it to meet the same data protection obligations as this addendum, to the extent that applies to what the sub-processor does. Burst remains responsible to you for its sub-processors' performance.
8. International transfers
8.1 Burst is in Japan, and the Shopper Data is stored and processed in Tokyo (Annex 3). Transfers of your Shopper Data to Burst rely on:
- for data coming from the EEA, the European Commission's adequacy decision for Japan (Decision (EU) 2019/419), which covers private-sector organisations subject to Japan's Act on the Protection of Personal Information;
- for data coming from the United Kingdom, the UK's recognition of that same decision under paragraph 5 of Schedule 21 to the Data Protection Act 2018, which covers transfers to private-sector organisations subject to Japan's Act on the Protection of Personal Information.
8.2 If either adequacy finding stops applying to the transfer, the parties agree that the following apply from that date without further signature, and Burst will give you the details needed to complete them: for EEA data, the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914), Module Two (controller to processor); for UK data, the UK International Data Transfer Addendum to those clauses or the UK IDTA. The annexes to those clauses are completed from Annexes 1 to 3 of this addendum.
8.3 Where a sub-processor moves Shopper Data outside Japan (Annex 3 shows where), Burst ensures a valid transfer mechanism covers it and states which one in Annex 3.
9. Helping you meet your own duties
9.1 Requests from shoppers. If a shopper asks you for access to, or deletion of, their data, Burst will help you with appropriate technical and organisational measures. Because the quiz stores no name, email or other direct identifier, Burst can only find a shopper's records through the session link that Shopify's order data provides (clause 9.2). Where Burst holds no information that identifies a shopper, it is not required to collect more in order to find them (Article 11 of the GDPR).
9.2 The method Burst uses for shoppers who bought is this. Shopify sends Burst the customer data request or deletion request for an order (the customers/data_request and customers/redact notices). Burst uses that order's details to find the quiz session that led to it, then sends you the records (for a data request) or deletes them (for a deletion request). A shopper who used the quiz and did not buy, or whose purchase cannot be linked to a quiz session, cannot be found by Burst; Burst will say so. After the Merchant has uninstalled the app, Burst can no longer read order data from Shopify, and the deletion in clause 11 applies instead.
9.3 If a shopper writes to Burst directly, Burst will not answer on its own account. It will forward the request to you within 2 working days, unless the law requires otherwise.
9.4 Burst will give you the information you reasonably need for data protection impact assessments and prior consultation (Articles 35 and 36), including for the optional age and gender estimate in Annex 1. Burst provides notice text for that feature; the assessment of whether and how you use it is yours.
9.5 Burst will respond to your reasonable requests for help under this addendum within 2 working days, in Japanese or English. A request that needs more than that to complete (for example, a full deletion check) will get an answer within the 2 working days saying what is needed and when it will be done. Burst's working days are Japanese working days (see the support page for hours in Japan Standard Time and the UK and Central European equivalents).
10. Personal data breach
10.1 Burst will tell you without undue delay, and in any event within 48 hours, after it becomes aware of a personal data breach affecting your Shopper Data. The notice will say, as far as Burst then knows: what happened; the categories and approximate number of records and shoppers; the likely consequences; and what Burst has done and will do. Burst will send further information as it learns it, and will help you decide whether to notify a supervisory authority or shoppers.
10.2 Burst records breaches and keeps the record. Burst also tells Shopify where Shopify's partner requirements ask it to.
10.3 The notice goes to the contact address on your account. Keep it up to date.
11. Return and deletion
11.1 While you use the Services. The dashboard shows you reports built from Shopper Data but has no button to download the underlying records. You can ask Burst for them by email and Burst will send them to you as a file within 2 working days. Burst deletes Shopper Data when you instruct it to, and on a request for earlier deletion will do so where technically possible.
11.2 Routine deletion. Burst deletes answers and usage records automatically 400 days after they were recorded.
11.3 When you leave. After you uninstall the app, Shopify sends Burst a shop deletion notice. Burst then deletes all Shopper Data for your store at the end of the paid period, and in any case no later than 30 days after that notice. Quizzes, product catalogue data, sessions and the Shopify connection go with it.
11.4 What Burst keeps. Records of your account, your plan and billing, your company details, and your acceptance of the Terms are not Shopper Data. Burst keeps them as a controller for the time needed for its legal and accounting duties, and its privacy notice says how long. Shopify bills the plan charges and issues the invoice; Burst does not issue its own.
11.5 Backups. The database provider keeps daily backups for a limited time. Deleted data leaves those backups within 7 days of the deletion.
11.6 Burst will confirm the deletion in writing if you ask.
12. Information and audit
12.1 Burst will give you the information needed to show that it meets this addendum, for example by answering a reasonable security and data protection questionnaire once a year.
12.2 If that is not enough, or if a supervisory authority requires it, you may audit Burst's compliance, or appoint an independent auditor bound by confidentiality, once every 12 months on at least 30 days' notice, during business hours in Japan, remotely where it will do, and without access to other customers' data or to Burst's security details beyond what the audit needs. Each party bears its own costs, and you pay Burst's reasonable time beyond one working day.
13. Liability
13.1 Each party's liability under this addendum is subject to the limits in the Terms, to the extent the law allows. Nothing in this addendum limits a person's right to compensation from either party under Article 82 of the GDPR or the UK GDPR, or either party's liability to a supervisory authority.
14. Term, order of precedence, and law
14.1 This addendum starts when you install Rekotto and lasts as long as Burst processes Shopper Data for you. Clauses that by their nature continue (confidentiality, deletion, liability) continue.
14.2 If this addendum and the Terms conflict on the handling of Shopper Data, this addendum wins.
14.3 This addendum is governed by the law that governs the Terms, which is the law of Japan, and the courts that the Terms name have jurisdiction. This does not affect Data Protection Law, which applies as it is mandatory, nor any rights a person has under it.
14.4 Burst may update this addendum to follow a change in law, a change to Annex 3 under clause 7, or to improve it without reducing your protection. For a material change it will give you 30 days' notice by email.
Annex 1: The processing
1. Subject matter and purpose. Running the Rekotto product-recommendation quiz on your store: showing shoppers the quiz, scoring their answers into recommended products, showing you reports on how the quiz is used, supporting you, keeping the Services secure, and counting your plan's monthly quiz usage.
2. Duration. Until the deletion in clause 11.
3. Nature of processing. Collection through the quiz and Shopify, storage in a database, calculation (scoring, counts, and where switched on, the estimate in part 5), display to you in the dashboard, deletion.
4. People. Shoppers who take a Rekotto quiz on your store, and, through Shopify's order data, shoppers who then buy.
5. Categories of data.
| Data | What it is | Where it comes from | Notes |
|---|---|---|---|
| Session ID | A random identifier made for each quiz session | The quiz | Not a cookie; the quiz sets no cookies and no local storage. It is copied to the shopper's Shopify cart as the attribute dx_sid (path 1), and added to links from the result page to your product pages as the link parameter dx_sid (path 2). Both are done only where Shopify reports that analytics is allowed for that shopper (see part 7). |
| Answers | The choice a shopper picks for each question | The quiz | Choices only. The quiz has no text boxes and asks for no name or email. |
| Results | Which products were recommended and in what order, the top match percentage | The quiz | |
| Usage events | Quiz started, question viewed, quiz completed, result viewed, product clicked; time; whether the quiz was on a product page or the hosted page; device class (one of four values); campaign tags in the link (source, medium, campaign, cut to 100 characters); whether the shopper used the optional "weighting" control | The quiz | No IP address, no browser string, no email, no name. |
| Purchase link | The value, currency and time of an order, and which quiz session it came from | Shopify (order data and the optional Shopify Web Pixel) | The order number is kept only as a keyed, one-way code. Linking an order to a quiz session works only where the shopper's consent allows analytics: the session ID is written to the cart, and the pixel is sent, only after Shopify reports that consent. Without consent the purchase is not linked. |
| Technical logs | Request records at the hosting provider, including IP address and URL | The hosting provider | Kept up to 30 days, then erased. Used for security and fault finding. |
6. Optional feature: estimated age band and gender lean (the "estimate"). Burst calculates, from the pattern of answers, an estimated spread of age bands and gender leaning for groups of at least 20 sessions, to show you how your quiz audience skews. It is a statistical estimate for a group, not a fact about a person; it is never attached to one shopper's record, never stored per session (it is worked out when you open the screen), and never changes which products are recommended. For merchants in the UK and EEA it is off until you switch it on yourself in the app, on the "Your data" screen, where you can also switch it off again at any time. Burst also switches it on or off for you if you ask in writing (an email to info@burst-tech.com is enough). You decide what the estimate means: it works only from the age bands and gender lean that you set on each answer option in the quiz editor, and shows nothing until you set some (Burst's ready-made quizzes set none). Burst's calculation that adds those up is the same for every merchant. You also decide whether to use it. If you switch it on, your shopper-facing privacy notice should mention it; Burst provides suggested wording ("what to tell your shoppers about the quiz") in the app guide.
7. What the shopper-side consent controls. For every store, the session ID on the cart (path 1), the session ID on result links (path 2) and the Shopify Web Pixel depend on the consent signal Shopify provides through its Customer Privacy API. The storefront script asks that API before it writes anything. If the API cannot be reached, it writes nothing. Where the signal is "not allowed", result links still carry the campaign tags (utm_source, utm_medium, utm_campaign, utm_content: they name the quiz and the rank of the product, not the shopper), and no session ID. For a store in the UK or the EEA, a result page that is not told the shopper's choice also leaves the session ID off. Shopify reports consent according to your store's privacy and consent settings; you are responsible for your store's banner and those settings. When consent is not given, quiz answers, usage events and results are still recorded as part of running the quiz (they contain no identifier that is linked to the shopper outside the quiz), but purchases are not matched to the quiz, so your purchase figures will be lower.
Annex 2: Security measures in force
Measures Burst has in place today.
- Data minimisation by design. The shopper tables hold no IP address, no browser string, no email and no name; the order number is stored only as a keyed one-way code.
- No tracking by the quiz. The quiz sets no cookies, uses no local storage, and loads no third-party scripts or fonts.
- Encryption. Traffic is encrypted (HTTPS). Shopify access tokens are encrypted at rest (AES-256-GCM).
- Webhook authenticity. Notices from Shopify (including the mandatory privacy notices) are accepted only after their signature is verified.
- Dashboard. Sign-in uses secure, HttpOnly cookies limited to their path; requests that change data are protected against cross-site request forgery; a strict content security policy is applied.
- Access control. Access to the database and to the internal operator console is limited to Burst personnel who need it.
- Support access logged. When Burst staff open a store's data to give support, the visit is logged and the merchant is notified by email.
- Data stored in Tokyo. Database and application hosting are in the Tokyo region.
- Deletion. Routine and on-request deletion as in clause 11.
- Incident handling. Burst follows a written procedure for personal data breaches, which includes the notice times in clause 10.1.
Annex 3: Sub-processors
| Sub-processor | What it does | Shopper Data it handles | Location | Transfer mechanism |
|---|---|---|---|---|
| Supabase (Supabase Pte. Ltd., Singapore) | Database | All Shopper Data at rest | Tokyo, Japan (region ap-northeast-1). Supabase's own staff and support systems may reach it from outside Japan. | Supabase's data processing addendum (supabase.com/legal/customer-resources/data-processing-addendum), which incorporates the EU Standard Contractual Clauses (Module Two/Three) and the UK International Data Transfer Addendum. Sub-processor list: supabase.com/legal/customer-resources/subprocessor-list. |
| Vercel (Vercel Inc.) | Application hosting; runs the hosted quiz, the dashboard and the Shopify app | All Shopper Data in transit; request logs with IP address and URL, up to 30 days | Tokyo, Japan (region hnd1). Vercel's staff and systems may reach it from the United States. | Vercel's data processing addendum (vercel.com/legal/dpa), which incorporates the EU Standard Contractual Clauses and the UK Addendum; Vercel is also certified under the EU-US Data Privacy Framework. Sub-processor list: security.vercel.com. |
| Resend (Plus Five Five, Inc., trading as Resend) | Sends email | The records of a shopper's quiz session, only when Burst emails you the result of a shopper's data request (clause 9.2); also your own notices, which hold no Shopper Data | United States. Resend keeps its sending records for up to 30 days. | Resend's data processing addendum (resend.com/legal/dpa), which incorporates the EU Standard Contractual Clauses and the UK Addendum; Resend states that it complies with the EU-US Data Privacy Framework and its UK Extension. Sub-processor list: resend.com/legal/subprocessors. |
Not sub-processors. Shopify supplies order and store data and receives the app's requests; it acts for itself under its own terms and privacy notice, and is not Burst's sub-processor. Your Shopify store, theme and consent settings are yours.
Notice of changes: see clause 7.2.