Is the API available today?
Not yet — we are onboarding early-access partners now. Joining the list is free, creates no subscription, and gets you sandbox access, launch updates and introductory pricing before general availability.
Who owns the logos our customers generate?
You do. We claim no rights in generated outputs and pass full commercial-use rights to you or your end users — you decide the split in your own terms. One honest note: under current US doctrine, purely AI-generated artwork may not qualify for copyright registration, which is exactly why the trademark route below matters.
Can an AI-generated logo actually be trademarked?
Yes, in principle. Trademark protection covers commercial identity and does not require human authorship — an AI-generated logo is registrable if it is distinctive, used in commerce and not confusingly similar to an existing mark. As with any logo, a clearance search before filing is the sensible step; none of this is legal advice.
How unique are the outputs? Could two of our customers get the same logo?
Icons are generated per request — there is no shared stock-icon pool being reshuffled between customers, which is the classic failure mode of template-based logo makers. Deterministic seeds mean identical results happen only on purpose: the same inputs with the same seed reproduce a logo, different seeds diverge. No generative system can promise global uniqueness, so we don't — but collisions by design are off the table.
How deep is the white label — can end users ever discover who is behind it?
There is no SMASHINGLOGO branding anywhere in the surface area: no watermarks, no vendor fingerprints in the SVG, PNG or JSON, and neutral error messages. The partner agreement adds the contractual side, including a commitment never to market to your end users. The EU AI Act's machine-readable marking for AI-generated images discloses that content is AI-generated — not who generated it — and is implemented without any visible watermark.
What happens to the data we send you?
By default, nothing stays: stateless mode processes brand inputs within the scope of the request and retains neither inputs nor generated assets — the response you receive is everything that exists. We keep only billing metadata such as request counts and timestamps. A GDPR data-processing agreement, sub-processor list and processing documentation are part of partner onboarding.
What are the rate limits — and what about a Black Friday spike?
Every plan has a sustained request rate with burst headroom on top, and temporary limit raises can be scheduled ahead of promotions or cohort onboarding days. At the limit you get clean 429 responses with Retry-After — requests are never dropped mid-generation. Overage terms are stated up front, not discovered on an invoice.
What exactly do we get back per generation?
A true vector SVG with real paths — not an auto-traced bitmap — plus high-resolution PNG renditions and structured JSON metadata: palette, fonts, layout and icon descriptors. The JSON is what lets you build your own editing and brand-kit features on top without ever calling us again for a color swap.
Can end users edit or regenerate their logo later?
Yes. Store the request parameters and seed and you can re-render or produce controlled variations at any time, on any pinned engine version. Layout, font and color changes need no regeneration at all — the JSON metadata carries everything your own editing UI needs.
You run a consumer logo maker yourselves. Why would a competitor use your engine?
Because the protection is structural, not just contractual: stateless mode means we cannot mine your traffic — brand names, volumes and outputs are simply not retained. The agreement additionally excludes using partner data for training or marketing and includes non-solicitation of your end users. You get ten years of engine development without funding a competitor's insight into your business.
How long does integration realistically take?
The first logo takes minutes: one REST endpoint, a sandbox key and copy-paste examples. A production integration — a checkout upsell or a full generation UI — is typically days, not quarters, and early-access partners get direct engineering support while they build.
What happens if we leave?
Everything already generated stays yours, forever — rights are never revoked at termination. Because outputs are open formats, nothing you shipped depends on our runtime, and in stateless mode there is no stored data left to delete. Lock-in is a pricing strategy; we would rather be kept by being good.