What you are agreeing to

Legal

No cross-references to a page you cannot open, and no clause that contradicts what the store actually does. Where a sentence below is decided by software, the same software renders it here.

Frontary sells access to digital frontend work. Two things exist for sale: a plan, which grants access for a fixed period, and a bundle, which is a one-time purchase of a fixed set of products. Nothing else is sold, and no purchase transfers ownership of the underlying copyright.

What a plan grants

A plan grants access to the products inside its scope for its duration, in the deliverables its rules allow. During that period you may build any number of projects with what you take, for yourself or for clients. When the period ends, the access ends — files you delivered under a licence that permits keeping them stay usable under the terms printed at the time you took them, and access to copy or download anything further stops.

What a bundle grants

A bundle grants both deliverables — the prompt and the source — for every product inside it, permanently. A bundle has no expiry, no renewal and no dependency on any plan. The subscriber discount on a bundle changes the price paid, never the grant received.

The source exclusion

Changes and continuity

Prices and rules change; grants you already hold do not shrink. If we alter a plan, the change applies to purchases made after the date printed on this page. If we stop selling a product, it stays available to anyone whose plan or bundle includes it until that entitlement ends.

Independence

Frontary is an independent storefront built and run by its own team. It is not affiliated with, endorsed by, licensed by, or derived from any other asset marketplace, template library or design agency, and no third-party name or brand appearing in a product description implies a relationship.

Effective 1 October 2026. This page describes the build that is running now: accounts, orders and payments are real services, and an earlier version of this text said otherwise. Where this site and this page disagree, this page is the one that is wrong, so it was rewritten from the code that runs rather than from memory.

What leaves your machine, and to whom

Signing in sends your email address and password to Firebase Authentication (Google), which stores the credential and gives this site a session token. Creating an account, buying a plan or a bundle, downloading a product, or applying to the affiliate programme each make a request to frontary-api on Cloudflare Workers, which reads and writes this project's database on Cloudflare D1. No browser is given a key to that database: every request is authorised by the Worker against your own session. Payment itself is handled by Razorpay or Stripe in their pages; card numbers never reach this site or this Worker.

What is stored about you, and where

Under your account identifier: your email address and, on a purchase, what you bought, when, for how much, in which currency, and the payment provider's own reference. Entitlements (which plan, until when) are derived from that order. If you join the affiliate programme: the name, platform, audience size and profile link you type, plus which orders were attributed to your link and the commission each produced; payout account details are stored encrypted with the key held only in the server's own secret store, and only the last four characters are ever shown back. A click on an affiliate link stores a random anonymous id, a coarse browser class and a timestamp — not your name.

Every administrative action is written to an immutable audit log: which account acted, what it changed, when, and a one-way digest of the acting IP address rather than the address itself. Rows are never edited or deleted, and nothing currently erases them; that retention is a decision this project has not yet automated, so it is stated plainly rather than promised away. Ask and it will be removed by hand.

Cookies and tracking

No cookies are set by this site, and no advertising pixel or analytics tool is loaded. The session lives in Firebase's own storage, not in a cookie, which is also why the framing rules on this origin matter. Affiliate attribution uses a query parameter and first-party browser storage; it identifies a browser, not a person, and it clears when you clear site data.

Requests this page makes

Loading a page fetches the typeface from Google Fonts, the layout script from the Tailwind CDN, product imagery from Cloudinary, and preview documents from a separate Cloudflare Pages origin that exists specifically so untrusted asset code runs somewhere it cannot reach this site's data. Each of those hosts sees your IP address. The list below is measured from this page's own network timing, not transcribed from this paragraph.

Erase it yourself

This removes every record this site has written into your browser — your region, any likes, the viewer used to demonstrate locked states, and any admin drafts this tab is holding. It does not touch what the server stores under your account, because a button on a public page cannot be the way you delete an order record. For that, write to the address on the contact page and say which account; it is a manual request today and the honest answer is that it takes a person.

A licence describes what you may do with a deliverable. It is separate from entitlement: buying a plan can let you read a file without ever licensing its redistribution. The set below is complete — there is no hidden tier.

Always allowed

• Use in any number of projects you or your clients own.
• Modify, refactor, re-theme and remove parts of the source.
• Ship it in a commercial product, an agency deliverable or an internal tool.
• Rebuild the same result from a prompt in your own codebase.

Never allowed

• Resell, give away or republish the source or prompt as an asset.
• Offer it inside a template, kit, UI library or AI training dataset for others to take.
• Claim the original authorship as your own in marketing.
• Use any Frontary name or logo to imply endorsement of your product.

Warranties and liability

Assets are provided as they are, with no warranty that they suit your project or that a preview behaves identically in your stack. To the extent the law allows, our liability on any purchase is limited to the price you paid for it. If something is materially broken, tell us and we fix it or refund it — see refunds.

Digital delivery makes the ordinary answer useless, so here is the specific one. The two products are treated differently because one is access and the other is a file.

Both cases

A duplicate charge, a charge you did not authorise, or a file that will not open is corrected or refunded without argument and without a limit on how recently you used the account. Ask through the contact form with the product name and the region you were priced in; that pair identifies an order faster than any reference number we could invent.

No payment is processed in this build at all, so nothing in this section has yet been tested against a real transaction. When checkout goes live, this page is updated in the same release, not afterwards.

What each deliverable means for a refund

A plan

Refundable on request within 14 days of purchase, provided you have taken delivery of no more than three deliverables — a copied prompt or a downloaded package each count as one. After that, or after the window, the term runs to its end and is not refunded. Downgrading to a shorter term is not a refund; you keep what you took until it expires.

A bundle

Not refundable once the source has been downloaded, because the download is the product. This has no time limit in your favour: if the package is broken, missing files, or does not run in the stack its page claims, it is fixed or refunded however long ago you bought it. Unopened bundles are refunded in full.

Something here is unclear? Ask.