Who operates this system
Glitch is operated as a private, internal tool by Otar Kapanadze. Enquiries relating to this policy may be sent to oto.kapanadze.dev@gmail.com.
Who this policy covers
This system has no public users. It is used by its operator alone, and the only personal data it holds belongs to that operator. We do not collect data about visitors to this page, and we do not operate any service into which a member of the public could enter personal data.
What is stored
- Operator account details — name, email address, and a hashed password.
- Brokerage authorization credentials — API credentials or OAuth access tokens for the operator's own brokerage accounts.
- Trading records — orders, positions, fills, and equity history produced by the operator's own activity.
- Application and access logs, retained for security and diagnostics.
There are no analytics packages, advertising networks, third-party trackers, session recorders, or marketing tooling on this domain.
Brokerage data
When the operator authorizes a brokerage connection, Glitch receives an access token scoped to that operator's own accounts. It uses this token only to read account and position state and to place, modify, and cancel orders in those accounts. It does not request, receive, or store data belonging to any other customer of that brokerage, and it does not transmit brokerage data onward to any third party.
Storage and security
Brokerage credentials and tokens are encrypted at rest in the application database. All traffic to this system and to brokerage APIs is served over TLS. Access to the application is restricted to authenticated operator accounts; there is no public registration path.
Retention
Trading records are retained for as long as they remain operationally or fiscally useful to the operator. Brokerage credentials are retained until the connection is disconnected within the application, at which point the stored credentials are erased. Access logs are retained on a rolling basis.
Third parties
Data is shared only with the infrastructure and market-data providers required to run the system — the hosting provider, the brokerage APIs the operator has connected, and market-data vendors. No data is sold, rented, or shared for advertising or marketing purposes.
Revoking access
The operator may revoke Glitch's access to a connected brokerage at any time, either from within this application or directly from the brokerage's own platform. Revocation takes effect immediately and stored credentials for that connection are erased.
Changes to this policy
This policy may be updated as the system changes. The effective date above will be revised when it is.