Documentation

Guides

How DesignTech AI works, what it can do, and how your content is handled. Training a design, bringing your material in, running a production, and the guarantees the platform enforces in code.

Getting started

Two sections get you running: What DesignTech AI is, then Start here. The 44 feature walkthroughs below them are the full reference, to read when you need them rather than up front.

What DesignTech AI is

DesignTech AI is the production platform for B2B marketing teams. It turns the material you already own into the assets you need, in the designs your brand has already approved.

Repurpose

Turn one piece of source content into a full campaign. Point the platform at a webinar, a report, or a customer story, and get back the posts, ads, one-pagers, and email copy the campaign needs, written from that source. Every claim traces back to the line it came from, so one webinar becomes a quarter of assets.

Reproduce

Ship new creative in the designs your brand has already approved. Give the platform a piece that already cleared brand review; it learns the layout and the type down to the pixel, then produces new versions with your next offer in place. Text, logo, and call to action stay editable. The layout never shifts.

ContentCanvas

The compounding foundation. Everything your team has brought in and everything it has made, held in one connected record. It is what repurposing and reproducing both run on, and it gets stronger with every asset you add.

AI should not design your assets. It should produce them.

The creative judgment is yours. The strategy, the positioning, the design system your team fought to get right: that is human work, and generative tools are not good at it. What they are exceptional at is production, doing the hundredth version as carefully as the first, at a volume no team can staff for.

So this is not a design generator. It is a production platform that reads whatever you give it and produces to the specs and examples you provide: your templates, your brand rules, your reference material. It does not suggest designs. It executes on yours.

What that guarantees

Each of these is a gate in the production path, not a line in a prompt. An asset cannot reach you without passing through it.

It never draws your logo. Every asset renders the logo file you gave it, and a design calling for a mark it does not have on file goes out without one rather than with an invented version.

Nothing arrives that you cannot edit later. Assets are live layers, not a flat picture of a design: text, color, imagery, and layout are still editable months from now, with version history on every section.

Real text, real color, real type. Copy is live text set in your fonts and your exact hex values, not pixels painted to look like words, so it stays selectable, searchable, and exportable.

Every claim traces back to its source. Finished work records the material it was built from, and a reference that does not resolve is never filed.

Nothing leaves without a person. The platform does not post to your channels on your behalf: work is filed into ContentCanvas for you to review, approve, and take out yourself.

Your content is not training data. Model calls run on enterprise endpoints that do not train on your material, and isolation between workspaces is enforced in the database itself.

Start here, in three steps

Train one design, bring your material in, then produce. Half an hour end to end, and the first finished asset comes out of it.

Step 1
Train a design so the platform can make it

Your workspace can only produce designs it has been trained on. The platform never invents a layout, so the first move is to hand it one finished piece your team is proud of.

Open Train and answer one question: what does this design make? A webinar promo, an event one-pager, a customer story. That name becomes the template's name and the name of everything it produces.

Drop the finished piece in: an image, a PDF of up to 20 pages (a multi-page PDF trains as a deck, one slide per page), an HTML or Word document, or plain text. Then press Train this template.

The platform keeps the artwork, lifts every word, logo, and button off it, and names each fillable field the way a designer would: Headline, Subhead, Call to action.

Training takes a couple of minutes and runs on the server, so you can close the tab. The tile on Train shows live progress and survives a reload; a failed one tells you why in plain words.

The moment the template is ready, a Make Job named after it appears for your whole team: in production runs, in AI Home, and in every Automations picker.

Train the designs you rebuild most often: your LinkedIn single image post, your carousel, your webinar promo, your one-pager, your case study, your event banner, your ad creative. Train one, produce with it, then train the next. A ready template can also be fine-tuned in its own editor, where the base artwork is the frame's background so you can never grab or delete it by accident.

Step 2
Bring your source content in

Nothing is produced from thin air. Every asset is written from material you own, and that material lives in ContentCanvas, the app's home screen.

