Manage your projects and their members
A project is a group of token collections, user wallets, API keys, billing information, and more.
If you are working with different teams or clients, you can create different projects to seggregate sensitive information and tool access. Alternatively, you can issue different API keys within the same project, but bear in mind they will share the same billing account.
Every developer account automatically includes a project named Default Project
. You can create new projects and alternate between them using the selector within the console, as illustrated in the screenshot below.
Projects have an option to register a link to your company’s privacy policy. If set, this link will be shown to your users when they’re using any Crossmint-managed user interface, such as the Checkout, where user information is collected. A privacy policy is required by law if you want to later those users’ personally identifiable information, such as their email address.
If you don’t already have a privacy policy, you can generate and host one using tools like Termly.
Note: Failure to add a privacy policy will result in email addresses being hidden.
Use Case | Privacy Policy Required |
---|---|
Payments (payment button) | Yes |
Payments (embedded checkout) | Yes |
Payments (headless checkout) | No |
Mint API or console | No |
Wallet APIs or console | No |
*Go to the General Settings tab
Include the Privacy Policy Link
Following these steps will ensure compliance with data protection laws and enable the visibility of email addresses in your project settings.
Why does Crossmint require my project's privacy policy?
Crossmint requires your project’s privacy policy to comply with data protection laws and ensure the privacy and security of user data. Without it, email addresses and other sensitive information will be hidden.
I have already configured the privacy policy URL, why can't I see the user identifier of some users?
Older users who joined before the privacy policy was added haven’t accepted the new policy. Therefore, their identifiers remain hidden.
Why can't I delete the privacy policy of my project?
Deleting the privacy policy is restricted to ensure compliance with data protection laws and maintain user privacy and security.
A project is a group of token collections, user wallets, API keys, billing information, and more.
If you are working with different teams or clients, you can create different projects to seggregate sensitive information and tool access. Alternatively, you can issue different API keys within the same project, but bear in mind they will share the same billing account.
Every developer account automatically includes a project named Default Project
. You can create new projects and alternate between them using the selector within the console, as illustrated in the screenshot below.
Projects have an option to register a link to your company’s privacy policy. If set, this link will be shown to your users when they’re using any Crossmint-managed user interface, such as the Checkout, where user information is collected. A privacy policy is required by law if you want to later those users’ personally identifiable information, such as their email address.
If you don’t already have a privacy policy, you can generate and host one using tools like Termly.
Note: Failure to add a privacy policy will result in email addresses being hidden.
Use Case | Privacy Policy Required |
---|---|
Payments (payment button) | Yes |
Payments (embedded checkout) | Yes |
Payments (headless checkout) | No |
Mint API or console | No |
Wallet APIs or console | No |
*Go to the General Settings tab
Include the Privacy Policy Link
Following these steps will ensure compliance with data protection laws and enable the visibility of email addresses in your project settings.
Why does Crossmint require my project's privacy policy?
Crossmint requires your project’s privacy policy to comply with data protection laws and ensure the privacy and security of user data. Without it, email addresses and other sensitive information will be hidden.
I have already configured the privacy policy URL, why can't I see the user identifier of some users?
Older users who joined before the privacy policy was added haven’t accepted the new policy. Therefore, their identifiers remain hidden.
Why can't I delete the privacy policy of my project?
Deleting the privacy policy is restricted to ensure compliance with data protection laws and maintain user privacy and security.
Projects can be shared across multiple team members. You can add new members from the Members tab on the console. All members get the same permissions, except for the ability to delete other members, which only belongs to the creator of the project.
Manage your projects and their members
A project is a group of token collections, user wallets, API keys, billing information, and more.
If you are working with different teams or clients, you can create different projects to seggregate sensitive information and tool access. Alternatively, you can issue different API keys within the same project, but bear in mind they will share the same billing account.
Every developer account automatically includes a project named Default Project
. You can create new projects and alternate between them using the selector within the console, as illustrated in the screenshot below.
Projects have an option to register a link to your company’s privacy policy. If set, this link will be shown to your users when they’re using any Crossmint-managed user interface, such as the Checkout, where user information is collected. A privacy policy is required by law if you want to later those users’ personally identifiable information, such as their email address.
If you don’t already have a privacy policy, you can generate and host one using tools like Termly.
Note: Failure to add a privacy policy will result in email addresses being hidden.
Use Case | Privacy Policy Required |
---|---|
Payments (payment button) | Yes |
Payments (embedded checkout) | Yes |
Payments (headless checkout) | No |
Mint API or console | No |
Wallet APIs or console | No |
*Go to the General Settings tab
Include the Privacy Policy Link
Following these steps will ensure compliance with data protection laws and enable the visibility of email addresses in your project settings.
Why does Crossmint require my project's privacy policy?
Crossmint requires your project’s privacy policy to comply with data protection laws and ensure the privacy and security of user data. Without it, email addresses and other sensitive information will be hidden.
I have already configured the privacy policy URL, why can't I see the user identifier of some users?
Older users who joined before the privacy policy was added haven’t accepted the new policy. Therefore, their identifiers remain hidden.
Why can't I delete the privacy policy of my project?
Deleting the privacy policy is restricted to ensure compliance with data protection laws and maintain user privacy and security.
A project is a group of token collections, user wallets, API keys, billing information, and more.
If you are working with different teams or clients, you can create different projects to seggregate sensitive information and tool access. Alternatively, you can issue different API keys within the same project, but bear in mind they will share the same billing account.
Every developer account automatically includes a project named Default Project
. You can create new projects and alternate between them using the selector within the console, as illustrated in the screenshot below.
Projects have an option to register a link to your company’s privacy policy. If set, this link will be shown to your users when they’re using any Crossmint-managed user interface, such as the Checkout, where user information is collected. A privacy policy is required by law if you want to later those users’ personally identifiable information, such as their email address.
If you don’t already have a privacy policy, you can generate and host one using tools like Termly.
Note: Failure to add a privacy policy will result in email addresses being hidden.
Use Case | Privacy Policy Required |
---|---|
Payments (payment button) | Yes |
Payments (embedded checkout) | Yes |
Payments (headless checkout) | No |
Mint API or console | No |
Wallet APIs or console | No |
*Go to the General Settings tab
Include the Privacy Policy Link
Following these steps will ensure compliance with data protection laws and enable the visibility of email addresses in your project settings.
Why does Crossmint require my project's privacy policy?
Crossmint requires your project’s privacy policy to comply with data protection laws and ensure the privacy and security of user data. Without it, email addresses and other sensitive information will be hidden.
I have already configured the privacy policy URL, why can't I see the user identifier of some users?
Older users who joined before the privacy policy was added haven’t accepted the new policy. Therefore, their identifiers remain hidden.
Why can't I delete the privacy policy of my project?
Deleting the privacy policy is restricted to ensure compliance with data protection laws and maintain user privacy and security.
Projects can be shared across multiple team members. You can add new members from the Members tab on the console. All members get the same permissions, except for the ability to delete other members, which only belongs to the creator of the project.