What this holds about a person¶

3 tables, 7 columns about a person, 2 things held outside a column, 1 kind of data subject, 0 destinations. Some of it is kept indefinitely, and every one of those says why below.

What it holds¶

`gift_cards_card`¶

Who a row is about: the shopper, by voucher_id matched into voucher.voucher_id, which names them at to_email.

What makes a row go away: never — Nothing on a clock removes an expiry date, and nothing removes one on an event either. The date is what the merchant owes the holder until it passes, and a row deleted for tidiness is a card that silently becomes redeemable forever — a change to the store's liability rather than a removal of anything about a person. Where core itself deletes the voucher, the row is left as an orphan holding a date and an id that resolves to nothing, unreachable by any request because the join such a request arrives on no longer resolves; saying that plainly is more honest than a sweep claiming to erase something already unlinked.

Column	What it is	Why it exists	What an erasure does
`voucher_id`	`refers`	Which of core's vouchers this date belongs to, and the whole of how a person is reached from this table. It is the primary key rather than a plain column, which is what makes a card impossible to stamp twice.	`retain`
`expires_on`	`about`	When this person's card stops being redeemable, or NULL where the merchant decided it never does. It is the only fact this extension stores about a card.	`retain`
`date_added`	`about`	When the date was stamped, which is the moment the card's purchasing order first reached a complete status. A merchant asked why a card expires when it does needs the day the clock started.	`retain`

`gift_cards_attempt`¶

Who a row is about: the shopper, by ip on this table.

What makes a row go away: swept — The prune rides on the next write rather than on a schedule — this extension ships no cron row of its own — and deletes every row older than the window anything is counted over. Inside the window the rows are kept, because a rate limit that forgets is not one. The remove-everything screen empties the table outright, which is the one path by which anything this extension holds leaves the store on a merchant's say-so: a request about one person cannot reach these rows, because an address is not matchable from an email and guessing which attempts were somebody's would be worse than saying so.

How long: PersonalData::ATTEMPT_DAYS, which is 30.

Column	What it is	Why it exists	What an erasure does
`ip`	`identifies`	The address the lookup came from, counted so that a public page challenging a code and an email address cannot be used to walk the code space. It is here because the email cannot serve: on this page the email is the attacker's second variable rather than a handle on anybody.	`delete`
`voucher_id`	`refers`	The other thing an attempt is counted against, where the code resolved — `0` where it did not — so that one card cannot be hammered from many addresses. It is the only thing a row is allowed to remember about the code that was presented.	`delete`
`outcome`	`about`	Whether the attempt was answered or refused. A merchant reading the throttle needs to know whether they are looking at somebody guessing or at one person mistyping their own address.	`delete`
`date_added`	`about`	When the attempt was made. It is both the window the count is taken over and the clock the opportunistic prune reads, so a row outlives its purpose by minutes.	`delete`

What it holds that is not in a column¶

A file, a cookie and a key in the session are exactly where an erasure written as row deletion reaches nothing, and no schema can be diffed to find one. Each is listed here with what keys it to a person, why it is there, and what removes it.

A file on disk. kyvero.log in the store's own DIR_LOGS, the one diagnostic file every extension in this repository shares, capped at 1 MiB and trimmed oldest-first.

Nothing keys this to a person — every message is put through the diary's redaction rule before a byte is written, which is what makes the file survivable where OpenCart puts its own error log.

Why it is here: A merchant reporting a failure needs one place to look, and a support conversation without it is guesswork on both sides.

What an erasure does: delete.

A file on disk. Not a file on disk at all: php://temp, the in-memory buffer the outstanding-cards CSV is assembled in before it is read back into the response. It is opened, written a line at a time and closed inside one request, and PHP spills it to a temporary file only if it outgrows its memory budget. What goes into it is, per card, its voucher id, its order id, two amounts, the currency, its expiry date and which figures it counts toward. No card code, no name, no address and nothing a shopper typed.

Nothing keys this to a person — the buffer holds ids, amounts and dates per card and is keyed to the export the administrator asked for, which does not outlive the request that asked for it.

Why it is here: The liability list is read beside the books in a spreadsheet, and the incumbents this extension is measured against ship an export of it.

What an erasure does: retain.

What it deliberately does not hold¶

Each of these is a column that could have been stored and was not, with the reason it was not. They are decisions rather than omissions.

Neither table holds a gift-card code, and neither holds a hash of one.

