Portraitor operates no accounts and keeps no copy of your email address, so a data request cannot be checked against a password or matched to anything it holds. Its Your Data Rights page says the address you enter is sent to its payment processor, which returns the customer reference your payment and Pass records hang from, and that a verification link sent to that address, pressed by you rather than followed automatically, is what confirms the request.<\/p>\n\n\n\n
Most services answer the identity question with a login. Portraitor publishes no login, which moves the question rather than removing it.<\/p>\n\n\n\n
The Your Data Rights page, version 1.3, last updated 30 September 2026, sets out the whole of what it does instead. This page reports that machinery and nothing beyond it. It is a description of published pages, not advice.<\/p>\n\n\n\n
The Privacy Policy, the same version, states in its summary that the Service operates no user accounts and retains no email address. The Your Data Rights page says it from the other side: Portraitor operates no accounts and holds neither your name nor your email address, and there is no account to delete.<\/p>\n\n\n\n
Both halves of that matter when a request arrives. A service with logins can check a password. A service that keeps your email address can compare the address on a request against the one in its own records. Portraitor’s published pages describe neither, so neither check is available to it. The page does name who a request goes to: the controller responsible for the data it describes, and the party a request under it is made to, is Project 54, with the registered company behind that name set out in the Privacy Policy.<\/p>\n\n\n\n
One thing is left. The Your Data Rights page describes access as obtaining a copy of the data associated with your email address, and the Privacy Policy says that because the Service operates no accounts and retains no email address, the scope of most requests is limited and the personal data associated with you is held by its payment processor. The address is the key. The lock is somewhere else.<\/p>\n\n\n\n
The Your Data Rights page states the mechanism in two sentences. Because Portraitor does not hold your email address itself, it locates your records by asking its payment processor which customer the address belongs to, and the reference they return is what links to your payment and Pass records.<\/p>\n\n\n\n
The Privacy Policy names that processor. Payments on the website are processed by Stripe, and the register of third parties lists Stripe as receiving your email address, card details and billing country, for the purpose of taking payment, sending receipts, and holding the only copy of your email address. The same policy says the address is passed to Stripe at checkout with no copy kept, and is retrieved from Stripe only at the point of delivery rather than copied into Portraitor’s own records.<\/p>\n\n\n\n
So the identity step runs outward. An address typed on the data rights page goes to Stripe, Stripe answers with a customer reference, and that reference is what the payment history and any Pass are found through. The Privacy Policy adds one restriction on the records side: every request concerning a Pass is tied to the session that made it, so one customer cannot reach another’s records by altering a request. The Your Data Rights page notes that a Pass contains no information identifying you, so there is nothing within it to erase. Every party the policy names as receiving anything is listed in its register, covered in the page on who else receives your chat<\/a>.<\/p>\n\n\n\n Entering your address does not file you anywhere. The Your Data Rights page says the address is used to perform that lookup and to send you the verification link, and that it is not added to Portraitor’s records by making the request, with one exception: to limit repeat requests an irreversible code derived from your address is kept until the link expires. The page says that code cannot be turned back into your address and is cleared automatically.<\/p>\n\n\n\n The retention table in the Privacy Policy carries the same row, described as an irreversible code derived from the requesting email address, used only to limit repeat requests, with the record cleared by daily maintenance once the link has expired.<\/p>\n\n\n\n That is the inverse of what an account does. The one thing a request leaves behind is there to stop the same address asking repeatedly, not to recognise it next time, and the page says it cannot be read back into an address at all.<\/p>\n\n\n\n The verification step is manual on purpose, and the page says why. Verification is completed by you rather than automatically, so that automated email scanners cannot trigger it. The verification screen repeats the reason: verification is not automatic, so that automated email scanners cannot trigger it on your behalf.<\/p>\n\n\n\n A link that software could follow would be a link something other than the recipient could complete. The pages do not describe those scanners further; they state the reason and the design, which is a button behind the link that waits to be pressed. The request panel says the link confirms your identity, and that a request is processed within 30 days.<\/p>\n\n\n\n The two kinds of request are not held to the same clock. The Your Data Rights page says links to view or export your data expire after 24 hours, and that deletion links expire after 30 minutes. The Privacy Policy’s retention table carries both figures. A request that only reads has most of a day. A request that erases has half an hour.<\/p>\n\n\n\n An erasure also asks for something typed. The confirmation screen carries a warning, states that the action cannot be reversed, and asks you to type the word DELETE to confirm. The warning names what the erasure does: it removes your customer record from the payment processor, taking your email address off it. What survives that request, and for how long, is set out in the page on deleting your data from a chat analyser<\/a>.<\/p>\n\n\n\n The asymmetry is the part worth noticing. Reading is reversible and gets 24 hours. Erasing is not, and gets 30 minutes plus a typed word.<\/p>\n\n\n\n The single handle has one place where it does not exist. The Your Data Rights page says that if you bought in the iPhone app, your purchase records are not linked to your email address, so a request made on that page by email address cannot find them. It names a separate route for those records: writing to admin@portraitor.ai with your Pass code or the order ID on Apple’s receipt.<\/p>\n\n\n\n The Privacy Policy explains where the gap comes from. In the app, Apple takes the payment rather than Stripe, and the address is not passed to Stripe at all. The app asks for an email address because the portrait, and a Pass code if one was bought, are delivered to it, and the policy says that address is not stored on Portraitor’s servers. There is therefore no Stripe customer for the lookup to return, and on that page the lookup is the whole of the mechanism.<\/p>\n\n\n\n Portraits themselves sit on the device rather than on a server by either route, which the page on where your portrait is saved<\/a> covers.<\/p>\n\n\n\n What the flow establishes is narrow, and the pages are specific enough to say so. For a website purchase they describe one check: an address is entered, a link is sent to it, and the link is pressed. Whoever presses it has shown that mail sent to that address reached them. The published pages describe no second factor, no security question and no comparison against anything Portraitor holds, because on their own account it holds nothing to compare.<\/p>\n\n\n\n The pages do not say what happens when more than one person can open that mailbox, and they describe no other route to a website purchase’s records. They say what the lookup is and what the link proves, and they stop there. This page stops with them.<\/p>\n\n\n\n The trade behind all of it is the one Portraitor makes everywhere: there is no login to lose, and no login to prove you are you. The guide to buying a chat analysis without an account<\/a> sets out the rest of that bargain, and the page on what crosses the payment gateway<\/a> covers the Stripe side of the same arrangement. The masking step that runs before any purchase is shown on the Portraitor home page<\/a>.<\/p>\n\n\n\n The published pages describe no check other than a verification link sent to the address entered, so completing a request for a website purchase takes access to the mail sent to that address. The Your Data Rights page says the address is used to look up the customer at the payment processor and to send that link, and that verification is completed by you rather than automatically.<\/p>\n<\/details>\n\n\n\n It asks its payment processor. The Your Data Rights page says that because Portraitor does not hold your email address itself, it locates your records by asking the processor which customer the address belongs to, and the reference returned is what links to your payment and Pass records.<\/p>\n<\/details>\n\n\n\n The page says the address is not added to its records by making the request, with one exception: an irreversible code derived from the address is kept until the link expires, in order to limit repeat requests. It says that code cannot be turned back into your address and is cleared automatically, and the Privacy Policy’s retention table says the record is then cleared by daily maintenance.<\/p>\n<\/details>\n\n\n\n No. The Your Data Rights page says purchases made in the app are not linked to your email address, so a request made on that page by email address cannot find them, and it names writing to admin@portraitor.ai with the Pass code or the order ID on Apple’s receipt as the route for those records.<\/p>\n<\/details>\n\n\n\n The Your Data Rights page says Portraitor holds nothing about a person who has never used the Service: their name and contact details were replaced with placeholders on the uploader’s own device before anything was transmitted, Portraitor never received them, and the portrait was delivered to that person alone, so there is nothing for it to find, copy or erase. The page adds that anyone with a concern about how the Service was used may write to the address on it. The same question across five services is covered in the page on uploading a chat someone else is in<\/a>.<\/p>\n<\/details>\n\n\n\n There is no password to check, so the check is a lookup at the payment processor and a link only the mailbox receives.<\/p>\n","protected":false},"excerpt":{"rendered":" Portraitor runs no accounts and keeps no copy of your email address, so there is no password to check and nothing to match. What its data rights page does instead.<\/p>\n","protected":false},"author":6,"featured_media":475,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"pp_title_highlight":"","pp_meta_title":"","pp_meta_description":"Can someone else request my data from a chat analyser? Portraitor holds no account and no address, so a lookup at Stripe stands in for a login.","pp_sidebar_cta":"{\"variant\": \"light\", \"heading\": \"No account, no stored address\", \"bodyHtml\": \"Portraitor operates no accounts and keeps no copy of your email address. A data request is located through its payment processor instead.\", \"label\": \"See how Portraitor works →\"}","pp_sources":"[{\"html\": \"Portraitor, Your Data Rights<\/em>, version 1.3, 30 September 2026.\", \"href\": \"https:\/\/portraitor.ai\/gdpr\"}, {\"html\": \"Portraitor, Privacy Policy<\/em>, version 1.3, 30 September 2026.\", \"href\": \"https:\/\/portraitor.ai\/privacy\"}]","pp_endcard":"{\"h3\": \"Read the data rights page first\", \"body\": \"It names the controller, the lookup that finds your records, and the two link expiry times. The whole mechanism is published.\", \"label\": \"See how Portraitor works →\"}","pp_howto":"","footnotes":""},"categories":[3],"tags":[],"class_list":["post-476","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-understanding-yourself"],"_links":{"self":[{"href":"https:\/\/portraitor.ai\/blog\/wp-json\/wp\/v2\/posts\/476","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/portraitor.ai\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/portraitor.ai\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/portraitor.ai\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/portraitor.ai\/blog\/wp-json\/wp\/v2\/comments?post=476"}],"version-history":[{"count":1,"href":"https:\/\/portraitor.ai\/blog\/wp-json\/wp\/v2\/posts\/476\/revisions"}],"predecessor-version":[{"id":512,"href":"https:\/\/portraitor.ai\/blog\/wp-json\/wp\/v2\/posts\/476\/revisions\/512"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/portraitor.ai\/blog\/wp-json\/wp\/v2\/media\/475"}],"wp:attachment":[{"href":"https:\/\/portraitor.ai\/blog\/wp-json\/wp\/v2\/media?parent=476"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/portraitor.ai\/blog\/wp-json\/wp\/v2\/categories?post=476"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/portraitor.ai\/blog\/wp-json\/wp\/v2\/tags?post=476"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What your address does, and what it does not become<\/h2>\n\n\n\n
The link is clicked by you, not by your mail server<\/h2>\n\n\n\n
An erasure runs on a shorter clock and a typed word<\/h2>\n\n\n\n
The purchase an email address cannot reach<\/h2>\n\n\n\n
Control of the mailbox is the whole of the proof<\/h2>\n\n\n\n
Frequently asked questions<\/h2>\n\n\n\n
Can someone else request my data from Portraitor?<\/summary>\n
How does Portraitor find my records if it does not hold my email address?<\/summary>\n
Does making a request mean Portraitor now has my email address?<\/summary>\n
Can a request find a purchase made in the iPhone app?<\/summary>\n
What if I appear in a conversation someone else uploaded?<\/summary>\n