Drag a file straight onto the board. PDFs, documents, decks, images, audio, and video are all read. A file the platform cannot take says so plainly rather than failing quietly.

Point it at a URL to read one live page, or import a whole website's content in bulk.

Run a research job and it gathers current material from across the open web, cited, and files it as an ordinary source.

Connect an app on Integrations and its items appear as their own tab in ContentCanvas, ready to import exactly like an upload.

However it arrives, a source is split into sections you can search, quote, and pick from, and it keeps a reference back to where each part came from. Bring in the thing your next campaign is about: the webinar recording, the quarterly report, the customer story.

Step 3
Run a production

Producing fills a trained template with words drawn from your source. Your design, your material, a new asset.

One asset, words checked first: open Produce, pick the template, then the source it should be about and, if you want, the exact material inside it. Draft the copy and every field fills in, ready to edit.

The original wording sits beneath each field, because the original is the specification for how much text that space holds. Nothing is made until you press Proceed, and then you land straight in the finished asset's editor.

Several at once: start a production run from any source on the board. Keep all its material or pick the parts that matter, choose one or more templates, and each becomes one asset built as a live tile under the source.

A production run belongs to the server, so you can close the tab and come back to it. If a template you picked is still training, the run waits for it and shows that training's own progress.

What comes out is real, editable content filed into ContentCanvas: live text in your fonts and your colors, with a record of what it was built from. Download it in the formats its type supports, or share a link that opens with no account. The platform does not post to your channels for you: you take the finished file out and publish it yourself.

Worth doing before your first run: fill in Brand

Brand holds what is true for everything you will ever make: your voice, your colors, fonts and logos, who you sell to, and what you sell. Every job reads it before it writes a word, and the brand check measures every finished asset back against it. You can produce without it, but the output will be generically about your company rather than written for your buyer about your offering.

Find your way around

Where everything lives, and the one shortcut that reaches all of it.

01
The rail, top to bottom

AI Home (the assistant), ContentCanvas (your library and working board, the home screen), Tasks, Automations, Brand, Integrations (connected apps), then Train and Produce side by side, one flow read in that order. Below them sit search, Settings, this Help drawer, and your Account.

02
Jump anywhere

Press Cmd+K (Ctrl+K on Windows) at any time to jump to any destination, any Job, or any piece of content by name, from anywhere in the app.

03
Three ways to start the same work

Start a production run from a source on the ContentCanvas board, produce a single asset from the Produce page, or hand the work to AI Home in plain language. All three end in the same place: real, editable content filed into ContentCanvas with a record of what it was built from.

Bring your material in

Everything starts from a source: a document you upload, a page you point at, a recording, or an item pulled from an app you have connected.

04
Drop a file onto the board

Drag a file from your machine straight onto the ContentCanvas board. It uploads, shows itself being read, and lands as a source split into sections. PDFs, documents, decks, images, audio, and video are all accepted; a file the platform cannot take says so plainly rather than failing quietly.

05
Bring in a page, a site, or research

Point the platform at a URL to read one live page, import a whole website's content in bulk, or run a research job to have it gather and cite current material across the open web. All three arrive as ordinary sources in the same library.

06
Connect an app and import from it

Connect a third-party app on Integrations, on the left rail. Its items then appear as their own tab in ContentCanvas, and importing one turns it into a source split into sections, exactly like an upload.

Your content library

ContentCanvas is where everything your organization brings in and everything it makes lives, on one board. It is the app's home screen.

07
The board, and how it is grouped

The tabs across the top are grouped by where things came from: what you singled out (Starred, Folders), what you brought in (Source content, Research, Website), what is plugged in (each connected app), and what the platform made (Generated, Collections). Each card carries a cover, its format icon, and its stage.

08
Four ways to look at it

Switch layouts with the toggle: Canvas is the spatial board and the default, Grid shows covers, List is dense for scanning, and Graph shows lineage so you can see which assets came from which source. On a phone you land on List.

09
Search, filter, and drill in

