Comparisons
Us and Aragon, from a data protection angle
What we can honestly say about Aragon as of September 2026, and exactly how consent, retention and deletion work on the Starkie Teams side.
From $39 per person, volume discounts from 5 people.
- 40 headshots per person
- About an hour from selfies to download
- Nobody on the team needs an account
Aragon comes up regularly when companies compare options for AI headshots and, according to its own site, addresses teams as well as individuals. We have not verified its current feature set or prices as of September 2026, and we are not going to summarise a competitor from memory, so this page does something more useful for a buyer: it sets out, in detail, how the employee side of Starkie Teams handles consent, storage and deletion. That is usually the section where a purchase for thirty colleagues either clears an internal review or stalls in one.
Comparing
What to check before you choose.
The questions a team buyer should put to any headshot tool, and how Starkie Teams answers them. For the other tool, check their current site.
| What to check before you choose. | Starkie Teams | The other tool |
|---|---|---|
| One-time credits, no subscription | Yes | See their site |
| 40 headshots per person | Yes | See their site |
| One style enforced across the whole team | Yes | See their site |
| Teammates need no account | Yes | See their site |
| Admin approval before photos go out | Yes | See their site |
| Consent text versioned and logged per person | Yes | See their site |
| API and signed webhooks | Yes | See their site |
| Published in English and Italian | Yes | See their site |
The honest scope of this comparison
We will not tell you what Aragon charges, how many images it returns, how long it retains uploads or which sub-processors it uses, because we do not know those things to the standard we would want to be held to ourselves.
Their site answers them, and any answer should be dated when you record it, since products in this category change quickly. What follows is our own behaviour, described precisely enough that a data protection officer can check it against the documents we publish rather than against a claim on a marketing page.
The result
Everyone, in the same light.
Choose a backdrop and an outfit once. Every person who joins is generated inside that style, so the team page finally looks like one team rather than a collage of whoever had a photo.
Sample headshots generated by Starkie from phone selfies.
Consent, storage and erasure on our side
Each employee accepts a consent text before uploading anything, and the acceptance is stored together with the version of the text they were shown; a change to that text sends them back through it instead of carrying the old acceptance forward. Uploaded selfies are deleted when their retention window ends.
Nothing under the Teams storage prefix has a public address: reads are short-lived signed URLs. Any person can clear their own record from the private page in their invitation and receives a written deletion certificate, and anyone at all can raise a request through our public privacy request form.
Your selfies are used to generate your headshots and deleted at the end of the retention period.
What the organiser sees
The whole run, from one screen.
Invites, consent, approval, downloads and the branded profile pictures, each a step in the same place.
- Invite peoplePaste emails or upload a CSVOpen linkCopy linkstarkie.ai/teams/join/x7q…Only @acme.com addresses24 invited
- DownloadsWhole team, one archive24 people · 960 files
- One folder per person
- Approved people only
- ReviewTia40 headshotsAwaiting approval
ApproveRequest a retakeReasonThe tie: could we try the open collar? - Branded profile pictureACMECompany frame1024 · 512
Re-rendered when the template changes
- Before you uploadConsent text v3
Your selfies are used to generate your headshots and deleted at the end of the retention period.
I agreeAccepted · logged - Webhookmember.photos_readyDelivered
X-Starkie-Signature: t=1700000000,v1=5257a8… · Signed{ "type": "member.photos_ready", "organizationId": "org_…", "data": { "memberId": "cle…" } }
Documents you can read before you buy
Four published documents cover the ground a review usually asks about: the security page, the sub-processors list, the data processing agreement and the privacy notice written for Teams.
They are versioned and carry a last-updated date, and the sub-processor list is generated from the same source as the annex inside the agreement, so the two cannot drift apart. None of this is legal advice, and we would encourage exactly the same scrutiny of us as of anybody else on your shortlist, including asking for the equivalent documents in writing.
The difference
A shoot day, or an afternoon.
Booking a photographer
- Find a date the whole team can make
- Book a room and a photographer
- Chase the people who were travelling
- Wait for retouched files
- Start again for every new hire
With Starkie Teams
- Invite by email, CSV or one link
- Everyone uploads selfies from a phone
- Remote colleagues take part on the same terms
- 40 headshots each in about an hour
- New hires get the same style, whenever they join
Pricing
One credit per person. Discounts stack as you buy.
No subscription and no seats. A credit is one person’s 40 headshots, and the discount on every purchase is set by the credits you have bought so far.
- First 4 creditsList price$39.00 each
- 5+ credits20% off$31.20 each
- 25+ credits30% off$27.30 each
- 100+ credits40% off$23.40 each
- 250+ credits50% off$19.50 each
Estimate your price
- Price per person
- $31.20
- Volume discount
- 20%
- Subtotal
You're in the 20% band. 15 more people reaches 30%.
Prices in US dollars. One credit per teammate.
Trust
Read it before you buy.
The documents a procurement or IT team asks for, published rather than sent on request.
- Data Processing AgreementRoles, sub-processing, retention and deletion, in writing.
- Sub-processorsEvery third party that touches a photo, and why.
- SecurityHow photos are stored, who can open them, and for how long.
- Privacy notice for teamsWhat each teammate is told before they upload a selfie.
- GDPRRights, requests, and how to exercise them.
Frequently asked questions
Does the employer ever hold the original selfies?
No. The person uploads through a link of their own, having accepted the consent text in person, so the company is never in the chain of custody for source images. Admins see the generated galleries for their organisation, which is the basis of both the review queue and the group download.
What does the deletion certificate contain?
A reference, the address the request related to, the organisation it belonged to, the exact time, and a tally of everything removed. It is sent by email when a member is purged, so the person has a record they hold themselves rather than one they have to request later.
Can we ask for a data processing agreement?
It is published rather than negotiated per customer, with a version number and a date, and it carries an annex listing the sub-processors involved. Reading it before a purchase is the point of publishing it.
Is this page a criticism of Aragon?
It is not. We have no verified findings about them to report and we are not going to imply any. If a reader wants a like-for-like table, the honest way to build one is to ask both vendors the same written questions and compare the answers with a date attached.
Give the whole team the same headshot, without the shoot day.
Free to set up: you only pay when you buy credits. There is no subscription, and you don't need a card to start.