A code is a live bearer credential: whoever has it can spend the card. A hash of one is the credential too, because the code space a store issues from is small enough to walk offline — storing it would turn a database that leaks into every card in the store being spent. An attempt on a code that resolved is remembered as the voucher_id it resolved to, and an attempt on one that did not is remembered as 0, which is the whole of what a throttle needs.

The email address a balance lookup is challenged against is compared and forgotten. It is never written to the attempt table.

Keeping it would build, out of a public page nobody has to sign in to, a list of addresses somebody typed beside a gift card — which is a more sensitive holding than the one the page exists to protect. The throttle counts the address the request came from and the card the code resolved to, and neither needs the email.

The card table holds no name, no recipient address, no amount and no history. It holds a date.

All of those are already on core's own voucher rows, and a copy is a copy that can drift — a merchant correcting a recipient's address in core would leave this extension quietly showing the old one. Balances and the liability figure are derived on every read for the same reason.

Where it goes¶

Nowhere. Nothing Gift Cards holds about a person leaves your store.

What the standard asks, and what this extension answers¶

Kept indefinitely, on purpose. Nothing below is removed by a clock. Each one says why, which is the part a merchant relying on it has to be able to state:

gift_cards_card — Nothing on a clock removes an expiry date, and nothing removes one on an event either. The date is what the merchant owes the holder until it passes, and a row deleted for tidiness is a card that silently becomes redeemable forever — a change to the store's liability rather than a removal of anything about a person. Where core itself deletes the voucher, the row is left as an orphan holding a date and an id that resolves to nothing, unreachable by any request because the join such a request arrives on no longer resolves; saying that plainly is more honest than a sweep claiming to erase something already unlinked.

What reaches them instead is the remove-everything screen, which is a request you act on rather than a clock that runs.

Each row below is keyed by the sub-paragraph of the General Data Protection Regulation it comes from, so that you can read the source and disagree with us. What each state means is on the data-protection boundary, once, rather than reworded here. declared is not a pass: it says what the thing is, not that the thing is fine.