Type in the search box to find anything by keyword or by meaning. Filter Generated work by workflow stage, or open Collections to slice the whole library by the kind of material inside it. Clicking a source on the board fans out everything made from it; clicking a production run opens what that run produced.

10
Every screen has its own link

Tabs, layouts, the thing you drilled into, even the section you selected are all in the address bar. Back and Forward work, a refresh restores exactly what was on screen, and you can send a colleague a link to precisely what you are looking at.

Train: teach it a design

Train is where your workspace's catalog comes from. One finished file in, one reusable template out, and a new Make Job for your whole team.

11
Name it, drop it, train it

Open Train and answer one question: what does this design make? That name (a Webinar promo, an Event one-pager) becomes the template's name and the name of everything it produces. Then drop in the finished piece itself: an image, a PDF of up to 20 pages (a multi-page PDF trains as a deck, one slide per page), an HTML or Word document, or plain text. Press Train this template.

12
What training does

Training is a tracked run you can watch in your Activity panel, and it takes a couple of minutes. The platform reads the design, lifts every word, logo, and button off the artwork while keeping the artwork itself, names each text element the way a designer would (Headline, Subhead, Call to action), and rebuilds the whole thing as an editable template. You can close the tab: the tile on Train shows live progress and survives a reload.

13
Your templates, and their tiles

Every template is a tile: the cleaned artwork as its cover, its name, and how many fields it has to fill. A tile still building says so, and a failed one tells you why in plain words. Open a ready template to fine-tune it in its editor: move and resize elements, restack layers, adjust type and color. The base artwork is the frame's background, so you can never grab or delete it by accident.

14
A ready template is a Job

The moment a template is ready, a Make Job named after it appears for your whole team: in production runs, in AI Home, and in every Automations picker. Removing a template stops it being offered, nothing more: the style it learned and every asset it produced are kept.

Produce: your design, new words

Producing fills a trained template from your material. One asset at a time on the Produce page, with the words checked before anything is made, or several at once from the board.

15
One asset, words checked first

Open Produce and pick the template, then the source it should be about, and optionally the exact material inside that source. Draft the copy and every field fills in, ready to edit, with the original copy shown beneath each one: the original is the specification for how much text that space holds. Nothing is made until you press Proceed, and then you land straight in the finished asset's editor.

16
Logos and pictures

An image field offers three ways in: pick from your existing content and brand assets, upload a file, or generate with AI. On a graphic, a field you leave empty leaves that element off the asset rather than rendering a blank; an HTML or text template keeps the picture it was trained with.

17
Brief the artwork by region

On a graphic template you can change the artwork itself before producing. Drag a box over the part of the picture you mean, describe the change, add as many regions as you like, then apply them in one AI pass. The edits are confined to the regions you drew; the rest of the artwork is untouched.

18
Several at once, from the board

To produce a batch, start a production run from any source: from its card on the board, from its page, or from AI Home. The platform pulls the source's usable material, you keep all of it or pick the parts that matter, then choose one or more templates; each becomes one asset, built as a live tile under the source. The run belongs to the server, so you can close the tab. If a template you picked is still training, the run waits for it and shows the training's own progress in the tile.

19
Versions on demand

Every produced asset carries a small plus beneath it on the board: describe the changes and a new version is produced, chained under its parent. And an uploaded image of a finished design can become an editable copy in one click with Create a new version of this source; the platform trains the template the first time and reuses it after that.

The asset page

Every generated asset has one page. It previews the work as it will really look, and it is also where you edit, review, and take it away.

20
View and Edit, one page

The asset opens in View: a clean proof of the finished work on a dark mat, at the size and shape it really is. Toggle to Edit in place. There is no separate viewer and editor to keep straight, and the preview adapts to the medium, so a deck pages as a deck, a document reads as a document, and video and audio play.

21
Its cover is the real thing

Covers are made from the asset itself, not a screenshot of a page. A LinkedIn post covers as the feed card it will be: your brand name and avatar, the copy folded where LinkedIn folds it, the creative edge to edge, and the reaction bar.

22
Where it came from

