Auksionline

Privacy policy

The Auksionline app and website provide a service for publishing listings and participating in auctions. Contact for personal data questions: support@auksionline.com.

Updated: October 15, 2026.

Data we process

Why the data is needed

For mobile notifications, the service stores a technical device token and its association with an account. On iPhone, delivery uses Apple Push Notification service (APNs); on Android, it uses Google Firebase Cloud Messaging (FCM). The provider receives the token, generic notification text and technical identifiers for the notification, account and listing. The SDK may process technical installation and device identifiers. Passwords, buyer contact details and the account database are not sent to these providers for delivery. The app does not use Firebase Authentication, Analytics, Database or Storage: accounts, listings and photos are served by our own infrastructure. Signing out revokes the association; if offline, the request is retried when connectivity returns. Account deletion also removes tokens. Associations expire with the session; expired records and the delivery queue are cleaned up within seven days. Permission can be disabled in phone settings.

Data is used for account access, publishing listings, running auctions, connecting sellers and buyers, account recovery and service protection. Passwords are stored as hashes, not plain text.

What other users can see

Listings, their photos, the city, seller name and bid information are available in the service interface. Buyer details, including email and phone number, may be shown to the seller when processing a purchase or auction result. Do not include confidential data in listing descriptions or photos.

Storage and external services

The database and newly uploaded photos are stored on the computer serving Auksionline. Previously added photos may load from external Cloudinary storage. Password recovery may use an email service. Network requests to external resources transmit technical connection data to their operators.

An authorization token is stored on the device to keep you signed in. Signing out removes the saved token. Photos may be analyzed to generate product search tags.

Personal blocks are stored to hide selected sellers and restrict new interactions between users. This is not a platform-wide access ban and does not cancel existing bids or transactions. The list is available in settings and users can unblock others. Deleting either associated account removes the block record.

Deletion and retention

The Delete account button under Settings → Security deletes the account, listings and associated personal records from the live database. Photos on our server are deleted through a cleanup queue; processing is retried after technical errors.

When payments are connected, payment records are stored separately from the profile for five years from the payment date, then automatically deleted. Records subject to a specific lawful preservation requirement are excluded until that requirement is lifted. Bank card details are not stored in this archive. Cleaning the live database does not immediately delete backups, support emails or old files in external storage. Contact support about this data.

Your requests

For data corrections, access questions or deletion, write to support@auksionline.com. Do not send your password.

Automatic deletion of completed listings

Completed and cancelled listings are automatically cleaned up one calendar month after the auction end or cancellation time. For sold listings, the period starts when the sale is confirmed. Deadlines use Baku time and are checked at least once an hour. The listing, bids, purchase requests, favorite links, related notifications, moderation records and image-tagging records are removed from the live database. Local photos not used by other listings or profiles are removed through a retryable deletion queue. Active listings and separately republished listings are not deleted. The account remains. Payment records are detached from the deleted listing and kept under the existing five-year rule. Backups and separate support correspondence follow their own retention rules.