LastFolk — Security Incident Response and Data Retention & Loss Prevention Policies
Last updated: November 18, 2026
These two policies put in writing what LastFolk already promises in its Data Processing Agreement (DPA; §5, §8 and Annexes I–II) and its Privacy Policy (§3 and §8). Where the DPA or the Privacy Policy already states a rule, these policies repeat it and do not change it.
Policy A — Security Incident Response
When LastFolk becomes aware of a security incident that may affect personal data, it contains it first, then tells every affected merchant within 48 hours, as DPA §8 requires.
A1. Scope
This policy covers any event that does or may compromise the confidentiality, integrity or availability of personal data that LastFolk processes. That includes merchants' end customers, fleet members (drivers), merchant staff and website visitors, in every system LastFolk runs: the operations hub and its database (Supabase), the edge functions, the merchant panels for Wix and Shopify, the LastFolk Driver app, the public website, and the accounts used to run them (GitHub, Lovable, Cloudflare, Supabase, Shopify Partners, Wix Developers, Google).
A personal data breach is an incident that has in fact led to personal data being destroyed, lost, altered, disclosed or accessed without authorization, as defined in the EU GDPR.
A2. Roles
| Role | Who | Contact |
|---|---|---|
| Incident owner and decision-maker | Jesús Castillo, Founder & CEO, Pictorica Devs LLC (LastFolk) | contact@lastfolk.com |
| Intake for reports from merchants, customers and researchers | LastFolk support | support@lastfolk.com, contact@lastfolk.com |
| Technical investigation and fixes | The incident owner, with the engineering tools LastFolk uses (including AI coding assistants under his supervision) | — |
The incident owner may bring in outside help. Any outside party works under confidentiality.
A3. Detection and reporting
Incidents can come from automated alerts (database and function logs, scheduled health checks, webhook verification, error monitoring), from a subprocessor's notice, or from a report by a merchant, an end customer, a fleet member or a security researcher. Anyone who suspects an incident reports it at once to support@lastfolk.com or contact@lastfolk.com. LastFolk acknowledges a report within 1 business day.
A4. Severity
| Level | Meaning | Example |
|---|---|---|
| High | Personal data exposed or likely exposed, or a production credential leaked | A database key published, a merchant's customers' addresses readable by another merchant |
| Medium | A weakness that could expose personal data, with no evidence it was used | A misconfigured access rule found in review |
| Low | No personal data at risk | A brief outage of a non-critical page |
A5. Response steps
1. Contain. Revoke or rotate any affected credential (API keys, webhook secrets, OAuth tokens), disable the affected function or integration, and block the access path.
2. Assess. Establish what data, which merchants and how many people are affected, how it happened, and whether it is a personal data breach. Preserve logs and evidence.
3. Notify merchants. Where a merchant's personal data is affected, notify that merchant without undue delay and in any event within 48 hours of becoming aware, with the information reasonably available, so the merchant can meet its own deadlines (including the 72-hour authority deadline under the EU/UK GDPR). Notify again as more is learned.
4. Notify others where LastFolk is the controller. For data LastFolk controls (its own merchant accounts, fleet member accounts, website visitors), notify the competent authority and the affected people where the law of their country requires it and within its deadline. Examples: within 72 hours under the EU/UK GDPR; as Chile's Law 21,719 requires from 1 December 2026.
5. Notify platforms where required. Tell Shopify, Wix, Uber or another platform where its terms require it, for example when the incident involves data received through that platform's API.
6. Fix and recover. Correct the root cause, restore any lost or altered data from backups (Policy B), and confirm the fix.
7. Review. Within 14 days of closing a High or Medium incident, write down what happened and what changes so it does not recur.
A6. Review of this policy
The incident owner reviews this policy at least once a year and after every High incident.
Policy B — Data Retention and Loss Prevention
LastFolk keeps personal data only as long as each purpose needs it, deletes it on fixed schedules, and protects it against loss and leaks with the measures below.
B1. Retention schedule
The periods below are the ones already published in the Privacy Policy and in DPA Annex I. Anything not listed is kept for the term of the merchant's agreement plus any period the law requires, then deleted or anonymized.
| Data | Kept for | Source |
|---|---|---|
| Delivery address of a checkout quote that did not become an order | 30 days, then replaced by «[redacted]» (the quoted price and pickup point are kept) | Privacy §3.2 |
| Delivery chat messages | 30 days after they are written | Privacy §3.6, DPA Annex I |
| Hash of the network address a chat message came from | 2 days at most | Privacy §3.6 |
| Driver position points | 72 hours | Privacy §3.7, DPA Annex I |
| Photo, voice note or video added when a driver skips a stop | 90 days after the route closes | Privacy §3.7 |
| Details of a driver removed from a merchant's fleet | 90 days after removal; at once if the driver deletes the account | Privacy §3.7, DPA §7.3 and Annex I |
| Revoked or failing notification token | 90 days | Privacy §3.7 |
| Form at lastfolk.com/drive | 12 months | Privacy §3.8 |
| Founding Merchants applications | 31 March 2027 if not selected; videos deleted that day in every case | Privacy §3.9 |
| Advertising click identifier attached to a record | 90 days from capture | Privacy, cookies section |
| Wix checkout fee quotes | 1 day | Scheduled purge |
| Audit and sync logs | 12 months | Scheduled purge |
| Database backups | About 14 days | Hosting provider |
| A merchant's personal data after the agreement ends | Deleted or returned at the merchant's choice; otherwise deleted or anonymized within 90 days | DPA §9 |
| End-customer and shop data on Shopify customers/redact or shop/redact requests | Deleted when the request arrives, except data the merchant still needs while the app remains installed | Shopify mandatory webhooks |
B2. How deletion happens
Scheduled database jobs delete data when its period ends. Deletion requests about data LastFolk controls are answered within 30 calendar days (Privacy §10). When LastFolk receives a request about data it processes on behalf of a merchant, it acknowledges the request, directs the person to that merchant and notifies the merchant; it does not otherwise respond unless the law requires it (DPA §7.1). Shopify's mandatory privacy webhooks are verified by HMAC before any data is read or deleted. If a deletion does not finish, the webhook returns an error so Shopify retries, instead of reporting success.
B3. Loss prevention
- Encryption. Personal data is encrypted in transit (TLS/HTTPS on every endpoint).
- Backups and recovery. The production database is backed up once a day by the hosting provider, and each backup is kept for about 14 days. A restore is the recovery path for lost or altered data (Policy A, step 6). Data deleted under B1 can remain in a backup until that backup expires, at most about 14 days later.
- Separation of test and production. Each merchant record carries an operating environment (production or sandbox). Development runs on a separate Shopify app, and test and production merchants use separate courier credentials. On every platform, a production merchant cannot quote or create a delivery with courier test credentials; on Shopify, it cannot connect them at all.
- Least data. The apps request only the platform permissions they need. Full card numbers are never stored; the payment processor holds them. End-customer email is used only for delivery notices, never for marketing.
- Masking. Phone numbers, email addresses and verification codes typed into the driver chat are hidden. When an AI service reads a delivery file's columns, the personal data in the sample rows is masked first.
- Secrets. API keys and secrets live in the hosting provider's secret store or in the database, never in the code repository or in the browser.
B4. Access control
- Who has access. Access to production personal data is limited to the incident owner. Any other person gets only the access their task needs, for as long as it lasts, and loses it when it ends.
- Isolation. Database access rules keep each merchant's data separate from every other merchant's.
- Logs. Sensitive actions on accounts and integrations (connections, deletions, webhook registrations) are written to an audit log. Routine reads of personal data are not logged individually.
B5. Review
The retention schedule is reviewed whenever a new kind of personal data is added, and at least once a year.