Each asset records what it was built from, so you can trace any piece of finished work back to the source, the run, and the template that made it, from the asset page or from the Graph layout.

23
Take it away

Download the asset in the formats its type supports, take everything a run produced with Download all, or mint a share link that anyone can open with no account. The platform does not post to your channels on your behalf: you take the finished file and publish it yourself.

Editing what it made

Generated work is real, editable content, not a flat picture. The editor you get is the one that suits the medium.

24
The section editor

Most deliverables open into the section editor: the outline on one side, a live preview on the other, kept in step. Click something in the preview to find it in the outline and the other way round. Click a heading or paragraph and type; there is no Edit button and no overlay.

25
Edit one section with AI, and roll it back

Ask AI to rewrite, shorten, or restyle one section without touching the rest. Every section keeps its own version history, so you can compare what changed and restore an earlier version.

26
Graphics, decks, and images

A designed graphic opens on a spatial canvas: drag elements, resize with the handles, restack the layer list by drag (it shows the real front-to-back order), add pages, apply a style, or reflow with the layout picker. A deck pages slide by slide, each slide fitted to the pane. An image opens to crop, rotate, replace, regenerate, or refine a selected region with AI, archiving each version as it goes.

27
Video and audio

A video opens on a timeline to trim a range, grab a frame at the playhead as a new image, or export a section. Voiceovers and music open in the audio editor.

Brand rules and market

Brand is a destination on the rail. It holds the things that are true for every asset you will ever make: how you sound, how you look, who you sell to, and what you sell.

28
Brand Voice

The Brand Voice tab holds your positioning, your tone, and the phrases that must always or never appear. Every job that writes anything reads it first.

29
Brand Assets

Brand Assets holds your colors, fonts, logos, and reusable artwork, with bulk upload and an import that reads a PDF of brand guidelines. If the platform has never been given a logo, it will never invent one.

30
Buyers and Offerings

Build one persona per buyer type in your committee, and list the products or services you sell. Attach a persona and an offering to a run and the asset is written for that buyer, about that offering, instead of being generically about your company.

Training: teach it your taste

Two features share a word, so keep them straight: Train, on the rail, teaches the platform one exact design to reproduce. Training, under Brand, teaches it your general taste from batches of past work: how your carousels open, how tight your one-pagers run. That taste steers everything it writes and designs.

31
Drop your work in

Under Brand, Training, Examples, drop finished files in. You do not have to tell the platform what they are first: it looks at each one and works out what it is, and you only correct what it got wrong. One drop can teach several formats at once, and a logo dropped in is recognized as a logo and routed to your Brand Kit.

32
What it read from each example

Each file is read by four separate passes, and a pass only runs where it has something to say. Open an example to see the findings: the file itself beside the individual elements the platform picked out of it, and what it concluded from each. You can see the evidence, not just the verdict.

33
Styles: what it has learned

Brand, Training, Styles is the Style Studio: everything Training has distilled, read back to you. The specimen at the top is painted in your own captured colors with your own voice quoted in it. Each learned rule is a card carrying its source, so you can see which example taught it, and what changed. Tokens it has never seen show as empty, never as a color you do not have.

34
Correct it, test it, and see the gaps

Tap a swatch on the specimen to correct that one token. Run a test to see something made to your style right now, side by side with the example that taught it. The coverage strip shows one chip per format, so you can see at a glance what it has learned and what it has never been shown; a rule can be scoped as narrowly as one offering in one format.

The brand check

Once the platform knows your brand, it can mark its own homework. Every finished asset can be measured against your brand and stamped with a score.

35
Run the check, read the score

An asset that has never been measured shows an invitation to check it, on the asset page and in the editor. The result is scored on four axes (color, type, logo, layout) rather than as a single number, so a low score tells you where the problem is, and it says what it measured: the whole asset, or just the part you last changed.

36
It advises, it never stands in your way

The check is observational. It will never stop you approving or downloading anything. A score produced by an older version of the check is labeled out of date with an offer to run it again, rather than being presented as current.

