This policy describes the data used to provide the service: account access, uploaded creative material, payment events, generation requests, API usage, and support records.
Михаил Дроздов, an individual based in the United States, operates Formatry and is responsible for the account and service data described here. Contact support@formatry.cc for privacy matters. We receive the information you provide: account and contact details, uploaded files, prompts and generation settings, support messages and connected-service permissions. We also receive login and recovery records, IP and browser information, request and delivery records, API usage and payment confirmations. To enforce the free raster-file allowance across accounts, we use an account reference, a first-party browser marker and the IP address received from a trusted network source. Allowance records use keyed hashes of these signals. A browser marker or IP address can be shared or change; neither identifies physical hardware reliably. Anonymous integration trials separately use hashed client and network markers to enforce temporary quotas and prevent abuse. If you sign in through another provider, we receive the verified identity information that provider supplies for the permissions requested.
Why we process data
We use account details, content and request records to provide the service you request and administer your contract, including the shared free raster-file allowance. We use limited security and operational records to protect accounts, prevent abuse and investigate faults, based on our legitimate interests and any applicable legal duties. We keep required payment and accounting records to meet legal obligations. Optional analytics uses your consent. You can refuse or withdraw optional consent without losing access to the service; data necessary for an account, a purchase or a requested feature is still needed to provide it.
Cookies and optional analytics
Essential cookies keep account sessions, security checks and your requested settings working. The first-party cookie formatry_free_export_device holds a signed random browser marker for up to one year to apply the shared free raster-file allowance; it is not an analytics identifier. The cookie formatry_cc_analytics_consent remembers your analytics choice for up to 180 days. Only after you accept, formatry_cc_anon_analytics stores a random analytics identifier for up to 30 days; PostHog uses it to measure visits and product actions, including links between a visit, registration and a purchase. The PostHog browser SDK uses memory rather than its own persistent cookies or local storage. Use to reject or withdraw at any time. Withdrawal removes this browser's optional identifier and stops future optional tracking and queued attribution; it does not automatically erase information already sent before withdrawal. You may separately request erasure. Blocking necessary storage can prevent login or other requested features from working.
Payments
The provider named at checkout processes your payment details. Supported payment routes include Stripe, Lava, YooKassa, Coinbase and Telegram Stars where offered. Formatry receives transaction identifiers, payment status, amounts, currency and account or billing references needed to fulfil the purchase, handle refunds and maintain records. Full card numbers and card security codes are entered with the payment provider, not stored by Formatry. Payment providers also process information for their own fraud-prevention and legal obligations under their notices.
Service providers and connected services
Hosting, database, file-storage, network-security and email providers process the data needed to operate Formatry; transactional email is sent through Resend. When you request an AI image feature, its inputs and relevant images are sent to the AI provider used for that feature, such as OpenAI or Google. When enabled, Google AI assists with support replies using the message and relevant help material. Connected login, cloud-delivery and editor services receive the information needed for the connection or delivery you request. Do not include sensitive personal information in prompts or support messages unless it is necessary for your request.
International processing
Formatry is operated from the United States. Service providers may process information in the United States and other countries, so your data is not promised to remain in the EEA or the UK. Contact support@formatry.cc for information about the recipients and transfer arrangements relevant to your data. A provider's location or your acceptance of the service terms is not, by itself, consent to an international transfer.
Figma plugin data
The Formatry Figma plugin sends only the PNG export of the single supported node you explicitly select, a hashed opaque selection reference, and the generation or delivery state needed to complete your request. It does not read unselected nodes, full document JSON, comments, version history, or your Figma account email. You explicitly connect a Formatry account in the browser; the plugin then stores only a short-lived, revocable editor session. Selection bytes become an account-owned Formatry asset; editor pairing, session, provenance, and delivery records are retained for up to 90 days, while generated-file retention and deletion follow the published Formatry account and storage controls.
Uploaded assets and generated files
Uploaded assets are used for your requested work and remain in your account until you delete them or account deletion is completed. Generated download files normally expire after 7 days; the service can set a period between 1 and 30 days. Check the expiry shown for the file and keep your own copy. Expired files are hidden and queued for storage cleanup; expiry is not a promise that every copy has already been erased.
API keys and security
API key secrets should be stored by the customer. Formatry verifies API access without showing key secrets again after creation.
Service records
Service records may include request status, delivery state, payment state, and error codes so failed uploads, payments, and generations can be reviewed. Records without a fixed product retention window are kept only while needed to operate the account, investigate a request, secure the service, meet payment-provider or audit requirements, or comply with applicable law.
Deletion and support
You can delete assets and revoke API keys through the account controls. Account deletion revokes access and starts a separate deletion process; submission does not mean all stored data has already been erased. Some payment, security and dispute records may need to be retained for a legal obligation or to establish or defend a claim. We restrict retained information to that purpose. Contact support@formatry.cc if you cannot access the account or need information about retained records.
Your privacy rights
Depending on the law that applies to you, you may request access to or a copy of your personal data, correction, erasure, restriction, portability or an objection to processing. You may withdraw consent and complain to your local data-protection authority. Send a request to support@formatry.cc or through Support, identifying the account and the right you wish to exercise. We may need proportionate verification before disclosing or changing data; do not send passwords, recovery keys or full card details. We respond within the applicable legal deadline, normally one month for EEA/UK requests, and explain any permitted extension or refusal. Where US state law provides an appeal, reply asking for a privacy appeal. Exercising a right does not itself justify discriminatory treatment.
Children and updates
Formatry is intended for people able to contract for a creative-production service and is not directed to children under 13. If you believe a child has supplied personal information, contact support so we can investigate. The revision date identifies this notice. We will explain material changes and obtain fresh consent where required; a change to this notice does not automatically expand an earlier optional consent.
Need help with account data?
Contact support with the account, payment, asset, or API access context needed to locate the record. Never send the key value.