| Deletion markers (an identification record for integrity checks for each photo and video) | Kept with no set period | The original and converted image files are deleted, and once account deletion completes each photo's capture time, file size, integrity hash, and the hash made from the device's photo identifier are deleted too, so only the identification record needed to confirm that no undeleted file remains in storage is kept — internal identifiers and the internal number of the account that uploaded it, processing status, whether it is a photo or a video and its file format, version order, processing times, and its location in storage (a file path made from internal numbers). It is tied together only by internal numbers, with no sign-in link. For photos added to shared albums, the record of which album each was added to and when (the album number, the internal number of the account that added it, and the time — the album link record) also remains. Link records in albums you created are deleted along with those albums, but link records in other people's shared albums are currently not deleted by the deletion process and remain. There is currently no process that deletes these records automatically. |
|---|
| Account deletion records | Kept with no set period | The account's internal number, account type and status, the times it was created and deleted, the sign-up type (whether the account started as a guest or signed up directly with a social login) and the week a social account was first linked (the week starting Monday 00:00 Korea time — no date or time is kept, and accounts that stayed guests have none), the deletion request number, the start and end of the grace period, and the storage in use when deletion was requested. This is the record of the deletion and is also used for weekly totals of sign-ups and social account links and of activation by sign-up week; once the social login link is deleted, it is tied together only by internal numbers. |
|---|
| Re-link block data | 30 days after deletion completes | A cryptographic hash of the social account identifier you signed in with, the provider's name, the deletion request number, and the times deletion was completed and the block expires. For 30 days it prevents that social account from being linked to another account. It does not prevent creating a new account with the same social account; in that case we tell you that it is a new account in which the previous photos and data are not restored. This record is tied to the account deletion record by the deletion request number, so if you sign in again with the same social account we can use this record to tell that it is the social account of the deleted earlier account. After 30 days a cleanup job that runs every 15 minutes deletes this record, and the tie to the account deletion record through this record goes with it. Ties through service operation logs are set out in the “Service operation logs” row below. |
|---|
| Service usage records | 90 days | Time and type of each request; the actor and target exist only as cryptographic hashes. |
|---|
| Service operation logs | The period set by the retention policy of the processor (Supabase) | The time of access, the IP address and the approximate location and network operator estimated from it, device and browser information, the address requested, account identifiers (such as the account's internal number and the sign-in handle), sign-in records, and part of the values being written to the database when a database error occurred on the server. They are recorded automatically for each request by the platform of the processor entrusted with running our servers, so they cannot be deleted together with your account; they are deleted once that period has passed. Because the sign-in handle is the same value for the same social account, during that period we can, by looking up the operation logs, connect a deleted account with an account newly created with the same social account. |
|---|
| Database backups | Up to 7 days | Database backups made once a day for disaster recovery still contain deleted data for up to 7 days, and it disappears as the backups are replaced. |
|---|
| Error diagnostics (Firebase Crashlytics) | 90 days | Sent from the app directly to Google, never through our servers. |
|---|
| Usage statistics (Google Analytics for Firebase) | Events 2 months · user-level identifiers 14 months | Sent from the app directly to Google. The retention period for user-level identifiers resets while the app is in use. |
|---|
| Usage statistics (Operator's server) | Individual events 90 days · per-user aggregates 14 months | Usage statistics the app sent to the Operator's server exist only with the account identifier irreversibly transformed; once account deletion completes, that value is replaced with a random value that belongs to no one, and they remain, unlinked from the account, until this period has passed and they are deleted. Records used to count resent statistics only once are not linked to any account and are deleted 37 days after the day they were received. |
|---|
| Ad performance measurement data (Airbridge) | For the term of the contract with the processor (AB180) (at most 5 years from processing) | Device and network information the app sent directly to Airbridge when it was installed or opened or when you signed up, in the app versions that include this feature and only if you consented to ad performance measurement. It does not pass through our servers and is not sent linked to your account, so it is not deleted with account deletion; it is all deleted once 30 days have passed after the contract ends. However, from the app versions that include it, when you delete your account we ask Airbridge to delete the data of each device used with your account that has kept its Airbridge random identifier (each device sends a deletion request that is not linked to your account — devices that have not kept the identifier do not make the request). From the iOS app versions that include it, it is sent only if you allowed tracking, and the advertising identifier (IDFA) is then sent as well. From the Android app versions that include it, this also includes the install record sent once, regardless of consent, when a newly installed app is first opened. |
|---|
| Activation totals of deleted accounts | Kept with no set period | When account deletion completes, the account's sign-up week and sign-up type ("unknown" if it cannot be told), and the number of days it took within 28 days of signing up to first create a shared album and to first join one through an invitation, are added without the account's internal number, only as a count of accounts with the same values. This keeps activation totals by sign-up week from shrinking when accounts are deleted. However, if only one deleted account has a given set of values, the number of days that account took can be found by matching it against the account deletion record. |
|---|