Review and approval

Nothing has to go out on one person's say-so. An asset can be routed to named people who have to respond before it is finished.

37
Send it to named reviewers

Send for review from the asset page, the task list, or the board. You name the people who have to sign off, and the asset waits on each of them until they respond. Reviewers outside your organization get an emailed link and can approve or request changes without an account.

38
The status is the control

An asset's status is a control you set, not a label you read. Changing it is how work moves from draft to finished. A Changes requested card says what was actually requested, not just that something was.

39
The review trail

Every asset keeps its approval history: who was asked, who responded, what they said, and the latest change request pinned to the top. A reviewer whose invitation failed to send is shown as failed with a retry, rather than sitting there as though they are still thinking about it.

Automations

Jobs do not have to be run by hand. Automations is the one place standing work is visible: everything scheduled, triggered, or queued, and everything that has already run.

40
Schedules and repeats

Any Make Job can run on a schedule: pick the content it should draw from, optionally give it an angle, and each fire produces one finished asset in your trained design. Run it once at a set time or on a cadence; the calendar is the default view, and any finished run can be turned into a schedule with Repeat.

41
Lists and triggers

On a list works down a queue, one item per run. On trigger fires when something happens, and the useful one is a new source landing: when new content arrives, make my trained design from it. Both file their output into ContentCanvas like any other run: a schedule produces assets, it does not post them anywhere.

42
Ideas and history

The Ideas view is your planned backlog, where content ideas you kept from an ideation job wait to be produced. History keeps a record of every execution, so you can see what ran, when, and what it made.

Settings and your team

Most day-to-day surfaces live on the rail itself, so Settings is smaller than you might expect.

43
Where things live now

Brand, Integrations, Train, and Produce are rail destinations, not Settings tabs, so most members rarely need Settings at all. Organization admins manage Users, Models, and Billing there, and some workspaces also carry Usage and Performance.

44
Getting help

This Help drawer holds a live catalog of every Job your workspace can run, our privacy and security documentation, and a contact form. If the platform is down or in maintenance you will see a notice in the app itself, and the system status page is linked from Contact.

What it can do

Everything DesignTech AI can do, in plain language. You teach it your designs on Train, and you run Jobs; under the hood the platform works through the right steps to deliver each one. Start with How it works, then browse the Jobs your team can run and what each one produces.

How it works

DesignTech AI is built in layers. You only ever touch the top two: you teach it templates on Train, and you run Jobs. Everything below is the machinery that makes them work.

Templates

The unit of production. On Train you hand the platform one finished design your team is proud of, and it learns the style, the layout, and every fillable field from that file. Your workspace can only produce what it has trained: the platform never invents a design, so everything it makes looks like something your team made.

Jobs

What you actually run. Training a template automatically mints its Make Job, one marketing outcome with the design already decided. Alongside those, the platform ships Jobs that plan, research, and measure. Pick one, fill in a few details, and run it.

The steps behind a Job

Underneath, a Job is a sequence of single operations: read the source, research the topic, draft the words, fill your template, file the result. You never run those one at a time. The Job runs them for you, in the right order. What it can do, further down, is the full inventory of the operations it has to work with.

How they fit together

Start a production run from a source on the ContentCanvas board, produce a single asset from the Produce page, or hand the work to AI Home. Everything produced is filed straight into ContentCanvas as real, editable content, with a record of what it was built from.

Your brand steers all of it

Nothing is generated in the abstract. Your brand rules, your buyer committee, your offerings, and everything Training has learned from your own work are injected into every step, and the finished asset is measured back against them by the brand check.

Jobs · Make an asset

One per trained template. Each produces one finished asset in that design, filled from your material and filed into ContentCanvas ready to review, edit, and download. Train a design and its Make Job appears here on its own.

Compose a Document

Compose a polished written document from a source.

Develop a Content Idea

Grow a one-paragraph idea into the finished piece.

Render a Video

Render selected clip segments into a finished video.

Jobs · Plan and research

