Privacy Policy

Effective date: 07-07-2023

Privacy Policy

Effective date: 07-07-2023

Privacy Policy

Effective date: 07-07-2023

Welcome to tokens studio.

tokens studio ("us", "we", or "our") operates https://tokens.studio/ (hereinafter referred to as "Service").

Our Privacy Policy governs your use of our Tokens Studio plugin and web pages located at https://tokens.studio/ operated by Hyma B.V., and explains how we collect, safeguard and disclose information that results from your use of our Service.

We use your data to provide and improve Service. By using Service, you agree to the collection and use of information in accordance with this policy. Unless otherwise defined in this Privacy Policy, the terms used in this Privacy Policy have the same meanings as in our Terms and Conditions.

Our Terms and Conditions ("Terms") govern all use of our Service and together with the Privacy Policy constitutes your agreement with us ("Agreement").

Definitions

SERVICE means the Tokens Studio for Figma and the https://tokens.studio/ website operated by Tokens Studio.

PERSONAL DATA means data about a living individual who can be identified from those data (or from those and other information either in our possession or likely to come into our possession).

USAGE DATA is data collected automatically either generated by the use of Service or from Service infrastructure itself (for example, the duration of a page visit).

COOKIES are small files stored on your device (computer or mobile device).

DATA CONTROLLER means a natural or legal person who (either alone or jointly or in common with other persons) determines the purposes for which and the manner in which any personal data are, or are to be, processed. For the purpose of this Privacy Policy, we are a Data Controller of your data.

DATA PROCESSORS (OR SERVICE PROVIDERS) means any natural or legal person who processes the data on behalf of the Data Controller. We may use the services of various Service Providers in order to process your data more effectively.

DATA SUBJECT is any living individual who is the subject of Personal Data.

THE USER is the individual using our Service. The User corresponds to the Data Subject, who is the subject of Personal Data.

Information Collection and Use

We collect several different types of information for various purposes to provide and improve our Service to you.

Types of Data Collected

Personal Data
While using our Service, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you ("Personal Data"). Personally identifiable information may include, but is not limited to:

1. Email address

2. First name and last name

3. Cookies and Usage Data

We may use your Personal Data to contact you with newsletters, marketing or promotional materials and other information that may be of interest to you. You may opt out of receiving any, or all, of these communications from us by following the unsubscribe link.

Usage Data

We may also collect information that your browser sends whenever you visit our Service or when you access Service by or through a mobile device ("Usage Data").

This Usage Data may include information such as your computer's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that you visit, the time and date of your visit, the time spent on those pages, unique device identifiers and other diagnostic data.

When you access Service with a mobile device, this Usage Data may include information such as the type of mobile device you use, your mobile device unique ID, the IP address of your mobile device, your mobile operating system, the type of mobile Internet browser you use, unique device identifiers and other diagnostic data.

Tracking Cookies Data

We use cookies and similar tracking technologies to track the activity on our Service and we hold certain information.

Cookies are files with a small amount of data which may include an anonymous unique identifier. Cookies are sent to your browser from a website and stored on your device. Other tracking technologies are also used such as beacons, tags and scripts to collect and track information and to improve and analyze our Service.

You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use some portions of our Service.

Examples of Cookies we use:

1. Session Cookies: We use Session Cookies to operate our Service.

2. Preference Cookies: We use Preference Cookies to remember your preferences and various settings.

3. Security Cookies: We use Security Cookies for security purposes.

Data storage

Places where we store data:

Plugin

Tokens are stored on the Figma document itself. The Tokens Studio for Figma plugin stores all data entered and used by the plugin on the user’s Figma client storage. This includes your plugin preferences (plugin window size and any settings set inside of the plugin), but also sync credentials such as:

- Personal Access Tokens used for GitHub, GitLab and ADO. We’re using the following packages to communicate with these platforms: @octokit/rest for GitHub, @gitbeaker/browser for GitLab, @azure-devops-node-api for ADO.

At the discretion of the user, tokens can be synchronised through any of the available sync providers including JSONBin, GitHub, GitLab, Azure DevOps. The synchronisation happens directly between the plugin and the sync destination and does not flow through any of our infrastructure.

The Tokens Studio plugin (as any other plugin) has full access to all the data on the canvas. The Tokens Studio for Figma plugin interacts with data on the canvas through the Figma API to read/write tokens via shared plugin data or to modify the appearance of elements on the canvas but none of this data ever leaves the Figma environment.

Stripe

Stripe is our payment service provider and the data entered during the checkout process is stored on the Stripe platform. We do not store any payment or credit card data on our infrastructure. The following data is stored on the Stripe platform:

- Customer Name
- Customer Email
- Billing Email
- Billing address
- VAT number (for EU customers)
- Payment details such as credit card information
- Company name

For more information about stripe:

Website: Stripe.com
Privacy policy: https://stripe.com/in/privacy

KeyGen

For pro users only:

Keygen is a licence management platform that is used by the plugin to validate a licence key entered in the plugin. It also validates that the licence key belongs to the current Figma user who is using the plugin. To achieve this the following data is stored on the KeyGen platform:

- Figma User ID
- E-mail address used for subscription via Stripe

