Digimarket.infoVerified SaaS Exchange

How to prove you own the project

A short, concrete guide to the optional proof of ownership you can attach when listing a project. Pick any single method below — the fastest one is usually the dashboard you already log into every week.

Accepted proof — pick one

  • A screen recording showing you logged into the code repository or hosting dashboard (GitHub, Lovable, Vercel, Replit).
  • A domain registrar screenshot showing the domain in your account.
  • A Stripe or analytics dashboard export for the project.

Up to 3 files, PNG / JPG / WEBP or PDF, max 8 MB each. Only our review team can see them.

Step by step

How to capture each proof

Each method takes under two minutes. Use whichever account you actually control.

GitHub

Screen recording or screenshot of your repository

  1. 1Sign in to github.com in your browser with the account that owns the project.
  2. 2Open the repository you are selling (the address should read github.com/your-username/repo-name).
  3. 3Make sure your username or organisation name is visible at the top of the page, together with the repository name.
  4. 4Take a screenshot of the whole page (or record a short clip while you open the repository) and upload it in the form.

Tip: A 10-second recording where you click into the repository is the strongest proof — it shows a real logged-in session, not a copied screenshot.

Lovable

Your Lovable project list

  1. 1Sign in to lovable.dev with the account that created the project.
  2. 2Open your projects list, then open the project you are selling.
  3. 3Keep the project name and the browser address bar in the shot — that is what shows the project belongs to your account.
  4. 4Screenshot the editor with the project open and upload it.

Tip: If you built the project with AI tools, this is exactly what we mean: the dashboard where your own projects are listed, opened by you.

Vercel

Vercel (or Netlify) project dashboard

  1. 1Sign in to vercel.com and open the team or account that hosts the project.
  2. 2Open the project so the production deployment and the connected domain are visible.
  3. 3Make sure your account e-mail or team name is visible on the page.
  4. 4Screenshot the project overview and upload it.

Tip: A screenshot of the project's Domains tab is ideal: it shows both the live site and the account behind it.

Replit

Replit workspace

  1. 1Sign in to replit.com with the account that owns the app.
  2. 2Open your Repls list so the project you are selling is visible.
  3. 3Open the Repl so your username and the project name appear together.
  4. 4Screenshot the workspace and upload it.

Tip: If the Repl is private, the URL plus your username in the header is enough.

Domain registrar

Domain registrar screenshot

  1. 1Sign in to the registrar where the domain is registered (Cloudflare, Namecheap, Porkbun, Gandi, OVH…).
  2. 2Open the management page of the domain you are selling.
  3. 3Make sure the domain name and your account e-mail (or registrant name) are visible.
  4. 4Screenshot that page and upload it.

Tip: If the domain is in a different account than the code, attach both screenshots — that is normal and not a problem.

Stripe / analytics

Stripe or analytics dashboard export

  1. 1Sign in to Stripe (or Google Analytics / Plausible) for the project.
  2. 2Open the dashboard showing the account e-mail and recent activity for the last 2–3 months.
  3. 3Export a CSV/PDF if the tool offers it, otherwise screenshot the dashboard.
  4. 4Upload the exported file or the screenshot.

Tip: Revenue proof and ownership proof are two different things: the revenue file backs your numbers, this file shows the account is yours.

How to take a screenshot

Capture the whole page — the project name and your account have to be visible in the same shot.

Windows
Win + Shift + S, then paste into the form or save as PNG
macOS
Cmd + Shift + 4, then Cmd + Shift + 4 + Space for one window
iPhone
Side button + Volume up, then crop in Photos and share the file
Android
Power + Volume down, then crop in Gallery and upload

What we cannot accept

  • A link to your dashboard instead of a file.
  • A screenshot of somebody else's account, or a stock image.
  • A shot cropped so tightly that the account or project name is no longer visible.
  • A screenshot that exposes passwords, API keys or two-factor codes.

Files go to private storage visible only to the Digimarket.info review team. They are never shown to buyers and never published. Before uploading, blur passwords, API keys, secret tokens and card numbers.

Proof of ownership — questions

What counts as proof of ownership?
Anything that shows the project lives in an account you control: a screen recording of you logged into the code repository or hosting dashboard (GitHub, Lovable, Vercel, Replit), a domain registrar screenshot, or a Stripe/analytics dashboard export. Up to 3 files, PNG/JPG/WEBP/PDF, max 8 MB each.
Is proof of ownership required to publish a listing?
No. Confirming the ownership declaration is required; attaching files is optional. Listings with proof are usually verified faster, and sellers who attach proof report fewer back-and-forth messages during review.
Who can see the files I upload?
Only the Digimarket.info review team. Files are stored in private storage, are never shown to buyers and are not part of your public listing.
What should I hide before uploading a screenshot?
Never show passwords, API keys, secret tokens, two-factor codes or full card numbers. Crop or blur them before uploading. A screenshot is only useful if it is safe to share.
Can I send a link to my dashboard instead of a file?
No. We review files, not logins — a link would mean giving access to your account, which is exactly what you should not do. A screenshot or recording gives us the same evidence without any risk to you.
I no longer have access to the account the project is in. What now?
Write to kontakt@digimarket.info before publishing. Describe the situation and we will tell you which alternative evidence works — for example a domain transfer record or a registrar invoice.
kontakt@digimarket.info