Launch plan
Accounts and library
How customers sign in, and how every ad and product they make ends up in a private account.
Signing in
| Method | Status |
|---|---|
| Planned | |
| Email and password | Planned |
| Two-factor with an authenticator app | Planned Optional for the customer |
| Meta (Facebook) | Later |
The desktop app signs in through the browser and keeps the session in the operating system's secure storage, the same place API keys live today.
Meta login
Signing in with Facebook is easy to add later. Publishing ads to a customer's Meta ad account is a separate and larger step: it needs Meta's app review and business verification. Treat them as two projects.
The account library
Each account shows every ad and every product the customer has made.
Today all of that lives on the customer's computer, so it has to sync to the cloud.
| Content | Size | Notes |
|---|---|---|
| Ads | Small | The layout document, a thumbnail and exported images |
| Products | Large | 3D models with textures |
| Artwork on packaging | Medium | Currently in the app's local database |
Privacy and security
- Every record and file belongs to one owner, and the database refuses everyone else. This is enforced in the database, not only in the app.
- Files are private and served through short-lived links.
- Passwords are handled by the sign-in provider and never stored by Ad Shots code.
- Photoroom and QuiverAI keys live only on the backend. Customers never see them.
- Customer API keys, where used, stay on the customer's machine as they do today.
Open questions
- Does a customer need to be online to use the app, or can they work offline and sync later?
- Is there one user per account, or can a brand invite teammates? The concierge service suggests brands will want more than one seat eventually.
Updated 2026-11-14. Built 2026-11-15.