Frequently asked questions
A regularly curated list of the most commonly asked questions by Quaaant users.
We use Stripe to process your payment. It’s the same provider used by Slack, Notion and Figma. We do not handle your credit card information directly or store it on our servers.
A seat is a paid spot that allows a designer or team member to publish designs, collaborate on designs, and exchange assets. It is required for any individual designer to access these features, as well as for any team member. The project owner also takes a seat.
While it is possible for someone to view a design project through a shared private link, this does not require the use of a seat. Instead, a seat is only necessary for those who need to actively participate in and contribute to the project.
You can change your payment method at any time by visiting the “Subscription” settings page on our web platform.
If a payment fails, it may be retried up to five times within the following three to five days. Your account email address will be notified after each failed payment. After this, if the payment did not succeed, your payment plan will be put “on-hold” until you manually renew subscription.
When you switch payment plans, we’ll activate the new plan immediately, and your credit card will be charged with a prorated amount. In case of upgrade, we’ll charge you the difference immediately. In case of downgrade, your first payment will be delayed based on the number of days you are in pre-paid.
Yes! We offer both monthly and yearly billing options. The yearly billing option is always cheaper.
Yes, we do. Please contact support for more details.
A branch is like your own personal copy of a project’s main branch. It’s where you can safely make changes to a project’s designs without affecting the original source of truth. Working on a branch allows you to experiment and edit without worrying about messing up the original design. When you’re happy with your changes, you can merge them into the main branch. This way, you can improve a project without worrying about overwriting any important work.
Merging lets you and your teammates collaborate in exciting new ways. For example, you could create a branch to revise a type hierarchy while your teammate branches off to work on the project’s color palette. Once they finish their work and merge their changes into your branch, you will then have file which contain both, your type choices and their colors.
Before merging, most teams should have their work reviewed by one or more people. Each team has its own process for approving work—for example, the team may require one-on-one communication between a designer and the reviewer, or they may conduct larger reviews of multiple designs with other team members.
Quaaant takes the security and data protection of client projects very seriously. To ensure that sensitive client data is kept confidential, Quaaant includes features such as secure login and access controls, encryption of data in transit and at rest, and regular security audits and assessments. In addition, Quaaant has a clearly defined data retention and destruction policy to ensure that client data is only retained for as long as necessary and is properly disposed of when no longer needed. These measures help to ensure that Quaaant is a secure and reliable platform for managing sensitive design projects.
Yes. Qaaant uses Stripe for storing payment details and payment processing. You can find more information about Stripe’s security and PCI Compliance here.
A design asset is a visual or graphical element that can be used in the creation of digital or print materials, such as logos, icons, images, and patterns. These assets are often created by designers and are intended to be reusable across multiple projects and platforms.
A design token is a specific design element or piece of information, such as a color value or a typographic scale, that can be reused across a design system. A design asset, on the other hand, is a tangible, visual design element that can be used as part of a user interface, such as a button, icon or illustration.
Design tokens are often used to establish a consistent visual language across a website or application. Design assets, on the other hand, are typically used as building blocks to create the visual elements of the interface.
