A traveler used a public kiosk to print a boarding document and walked away after the page appeared. The next user could still see the email address, travel details, and a list of recently opened files because the session had not fully closed.

Public kiosks are increasingly used for transport, government services, health registration, libraries, and event check-in. They provide access for people who lack a personal device, but they also create a predictable privacy risk when one user’s information remains visible to the next.

Every kiosk should clear browsing history, downloaded files, form entries, clipboard contents, and authentication tokens after logout or a short period of inactivity. Restarting the device should restore a clean state rather than reopening the previous session.

The screen needs a visible countdown before automatic clearing. A user who is still working should be able to extend the session, while someone who has left should not keep the system occupied indefinitely. Sensitive tasks may require even shorter time limits.

Designers should avoid saving passwords or offering persistent sign-in. Printing and scanning functions must remove temporary copies after the task finishes. Staff should know how to reset a kiosk immediately when a user reports that private information remains.

Public access should not require people to understand hidden browser settings. The institution operating the kiosk controls the environment and should provide the safer default. Automatic clearing protects users who are rushed, unfamiliar with the system, or unaware that closing a window is not the same as ending a session.

Periodic privacy tests should confirm that a session truly disappears rather than only closing the visible window.

Design teams should test the system with people using older devices, shared accounts, slow connections, and accessibility tools. A feature that works only under ideal conditions may fail precisely when a user most needs clarity or control. Publishing support information and reviewing complaints can reveal patterns that technical testing alone misses.

C. Armenta

Two neighbors ordered the same meal from the same restaurant at nearly the same time. Their delivery fees were different, and one received a discount that the other could not see. Neither app screen explained whether the difference came from distance, demand, account history, or a personalized promotion.

Dynamic pricing can help platforms respond to traffic, weather, driver availability, and busy periods. Personalization becomes more troubling when customers cannot tell whether their own data influences what they are charged.

Apps should identify which parts of the total are fixed and which may vary. A short explanation can state whether the price reflects distance, current demand, membership status, targeted discounts, or previous use. Customers do not need access to every line of an algorithm, but they should understand the basic reason for the difference.

The final cost should remain visible before payment, including service fees, small-order charges, taxes, and tips. A low headline price is misleading when required charges appear only at the final step. Promotions should state whether they are available to all users or selected accounts.

Regulators and researchers also need access to meaningful data so they can test whether personalized systems disadvantage certain neighborhoods or groups. Platforms should preserve privacy while allowing independent review of broad patterns.

Customers can accept that prices change when the reason is clear. What damages trust is the feeling that two people may be treated differently for reasons they cannot see or challenge. Transparent labels would not eliminate flexible pricing, but they would make the transaction easier to evaluate. A delivery service should compete on convenience and value, not on how effectively it hides the rules used to calculate the bill.

Customers should also be able to compare the personalized total with a standard local rate when one exists.

A receipt should preserve the explanation so customers can review the pricing after the order is complete.

C. Petrovic