Winesky
@winesky.app
The Winesky backend will keep a pair of record IDs and encryption keys, which the user can request at any point.
This also allows for an update process where a user can decrypt all their records if they want to keep them in clear text in the future.
#ATDev
This also allows for an update process where a user can decrypt all their records if they want to keep them in clear text in the future.
#ATDev
December 13, 2025 at 9:03 AM
The Winesky backend will keep a pair of record IDs and encryption keys, which the user can request at any point.
This also allows for an update process where a user can decrypt all their records if they want to keep them in clear text in the future.
#ATDev
This also allows for an update process where a user can decrypt all their records if they want to keep them in clear text in the future.
#ATDev
Slightly trickier to decide how to handle context for sommelier recommendations. The user should be in control of their information, but we also want to provide a measure of privacy.
For now the recommendation context will be AES-256-GCM encrypted, with one-time keys per record.
#ATDev
For now the recommendation context will be AES-256-GCM encrypted, with one-time keys per record.
#ATDev
December 13, 2025 at 9:03 AM
Slightly trickier to decide how to handle context for sommelier recommendations. The user should be in control of their information, but we also want to provide a measure of privacy.
For now the recommendation context will be AES-256-GCM encrypted, with one-time keys per record.
#ATDev
For now the recommendation context will be AES-256-GCM encrypted, with one-time keys per record.
#ATDev