Work out what to make and who it is for, before you produce anything.

Analyze and Recommend

Recommend the right content to make from a source.

Audit Your LinkedIn Content

Compare your ContentCanvas library against what you have actually posted on LinkedIn, and get a gap analysis plus a ranked list of repurposes to publish next.

Build a Media Plan

Set a monthly budget and average deal value and get a full-funnel B2B media mix model: AI proposes the channel mix and benchmark assumptions, the platform computes spend → leads → opportunities → sales → revenue → ROAS, and files it as an editable, exportable plan in ContentCanvas.

Build a Persona from a LinkedIn Profile

Point at a real LinkedIn profile and get a sharp, usable B2B buyer persona — their priorities, pains, how to reach them on LinkedIn, and the messaging that lands — grounded in that person’s actual role and background.

Competitor Review

Pull latest news and messaging for a competitor

Enrich an Account for ABM

Point this at a target account's LinkedIn company page and get an ABM-ready enrichment: their public shape (size, industry, product motion), what their people are posting about, where the openings are, and 3 to 5 outreach angles tied to observed evidence.

Extract Highlights from Content

Pull the quotes, stats, and key points from a source.

Ideate Social Posts

Turn one piece of source content into five social post ideas, each a hook, a one-line angle, the buyer persona it speaks to, and why it matters.

Plan a LinkedIn Ad Campaign

Get a ready-to-implement paid LinkedIn campaign plan: the recommended objective, a target audience built from real LinkedIn facets and your buyer personas, budget and schedule, the creative to run, tracking to set up, and the exact Campaign Manager steps.

Research a Topic

Research any topic into briefed, build-ready notes.

Review a LinkedIn Competitor

Point this at a competitor's LinkedIn company page and get a briefing on what is working for them: their best-performing post formats, the hooks and angles that earn engagement, where the gaps are, and how to respond.

Review Your Best LinkedIn Posts

Point this at your own LinkedIn company page and get a ranked read of your best-performing posts: the hooks and angles earning engagement, the formats that landed, and what to double down on next.

Jobs · Publish

These would send a finished asset out through a connected channel, and they are switched off today: nothing leaves the platform without you taking the finished file out yourself.

Publish Content

Push a change set to a connected publishing app.

Publish to a Connected App

Push a change set to any connected publishing app the org has authorized (Composio).

Jobs · Measure

Turn performance data into a decision.

Analyze Performance

Analyze metrics and surface what actually matters.

Pull Campaign Metrics

Pull performance metrics from a connected app.

What it can do · Gather

Get the raw material into the platform.

Ingest source

Read a pasted, uploaded, or selected source into clean markdown the rest of a job builds from, keeping a reference back to where each part came from.

Research

Research an objective across the open web and return one grounded, cited briefing. Never invents a claim.

Search ContentCanvas

Find the best existing content in your library for a topic, using meaning as well as keywords. Read-only.

Fetch a LinkedIn company page

Read a public LinkedIn company page and its recent posts, rank them by engagement, and file the result as a source.

Fetch a LinkedIn profile

Read a public LinkedIn person profile and file it as a source document, ready to build a persona from.

Audit your LinkedIn content

Compare what is in your ContentCanvas library against what you have actually posted on LinkedIn, and report the gaps plus ranked repurposing ideas.

Plan a LinkedIn ad campaign

Produce a ready-to-implement LinkedIn ad setup: objective, facet-based audience, budget, creative, tracking, and the Campaign Manager click-path.

Transcribe media

Turn a video or audio clip into a transcript with a word-level, timecoded timeline.

Pull ad metrics

Pull performance data from a connected ad account as structured, time-series records.

What it can do · Decide

Decide what matters before producing.

Extract material

Mine a source for quotes, stats, testimonials, insights, and headline lines, each grounded in the source.

Recommend ideas

Given existing content and the buyer persona it targets, propose a ranked set of repurposing ideas, each with a detailed rationale and the Job that produces it.

Ideate content

Propose several content-idea briefs, pause for you to pick the ones worth keeping, and file those to the Planned backlog on Automations.