For more information about Keygen:

Website: Keygen.sh
Privacy policy: https://keygen.sh/privacy/

LaunchDarkly

LaunchDarkly is a feature flag management platform that is used by the plugin to enable or disable features based on the user’s subscription. To achieve this the following data is stored on the LaunchDarkly platform:

- Figma User ID

For more information about LaunchDarkly:

Website: LaunchDarkly.com
Data, privacy and security: https://launchdarkly.com/security/

Mixpanel

Mixpanel is an analytics platform that is used to track the usage of the plugin and its features. To achieve this the following data is stored on the Mixpanel platform on servers in the European Union:

- Figma User ID
- Figma User Name

Sentry
Session recording is a feature to track user sessions when bugs occur, so we can better understand the issue and fix it. No data will be sent to our telemetry server if you do not experience a bug or if you turn off the debugging.
Any data collected is anonymized and will not be shared with any third parties and is used purely to address bugs and optimize performance.
Disclaimer: The initial session, when opting in for the first time, will be recorded.
For more information about Sentry:

Places where we store data:

Plugin

Tokens are stored on the Figma document itself. The Tokens Studio for Figma plugin stores all data entered and used by the plugin on the user’s Figma client storage. This includes your plugin preferences (plugin window size and any settings set inside of the plugin), but also sync credentials such as:

- Personal Access Tokens used for GitHub, GitLab and ADO. We’re using the following packages to communicate with these platforms: @octokit/rest for GitHub, @gitbeaker/browser for GitLab, @azure-devops-node-api for ADO.

At the discretion of the user, tokens can be synchronised through any of the available sync providers including JSONBin, GitHub, GitLab, Azure DevOps. The synchronisation happens directly between the plugin and the sync destination and does not flow through any of our infrastructure.

The Tokens Studio plugin (as any other plugin) has full access to all the data on the canvas. The Tokens Studio for Figma plugin interacts with data on the canvas through the Figma API to read/write tokens via shared plugin data or to modify the appearance of elements on the canvas but none of this data ever leaves the Figma environment.

Stripe

Stripe is our payment service provider and the data entered during the checkout process is stored on the Stripe platform. We do not store any payment or credit card data on our infrastructure. The following data is stored on the Stripe platform:

- Customer Name
- Customer Email
- Billing Email
- Billing address
- VAT number (for EU customers)
- Payment details such as credit card information
- Company name

For more information about stripe:

Website: Stripe.com
Privacy policy: https://stripe.com/in/privacy

KeyGen

For pro users only:

Keygen is a licence management platform that is used by the plugin to validate a licence key entered in the plugin. It also validates that the licence key belongs to the current Figma user who is using the plugin. To achieve this the following data is stored on the KeyGen platform:

- Figma User ID
- E-mail address used for subscription via Stripe

For more information about Keygen:

Website: Keygen.sh
Privacy policy: https://keygen.sh/privacy/

LaunchDarkly

LaunchDarkly is a feature flag management platform that is used by the plugin to enable or disable features based on the user’s subscription. To achieve this the following data is stored on the LaunchDarkly platform:

- Figma User ID

For more information about LaunchDarkly:

Website: LaunchDarkly.com
Data, privacy and security: https://launchdarkly.com/security/

Mixpanel

Mixpanel is an analytics platform that is used to track the usage of the plugin and its features. To achieve this the following data is stored on the Mixpanel platform on servers in the European Union:

- Figma User ID
- Figma User Name

Sentry
Session recording is a feature to track user sessions when bugs occur, so we can better understand the issue and fix it. No data will be sent to our telemetry server if you do not experience a bug or if you turn off the debugging.
Any data collected is anonymized and will not be shared with any third parties and is used purely to address bugs and optimize performance.
Disclaimer: The initial session, when opting in for the first time, will be recorded.
For more information about Sentry:

Places where we store data:

Plugin

Tokens are stored on the Figma document itself. The Tokens Studio for Figma plugin stores all data entered and used by the plugin on the user’s Figma client storage. This includes your plugin preferences (plugin window size and any settings set inside of the plugin), but also sync credentials such as:

- Personal Access Tokens used for GitHub, GitLab and ADO. We’re using the following packages to communicate with these platforms: @octokit/rest for GitHub, @gitbeaker/browser for GitLab, @azure-devops-node-api for ADO.

At the discretion of the user, tokens can be synchronised through any of the available sync providers including JSONBin, GitHub, GitLab, Azure DevOps. The synchronisation happens directly between the plugin and the sync destination and does not flow through any of our infrastructure.

The Tokens Studio plugin (as any other plugin) has full access to all the data on the canvas. The Tokens Studio for Figma plugin interacts with data on the canvas through the Figma API to read/write tokens via shared plugin data or to modify the appearance of elements on the canvas but none of this data ever leaves the Figma environment.

Stripe

Stripe is our payment service provider and the data entered during the checkout process is stored on the Stripe platform. We do not store any payment or credit card data on our infrastructure. The following data is stored on the Stripe platform:

- Customer Name
- Customer Email
- Billing Email
- Billing address
- VAT number (for EU customers)
- Payment details such as credit card information
- Company name

