Last updated: 5 October 2026
This policy explains what personal data StartBuildLaunch collects, why, and what you can do about it. StartBuildLaunch is run by Avis J. Williams in London, United Kingdom, who is the data controller for the personal data described here under the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.
1. Personal data we collect
| When | What we collect |
|---|---|
| You sign up for free resources, emails or offers | Name and email address |
| You buy a product or service | Name, billing address, email address, order details and anything you write in the order form. Card and payment details are handled by our payment providers (Stripe or PayPal), not by us. |
| You contact us or enquire about a project | Name, email address, phone number (if given), organisation and the details you send us |
| You browse the site | Device, browser and usage information collected through cookies, where you allow them. See our Cookie Policy. |
2. How we use it
- To deliver what you have bought and provide support (to perform our contract with you).
- To reply to your questions and enquiries (our legitimate interests, or steps before a contract).
- To send you emails you have signed up for (your consent; you can unsubscribe at any time).
- To understand how the site is used and improve it, and to measure our advertising (your consent, through the cookie banner).
- To keep records we are required to keep, such as tax records (legal obligation).
3. Who we share it with
We do not sell your personal data. We share it only with providers who help us run the business, under agreements that protect it:
- Payment providers: Stripe and PayPal.
- Website hosting: Hostinger. Our email list is managed on our own website.
- Analytics and advertising, only if you accept these cookies: Google Analytics, Microsoft Clarity and Microsoft Advertising, and Meta (Facebook and Instagram).
- Professional advisers or authorities, where the law requires it.
Some of these providers are based outside the UK. Where data is transferred abroad, it is protected by the safeguards UK law requires, such as UK adequacy regulations or approved contract clauses.
4. Data from client projects
When we build something for an organisation, that organisation decides how its data is used, and we handle it only on its instructions. We use synthetic or test data until a data processing agreement is in place, and we only access real data where that is necessary for the work.
5. Security and how long we keep data
We use technical and organisational measures to protect your data against loss and unauthorised access. We keep it only for as long as we need it for the purposes above, or as the law requires (for example, financial records are kept for 6 years). After that we delete or anonymise it.
6. Children
Our website and services are for adults. We do not knowingly collect personal data from anyone under 18.
7. Your rights
You can ask us to:
- give you a copy of the personal data we hold about you;
- correct or delete it;
- restrict or object to how we use it, or send it to another organisation;
- stop using it for marketing, or withdraw any consent you have given.
Email avis@startbuildlaunch.com and we will respond within one month. If you are unhappy with how we handle your data, you can complain to the Information Commissioner’s Office at ico.org.uk.
8. Changes to this policy
We only use your data for the purpose we collected it for, unless a new purpose is compatible with it. If we change this policy in a significant way, we will update the date at the top and, where appropriate, let you know.
9. Browser Extensions
Pixel To Token – Design Token Extractor Browser Extension
Effective date: May 15, 2026
PixelToToken is a Chrome extension that helps users extract design tokens from websites, app interfaces, mockups, screenshots, and uploaded images. This policy explains what information the extension accesses, how it is used, and how it is handled.
Summary
PixelToToken processes data locally in your browser. The extension does not sell, share, transmit, or upload your extracted tokens, screenshots, page data, uploaded images, or browsing activity to external servers.
Information Pixel To Token Accesses
When you choose to use PixelToToken on the active browser tab, the extension may access:
- Visible CSS styles from the active page, such as colors, fonts, spacing, border radii, and shadows.
- A screenshot of the visible area of the active tab, used to identify colors.
- Basic page metadata, such as page title, URL, and hostname, used in exports and reports.
- User-selected page elements when using the droplet picker.
- Images or JSON files that you choose to upload or import into the extension.
PixelToToken only accesses the active tab when you invoke the extension or start a picker action. It does not run continuously in the background to monitor your browsing.
How Information Is Used
The information accessed by PixelToToken is used only to provide the extension’s design-token extraction features, including:
- Detecting color tokens.
- Detecting typography, spacing, border radius, and shadow values.
- Building local exports such as Figma JSON, Tailwind config, CSS variables, Markdown, and Brand PDF reports.
- Temporarily storing droplet picker selections so they can be transferred back to the extension popup.
- Remembering that you have accepted the one-time privacy notice.
Local Storage
PixelToToken uses Chrome local storage for limited local-only purposes:
- To remember that you have seen and accepted the one-time notice.
- To temporarily store recent droplet picker selections until they are loaded into the popup.
- To temporarily store a locally generated Brand PDF report so it can open in a separate extension tab for printing or saving.
This storage remains on your device. PixelToToken does not sync this data to the developer or to third-party services.
Data Sharing
Pixel To Token does not sell, rent, share, or transfer user data to third parties. The extension does not use analytics, advertising trackers, remote logging, or behavioral profiling.
Remote Requests
PixelToToken does not send extracted tokens, screenshots, uploaded files, page contents, URLs, or browsing activity to external servers.
The extension may open links that you explicitly click, such as the Privacy Policy link or developer links shown in the extension interface. Those websites are separate from the extension and may have their own privacy practices.
Permissions
PixelToToken requests the following Chrome extension permissions:
PixelToToken does not request broad host permissions, cookie access, web request interception, browsing history access, or permission to read all websites continuously.
| Permission | Reason |
| activeTab | Allows PixelToToken to inspect the current tab only after you invoke the extension. |
| scripting | Allows PixelToToken to run its local extraction script on the active tab after user action. |
| storage | Allows PixelToToken to store the one-time notice status and temporary droplet picker selections locally. |
PixelToToken does not request broad host permissions, cookie access, web request interception, browsing history access, or permission to read all websites continuously.
Uploaded Files
If you upload an image or import a JSON token file, the file is processed locally in your browser. PixelToToken does not upload these files to the developer or to third-party services.
Security
Pixel To Token is designed to minimize data access and keep processing local. No method of software operation is completely risk-free, but the extension is built to request only the permissions needed for its stated functionality.
Chrome Web Store User Data Policy
The use of information received from Chrome APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Children’s Privacy
PixelToToken is not directed to children under 13 and does not knowingly collect personal information from children.
10. Contact us
For any questions about this policy or your data, email avis@startbuildlaunch.com or use our contact page.