Analyze and recommend

Turn performance data into a plain-language read plus ranked, actionable recommendations with a confidence on each.

Video edit

Select the strongest contiguous segments of a transcript to keep, as an ordered edit list.

What it can do · Make

Generate words, design, data, and media, on brand.

Brand

Inject the Brand Kit (voice, required and banned phrases, colors, fonts, logo) as a directive every AI step follows.

Persona

Inject the chosen buyer persona so the output speaks to that buyer's pains and language. Can fan a run out into one asset per persona.

Train a template

Read one finished design into a reusable template: keep the artwork, lift off every word and mark, name each fillable field the way a designer would, and learn the style and layout. A ready template mints its own Make Job.

Produce from a template

Fill a trained template with new words and images drawn from your material, at the template's exact geometry. Every production run ends here, so what comes out looks like what you trained.

Author an asset

The authoring engine for composed work: writes the finished, on-brand artifact a Job asks for, as a flowing document or a designed page.

Compose

Compose a titled, sectioned document from a source, grounded in it and steered by a brief.

Format faithfully

Restructure a document into your house style without changing a single word. Built for legal, HR, and compliance text.

Chart

Turn raw numbers into one structured chart (bar, pie, table, or metric). Never invents figures.

Media plan

Compute a full-funnel media mix model from a budget and an average deal value, filed as an editable plan.

Recreate as HTML

Rebuild a flat image as a pixel-faithful, editable page with live text layers.

Convert to graphic

Rebuild a flat image as an editable spatial graphic you can drag and restyle.

Generate image

Generate promo imagery from a scene description, optionally guided by one or more reference images.

Generate video from image

Generate a short video clip from a supplied still image.

Generate voiceover

Synthesize a spoken-word voiceover from a script, in your organization's voice.

Generate music

Generate a short, licensing-safe instrumental clip from a prompt.

What it can do · Finish and automate

Turn assets into files and act across connected apps. The platform can be wired to post on your behalf, but that is switched off today: you take the finished file out yourself.

Render video

Render a finished MP4 from an edit list, with an optional branded intro and outro.

Automate across connected apps

Run a plain-language objective across your connected apps, discovering and calling the right tools across as many apps as the task needs.

Publish change set
switched off

Would push an approved change set to a connected destination behind a human go-live approval. Not enabled: nothing leaves the platform without you taking it out yourself.

Publish to a channel
switched off

Would publish one filed asset to a connected LinkedIn company page behind an approval. Not enabled.

Push creative to LinkedIn Ads
switched off

Would upload an image creative into your LinkedIn Ads asset library. Not enabled.

Privacy

Privacy Policy

This Privacy Policy explains how DesignTech AI collects, uses, shares, and protects information when customers and authorized users access the platform.

Last updated: June 11, 2026

1. Scope

This Privacy Policy explains how DesignTech AI collects, uses, shares, and protects information when customers and authorized users access the DesignTech AI platform.

This policy applies to information processed through the DesignTech AI application, support interactions, and related customer operations. It should be read together with any applicable customer contract, data processing addendum, and subprocessor register.

2. Information We Collect

We may process account and identity data such as name, email address, authentication identifiers, and organization affiliation.

We may process customer content and assets uploaded to the platform, including documents, images, video, text, metadata, and workflow configuration.

We may also process integration data from connected third-party systems and operational metadata such as workflow runs, audit events, API activity, timestamps, and support diagnostics.

3. How We Use Information

We use information to provide and operate the platform, authenticate users, enforce access controls, process customer content through configured workflows and AI services, and support service reliability and compliance obligations.

We may also use operational metadata for troubleshooting, customer support, security review, and service administration.

4. AI Processing

The service includes AI-assisted workflows. The current production path sends AI requests directly to Google Vertex AI, including Gemini models and Anthropic Claude models served through Vertex AI, with no third-party AI request-routing intermediary.

Customer content is processed to fulfill requested operations. AI model execution runs on Google Cloud infrastructure under that provider's data processing terms.

