Privacy policy

1. Who provides DigiBytes

DigiBytes is provided by the independent developer operating the DigiBytes application and this website. For support, privacy questions, or data requests, contact chaos.aca@gmail.com.

2. Data stored on your device

The desktop app stores the information you enter or import: product names, categories, supplier costs, sale prices, stock, descriptions, purchase guides, sales, customer notes, account balances, expenses, fees, transfers, and settings. These records are stored in a local SQLite database. CSV exports and backups are saved where you choose.

Financial balances are manual bookkeeping entries. DigiBytes does not request passwords, API keys, or session cookies for Binance, Bybit, PayPal, RedotPay, or CCP. The developer does not automatically receive your local database.

3. Optional Google access: what and why

When you choose to connect Google, the desktop app opens Google's authorization page in your web browser. Google handles your account credentials. The app receives an authorization code and exchanges it for access and refresh tokens, which allow it to make Google API requests on your behalf.

DigiBytes requests https://www.googleapis.com/auth/drive.file to create and update the spreadsheet files used with the app. The spreadsheet ID, source timestamps, sync settings, and authorization tokens are stored locally. This permission does not grant general access to every file in your Drive, Gmail, or Contacts.

Google access is used solely to provide the spreadsheet report you request. The app reads report-tab metadata and writes the report's contents. It does not import other Drive documents or read unrelated spreadsheets to build a profile about you.

4. Information sent to Google

When you select Sync, or enable automatic sync while the app is open, the desktop app sends report data directly to Google's APIs. The report includes product and inventory details, prices, descriptions, purchase guides, account names and balances, DZD estimates and their rate metadata, and transaction dates, types, quantities, amounts, costs, fees, account or product references, and notes.

Customer information or other personal information written in your notes is included in the report. Do not place passwords, account cookies, license secrets, or information you do not want copied to Google in report fields.

The report is stored in the Google account you authorize. Its visibility also depends on that spreadsheet's Google sharing settings. Google's processing is governed by Google's Privacy Policy. A sync replaces the app-managed report tabs with the current local report; edits made in those tabs are not imported into DigiBytes.

5. Use, sharing, and Limited Use

Google user data is used to provide and maintain the user-requested Sheets integration. DigiBytes does not sell Google user data, use it for advertising, share it with data brokers, or use it to train generalized AI or machine-learning models. The standard desktop workflow sends the report from your device to Google; it does not send Google tokens or report contents to the developer's website or a developer-operated report server.

DigiBytes' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

If you voluntarily email support, the developer receives the information and attachments you send and uses them to respond to that request. Support messages are not a way to authorize account access. Do not send passwords, session cookies, or authorization tokens.

6. Exchange-rate requests

The app can request a public USDT/DZD reference quote from Square Live DZ at startup, periodically while open, or when you refresh. These requests do not include your wallet balances, products, transaction history, or Google tokens. Like other network requests, they disclose connection metadata such as your IP address to the receiving service. The quote and timestamps are cached locally.

7. Storage, retention, and deletion

Local store records remain on your device until you remove the database or copies you created. Disconnecting Google removes the locally stored Google token and disables automatic sync; it does not delete your inventory database, exported files, or spreadsheet. You can revoke DigiBytes' access in your Google Account connections.

To remove a Google report, delete the spreadsheet in Google Drive and manage its trash according to Google's controls. To remove local app data, close DigiBytes and delete its data directory, normally ~/.local/share/digibytes or $XDG_DATA_HOME/digibytes. Backups and exports stored elsewhere must be removed separately. The developer cannot delete files stored only on your device or in your Google account.

For support correspondence you have sent to the developer, you may request deletion by email. Messages are retained as needed to resolve the request, maintain relevant support records, or meet applicable legal obligations.

8. Security and website hosting

Google API requests use HTTPS. Local token and app-configuration files are created with owner-only file permissions. The SQLite database and local files are not encrypted by DigiBytes; their protection also depends on your device, operating-system account, disk encryption, and backups.

This public website uses local images and styles and does not embed analytics, advertising scripts, Google sign-in, or a form that collects your store records. The hosting provider may process ordinary request metadata, such as IP address, user agent, and requested URL, to deliver and protect the website. Clicking a mail link opens your email software; it does not send a message automatically.

9. Updates and contact

This policy may change when the app's functionality or data practices change. The current policy and update date will remain available on this page. Contact chaos.aca@gmail.com with questions or requests concerning this policy.