For more information about stripe:

Website: Stripe.com
Privacy policy: https://stripe.com/in/privacy

KeyGen

For pro users only:

Keygen is a licence management platform that is used by the plugin to validate a licence key entered in the plugin. It also validates that the licence key belongs to the current Figma user who is using the plugin. To achieve this the following data is stored on the KeyGen platform:

- Figma User ID
- E-mail address used for subscription via Stripe

For more information about Keygen:

Website: Keygen.sh
Privacy policy: https://keygen.sh/privacy/

LaunchDarkly

LaunchDarkly is a feature flag management platform that is used by the plugin to enable or disable features based on the user’s subscription. To achieve this the following data is stored on the LaunchDarkly platform:

- Figma User ID

For more information about LaunchDarkly:

Website: LaunchDarkly.com
Data, privacy and security: https://launchdarkly.com/security/

Mixpanel

Mixpanel is an analytics platform that is used to track the usage of the plugin and its features. To achieve this the following data is stored on the Mixpanel platform on servers in the European Union:

- Figma User ID
- Figma User Name

Sentry
Session recording is a feature to track user sessions when bugs occur, so we can better understand the issue and fix it. No data will be sent to our telemetry server if you do not experience a bug or if you turn off the debugging.
Any data collected is anonymized and will not be shared with any third parties and is used purely to address bugs and optimize performance.
Disclaimer: The initial session, when opting in for the first time, will be recorded.
For more information about Sentry:

Use of Data

Tokens Studio uses the collected data for various purposes:

1. to provide and maintain our Service;

2. to notify you about changes to our Service;

3. to allow you to participate in interactive features of our Service when you choose to do so;

4. to provide customer support;

5. to gather analysis or valuable information so that we can improve our Service;

6. to monitor the usage of our Service;

7. to detect, prevent and address technical issues;

8. to fulfill any other purpose for which you provide it;

9. to carry out our obligations and enforce our rights arising from any contracts entered into between you and us, including for billing and collection;

10. to provide you with notices about your account and/or subscription, including expiration and renewal notices, email-instructions, etc.;

11. to provide you with news, special offers and general information about other goods, services and events which we offer that are similar to those that you have already purchased or enquired about unless you have opted not to receive such information;

12. in any other way we may describe when you provide the information;

13. for any other purpose with your consent.

Retention of Data

We will retain your Personal Data only for as long as is necessary for the purposes set out in this Privacy Policy. We will retain and use your Personal Data to the extent necessary to comply with our legal obligations (for example, if we are required to retain your data to comply with applicable laws), resolve disputes, and enforce our legal agreements and policies.

We will also retain Usage Data for internal analysis purposes. Usage Data is generally retained for a shorter period, except when this data is used to strengthen the security or to improve the functionality of our Service, or we are legally obligated to retain this data for longer time periods.

Transfer of Data

Your information, including Personal Data, may be transferred to – and maintained on – computers located outside of your state, province, country or other governmental jurisdiction where the data protection laws may differ from those of your jurisdiction.

If you are located outside the European Union and choose to provide information to us, please note that we transfer the data, including Personal Data, to the European Union and process it there.

Your consent to this Privacy Policy followed by your submission of such information represents your agreement to that transfer.

Tokens Studio will take all the steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy and no transfer of your Personal Data will take place to an organisation or a country unless there are adequate controls in place including the security of your data and other personal information.

Disclosure of Data

We may disclose personal information that we collect, or you provide:

Business Transaction

If we or our subsidiaries are involved in a merger, acquisition or asset sale, your Personal Data may be transferred.

Security of Data

The security of your data is important to us but remember that no method of transmission over the Internet or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.

Service Providers

We may employ third party companies and individuals to facilitate our Service ("Service Providers"), provide Service on our behalf, perform Service-related services or assist us in analysing how our Service is used.

These third parties have access to your Personal Data only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose.

Analytics

We may use third-party Service Providers to monitor and analyze the use of our Service.

Payments

We may provide paid products and/or services within Service. In that case, we use third-party services for payment processing (e.g. payment processors).

We will not store or collect your payment card details. That information is provided directly to our third-party payment processors whose use of your personal information is governed by their Privacy Policy. These payment processors adhere to the standards set by PCI-DSS as managed by the PCI Security Standards Council, which is a joint effort of brands like Visa, Mastercard, American Express and Discover. PCI-DSS requirements help ensure the secure handling of payment information.

The payment processor we work with is:

Stripe: Their Privacy Policy can be viewed at: https://stripe.com/privacy

Children's Privacy

Our Services are not intended for use by children under the age of 13 ("Children").

We do not knowingly collect personally identifiable information from Children under 13. If you become aware that a Child has provided us with Personal Data, please contact us. If we become aware that we have collected Personal Data from Children without verification of parental consent, we take steps to remove that information from our servers.

Changes to this Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.

We will let you know via email and/or a prominent notice on our Service, prior to the change becoming effective and update "effective date" at the top of this Privacy Policy.

You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.

Contact Us

If you have any questions about this Privacy Policy, please let us know by emailing at support@tokens.studio so we can try to find a solution.