Article	What this extension supplies toward it	This extension
`5(1)(c)`	Every column this extension can put in a store is written down with the one sentence saying why it is there, and a column that is not fails the build — so what a store keeps is what somebody decided to keep rather than what accumulated. Beside it, in the same file and the extension's own voice, is what it deliberately does not keep, and why.	checked, 11 — every column this extension's schema can put in a store
`30(1)(c)`	What this extension holds about a person is published column by column — what the column is, whether it names somebody or points at them, and why it exists — so the record a merchant has to keep can be copied off a page rather than reconstructed out of the database.	declared
`7(1)`	Where anything this extension does rests on somebody having agreed to it, the declaration names the wording they agreed to and where the proof of it is recorded — and where nothing rests on consent it says so, because we did not need any is an answer and a blank is not.	declared
`7(3)`	A declared consent carries the path by which it is withdrawn, or the build fails — because withdrawing has to be no harder than giving, and a consent whose withdrawal path nobody wrote down is one a merchant discovers they cannot honour on the day somebody asks.	checked, 0 — every consent declared anywhere in it
`15(1)`	Every table holding anything about a person answers who that person is and how a request reaches them — a column on the table itself, the path through a table this extension does not own, or the plain statement that nothing on it keys a row to anybody — so that a request either has somewhere to arrive or is told outright that there is nowhere, rather than a screen having to guess which rows are whose.	checked, 2 — every table holding anything about a person
`16(1)`	A column holding a frozen copy of something the store holds elsewhere names the column it was copied from, so that correcting the original is an instruction a merchant can follow rather than a shrug about why the two disagree.	declared
`21(3)`	The row that records somebody saying stop names the subject it is keyed on and the verdict an erasure gives it, so that a live instruction to stop mailing survives the request that was meant to enforce it rather than being deleted by it.	declared
`25(2)`	A column that is only collected when a merchant turns something on names the setting that decides it, and the shipped value is read off the configuration declaration rather than restated here — so what a store collects out of the box is a fact on a page instead of something read out of a controller.	declared
`5(1)(e)`	Every table this extension can put in a store answers what makes a row holding a person go away — one of six verdicts, and a table that answers 'never' says why in the same breath or fails the build — so a store keeping something for ever is keeping it on purpose.	checked, 2 — every table an answer is owed for
`15(1)(d)`	The period each table is kept for is published beside what it holds, as the mechanism and — where there is one — the number or the setting it is read from, so that a merchant answering somebody who asks how long their data will be stored is copying an answer rather than composing one.	declared
`17(3)`	Everything an erasure deliberately keeps is published with the reason it was kept, and a kept column with no reason beside it fails the build — because the exemption a merchant relies on is one they have to be able to state, and the screen states it to them at the moment they press the button.	declared
`17(1)`	A merchant erases one named person from a screen, and what happens is what the declaration said would happen: the rows and the files an erasure takes are gone, what it keeps is still there, the person standing beside them is untouched, and pressing it a second time is safe. Asserted by running it on a real store — the only place in this standard where erasure behaviour is ever observed, and the only place a file is.	Asserted on a real store by `make smoke`, and deliberately not here — this page is generated by `make check`, which is green with no store at all, so a verdict rendered from it would rest on nothing.
`30(1)(f)`	The envisaged time limits for erasure are published per table rather than per extension, so the line a merchant copies into their own record says which data it is about instead of averaging seven answers into one.	declared
`15(1)(c)`	Every destination this extension's holdings leave it for is published by name, with which of those holdings reach it — so answering somebody who asks who their data was disclosed to is reading a page rather than reading the source.	declared
`20(2)`	This extension transmits nothing directly to another controller, and says so out loud rather than leaving it unmentioned: the destinations that exist are the published list, an export is a file the merchant receives and hands on themselves, and there is no path by which we send one controller's data to another on their behalf.	declared
`30(1)(d)`	Every destination is written down with who chose it, and a destination this extension chose itself that anything personal reaches fails the build — not by default, not behind a setting, not with a warning, because a store owner cannot consent on behalf of the people in the file.	checked, 0 — every destination anything leaves it for
`15(3)`	The screen that says what is held about one named person also hands that statement over: one button produces a file carrying every holding it just listed — what is held, why it is there and what removes it — so answering somebody who asked is sending what the screen showed rather than retyping it into an email. What the file does not carry is the values themselves, which stay in the store; `20(1)` below says what that costs. Every extension ships that screen and that button byte for byte, so the file is the same file whichever extension a merchant happened to open.	checked, 7 — every holding the file carries
`20(1)`	That file is JSON — structured, commonly used and machine-readable — rather than a screen printed to paper, so whoever asked for it can read it with something other than their eyes. What it carries is the inventory and not the contents: every holding this extension has about that person, folded out of the declaration without a table being opened, which is why two people's files differ in the address at the top and nowhere else. Portability is the right to receive the data itself, and this is not that — the values are in the merchant's own database, and what this supplies is a machine-readable statement of where each one is and what removes it. The row is `declared` for that reason and not `machine`: what the rule behind it decides is that every extension ships one export byte for byte, which says what the file is and not that the file is what this article asks for.	declared
`30(1)(g)`	The technical and organisational measures are the security baseline's subject, published on its own page with its own rows and its own scanners, and this page links to it rather than restating any of it. What is asserted here is the seam between them: every file this extension writes is declared in both places and cross-checked both ways, so the two descriptions cannot drift apart.	declared
`KYV-D1`	Everything this extension holds about a person can be removed on purpose, from a screen, without uninstalling it — and the screen shows what will go before it goes. Uninstalling keeps it all, because an OpenCart upgrade is an uninstall followed by an install and an extension that dropped its tables on the way out would destroy a store's data on every routine update. A holding every one of whose columns is kept for ever, with nothing anywhere able to remove any of it, fails the build.	checked, 4 — every holding the remove-everything screen reaches

What is left over¶

No column Gift Cards holds is declared a frozen copy of anything the store keeps elsewhere, so this page names no second place a correction has to be made first. What each column is, and where its contents came from, is in its own row above.

Removing all of it is one button, on Gift Cards's own settings screen at Admin > Extensions > Extensions > Modules > Gift Cards. It prints what will go — every table, every file, every key, with a count beside each line and the reason beside the ones it keeps — and nothing goes until you press the second button. It cannot be undone: no soft delete, no recycle bin, no undo, because a recycle bin for personal data is personal data that is still there. Uninstalling does not do it, deliberately: an OpenCart upgrade is an uninstall followed by an install, so an extension that dropped its tables on the way out would destroy your data every time you updated it. Your settings, your configuration and whatever the extension remembers about itself are not touched.

What the law asks of you — you are the controller, and installing an extension is not a compliance process — is on the data-protection boundary, which is also where the words above are defined and where it says why there is no badge. What OpenCart's own erasure feature does underneath all of this, and the things about it worth knowing first, is on what core's own GDPR feature does.