Customers requiring contractual commitments on AI processing, training restrictions, or regional deployment should rely on the applicable order form, DPA, and supporting diligence documents.

5. How We Share Information

We share information only as necessary to operate and support the service, including with subprocessors and service providers used for hosting, database operations, file and media storage, and AI model execution.

As of the current production review, the baseline providers for these functions are Render (hosting), Supabase (managed Postgres), Google Cloud Storage (file and media storage), and Google Cloud / Vertex AI (AI model execution). Search and content indexing run natively in Postgres, with no third-party search service.

A current subprocessor register should be used for customer diligence and contractual review.

6. International Transfers

The service relies on providers operating in multiple regions. Data may therefore be processed in the United States or other jurisdictions where the in-scope providers operate.

Customers with specific regional or transfer requirements should ensure those requirements are captured in the applicable contract documentation.

7. Retention

Retention periods depend on the type of data and the relevant system of record. DesignTech AI does not apply a single universal retention period to every class of customer data.

Detailed full execution payload logs used for operational troubleshooting are retained for a short default period in the current implementation. Other data sets, such as content, assets, account records, and search indexes, follow different lifecycle rules.

Customers should use the applicable retention schedule and contract documents for any definitive retention commitment.

8. Security

DesignTech AI relies on a combination of application controls and managed service provider security controls. Additional implementation detail is available in the current Security Overview and customer diligence documents.

9. Customer Rights and Requests

Customers may request access, export, correction, or deletion assistance through their account team or support channels, subject to applicable law and contractual responsibilities.

Where DesignTech AI acts as a processor on behalf of a customer, the customer remains responsible for handling data subject requests and providing lawful instructions.

10. Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes to the service, subprocessors, legal requirements, or internal controls.

11. Contact

Privacy inquiries may be directed to:

Security

Security Overview

This page summarizes the current security posture of the DesignTech AI service based on the implemented application architecture and the managed service providers used in production.

Last updated: June 11, 2026

Production Stack

The baseline production stack currently includes Render for application hosting, Supabase for managed Postgres database services, Google Cloud Storage for file and media storage, and Google Cloud / Vertex AI for AI model execution. Search and content indexing run natively in Postgres (full-text and trigram), with no third-party search service. Each managed-provider name links to that provider's public trust center.

Authentication and Access Control

The application uses Auth0-backed authentication in production when configured and resolves authenticated users into application-level roles.

The platform implements role-based access controls, including super admin, organization admin, and user roles, with organization scoping enforced through the application and storage layers.

Development-only fallback login behavior exists in the codebase for local environments when Auth0 is not configured and should not be enabled for production customer environments.

Trust centers:

Logging and Data Protection

The service records audit signals for selected user and administrative actions and supports detailed execution payload logging for certain AI operations.

In the current implementation, detailed full execution payload logs are retained for 60 minutes by default and are subject to redaction logic for common secret patterns.

This page should not be interpreted as a commitment to any universal log-retention period beyond the current documented implementation.

AI Routing and Model Processing

Current application code sends AI requests directly to Google Vertex AI, including Gemini models and Anthropic Claude models served through Vertex AI. There is no third-party AI request-routing intermediary in the request path.

Model execution therefore runs on Google Cloud infrastructure under that provider's data processing terms.

This page does not state that all AI processing occurs only in the EEA or only on DesignTech AI-managed infrastructure.

Trust centers:

Versioning and Recovery Aids

The platform includes content versioning and per-section asset versioning for relevant objects. Those features support review, rollback, and operational recovery for specific content and asset workflows.

Incident Handling

Security incidents affecting customer data should be handled through documented internal processes, applicable provider processes, and contractual notification obligations.

This overview does not claim the existence of a dedicated 24/7 internal SOC, a fixed notification window, or any certification held by DesignTech AI unless separately evidenced.

Vulnerability Reporting

Security questions or vulnerability reports may be directed to:

Contact

Contact us

Send our support team a message, or reach a team directly by email.