Privacy there is very little of yours to describe

Three separate things, with very different answers:

• The software. The PriceSylo engine, together with the web panel and desktop app included with it, which you install and run on your own hardware. It transmits one thing to us the licence check in 03 and collects nothing else about you. Almost all of that section is still a description of what does not happen.
• Third parties you choose. The exchanges you connect to, the webhook endpoints you point the engine at, and if you use the panel’s AI assistant the model and search providers whose accounts and keys you supply. Those receive data directly from your machine, under their own terms, not ours.
• This website. A separate, conventional web property, and the one place where processing by us actually occurs including the third-party analytics it loads on every page, which the software has never had and still does not. It is described in 08.

This policy takes effect on 28 August 2026. The publisher of PriceSylo, and the data controller for everything described here, is Laxtic Software Services, a business name registered with the Corporate Affairs Commission of Nigeria (Business Name Registration No. 8618796), of 1 Adekunle Owobiyi Close, off Oladele Kadiri Close, Ogba, Lagos State, Nigeria.

Everything the software produces or remembers stays on your machine in the folder the engine runs from, or in the browser profile you run the panel in:

The engine is not offline, and claiming otherwise would be false. It needs outbound HTTPS/WSS access to do its job. The accurate statement is narrower: every outbound connection but one goes to a destination you chose, and the one that is ours carries your licence and nothing else.

• Exchange feeds. Live websocket connections for the pairs you favorite, to the exchanges you favorite them on. You choose which; the engine idles at zero cost until you do.
• Pair-catalogue refresh. A public, unauthenticated fetch of the exchanges’ own listings, at most about once a day. No credentials are involved.
• Chart history. Charting a pair you do not already track fetches its history from the exchange. Rendering itself makes no network call at all.
• Trading calls, if you make any. Requests to the exchange you addressed, on the credentials you supplied for that call. See 05 below.
• Webhook deliveries you configured. If you create a subscription, the engine posts to the endpoint you gave it when your condition fires, signed with HMAC-SHA256 so your endpoint can verify it. You pick the destination; there is no default and no fallback to anything of ours.
• The licence check. One encrypted request to us when the engine starts, and another periodically while it runs. It is the only endpoint of ours the software has, and the box below sets out everything it carries.
• Nothing else. No crash reporter, no usage counter, no update ping, and no second channel that could be asked for more later. Beyond the answer to the one licence question, the software does not report and does not receive instructions.

The panel adds exactly one category on top of that, and only if you turn it on: the model and search providers you configured for the assistant. That is the next section.

• Your keys stay with you. Provider keys are held encrypted in your browser on your machine, unlocked by you. The panel records only whether a provider is configured, never the value. Nothing about a key is transmitted to us, and no key is ever displayed back through any read surface.
• What travels, travels straight to the provider. When you send a message, your prompt, the conversation so far, and whatever context the assistant gathered for it market context read from your own engine, and a chart image if you asked for a visual read go directly from your browser to the provider you selected, on your own account. That traffic does not pass through any infrastructure of ours, and we cannot see it.
• Their policy governs it, not this one. What a provider logs, how long it keeps a prompt, whether it trains on it and where it processes it are governed by that provider’s own terms and privacy policy. We are not a party to that relationship and cannot make commitments on their behalf. Read the policy of any provider you enable before you send it anything you would not want a third party to hold.
• Web search and page reading. If you enable them, your query goes to the search provider you selected, and fetching a page reaches that page’s host. Same rule: your choice, your account, their policy.
• Conversations stay local. Your assistant conversations, your edited skills and your saved routines live in your browser’s storage on your machine. They are not synced, not backed up by us, and not readable by us.
• It can fill an order ticket. It cannot submit one. The confirm control is human-only and refuses the assistant unconditionally. Every order that reaches an exchange was pressed by a person.

Assistant output is generated by a third-party model that you chose and paid for. It is not reviewed by us, it is not our advice, and it can be confidently wrong. See the terms for what that means in practice.

Exchange API credentials are optional. Everything except trading works fully without them. If you do add them, this is what happens to them:

• They are held encrypted, in your browser, on your machine, and unlocked by you. Locking, or simply closing the panel, puts them back out of reach.
• They are supplied with the individual request that needs them, used for that one call against the exchange they belong to, and held no longer than the call. They are not written into the engine’s stored settings, and they are not kept in its local record of your orders.
• No read surface ever returns a credential value. A surface will tell you that an exchange is configured; it will not tell you, or an agent, what the secret is. Text an exchange echoes back inside an error is stripped of credential-shaped content before it reaches you.
• They never reach us. There is no destination of ours anywhere in that path. If someone demanded your exchange keys from us, we would have nothing to give them.
• The protection that matters is therefore yours to keep: anyone who can unlock the vault on your machine can trade with it. See 07.

Because none of your market data, your analysis or your trading leaves your machine unless you send it and the licence check carries none of it the privacy of your PriceSylo data is a property of your machine rather than of anything we operate. That is the trade this product makes, and it is worth stating plainly rather than burying:

• Disk encryption, screen lock, operating-system account hygiene and backups are yours to manage. So is who else can use the computer.
• Encryption at rest protects your keys when the vault is locked. It cannot protect an unlocked machine, a compromised browser profile, or a browser extension you installed that can read the page.
• We cannot reset, recover or export your data for you. There is no account, no server-side copy of anything you produced, and no support back door into your machine. If you lose the data, it is lost; if you lose control of the machine, we cannot help you contain it. Revoke exposed exchange keys at the exchange. The one record we do hold is the licence itself enough to move an installation off a machine you no longer have, and nothing more.

This is the one place where processing by us actually occurs, and it is the part of this document that changed most. An earlier version of this page said the site carried no analytics and set no cookie. That is no longer true, and the sentences that said it are deleted rather than qualified: the site now measures its own traffic with Google Analytics, and the box below sets out what that loads, what it sets, what it reports and how to stop it. Everything else here is what serving a website necessarily involves, described rather than glossed over.

• What the site keeps in your browser. Beside the two analytics cookies above, the site keeps four small values in this browser’s own local storage, and each is either a preference you set or bookkeeping for something you did on the page: the language you picked from the switcher, so the site is still in it when you return; a colour-theme choice, if you made one while that control was on the page the current build is fixed to one theme and neither reads nor writes that value, and it is left alone rather than quietly cleared; a random per-browser identifier the same one the contact form below uses, minted on your machine and not derived from anything about you; and the list of suggestions you have already voted on, so a suggestion you voted on still reads as voted when you come back. The language, the theme and the voted list never leave your browser at all; the identifier travels only with a vote or a contact submission. Clearing this site’s data clears all four, and nothing restores them from anywhere.
• The pages themselves are static. The site is a static export: the same file is served to every reader, and there is no server of ours behind a page view deciding what you get. Its fonts are bundled with the site rather than fetched from a third party as you browse, so no request for a typeface tells anyone that you were here.
• One embedded video. The home page embeds a product walkthrough hosted on YouTube, loaded through the privacy-preserving youtube-nocookie.com domain. It is a third-party frame: your browser fetches the player from YouTube, and the video itself if you press play. That domain is used precisely so YouTube sets no cookie and stores nothing on you unless you actually start playback and once you do, what it then collects is governed by Google’s policy, not this one. Apart from that frame and the analytics loader above, nothing else on the site loads from a third party as you browse.
• Hosting and server logs. The site is served for us by a third-party hosting provider, and, as with any web host, it sees the requests made for the pages: your IP address, what you asked for, when, and the user-agent string your browser sends. Those are ordinary server logs, kept for security and for keeping the site up, and we do not use them to build a profile of you or combine them with anything else. There is nothing else of yours here to combine them with.
• Nothing is added at the edge. The hosting provider, and any content delivery network in front of the site, inject nothing of their own: no further analytics, no tag manager, no advertising pixel, no tracking script. What the source contains is what your browser receives and the Google Analytics loader described above is in that source, and is the whole of it.
• The contact form. Pressing send submits it to our own service, which files it for the support@pricesylo.com mailbox. What is sent is what you typed your name, your address, your message, and the topic you picked plus a random identifier this browser generated for itself, which exists so a flood of submissions can be told apart and is not derived from anything about you. Nothing leaves the tab until you press send. If the submission cannot get through, the page falls back to composing the same message in your email client for you to send yourself. Either way the message ends up in that mailbox, which is a business mailbox on our own domain, operated for us by a third-party email provider under its own terms. We keep support correspondence for as long as it is useful for answering you and for our own record of the exchange, and no longer.

PriceSylo is sold under two licences: a personal licence at $85 that runs for one year and is renewed at the end of it, and a commercial licence at $599 that runs for two years and is renewed at the end of that term. Each is bought once, for its term; neither is perpetual and neither renews itself. Neither is a subscription to a hosted service, because there is no hosted service. The licence covers the engine, with the web panel and desktop app included.

• Payment and delivery happen off this site. Checkout is handled by Zatabox, the third-party payment and box-office platform we sell through, and the build follows from that purchase; this site takes no payment and hosts no download. So the personal data involved is what the purchase itself requires your email above all, because the email you buy with is the identity the licence is issued against, and the one your copy presents at every check.
• What Zatabox holds, and what reaches us. Zatabox takes the payment on its own platform, under its own terms and privacy policy, and it not we handles your card or payment-method details. We never see them. What comes back to us is the completed order: the email you bought with, which licence you bought, and the fact and time of payment. That is what issuing a licence needs, and it is all we take from it.
• How long any of it is kept. Your purchase record, the licence key issued against it, and the one-way machine fingerprints counted against its allowance are held for as long as the licence is live a licence cannot be verified, renewed or moved to a new machine without them. After it ends they are kept only for as long as we are required to keep a record of the underlying transaction, or for as long as a claim arising from the purchase could still be brought, whichever is longer, and are then deleted.
• The software verifies the licence, and will not run without a valid one. Buying creates a licence record against your email on our side and mails you the key it issued; the copy on your machine is activated with that key and re-validates it periodically after that 03 sets out exactly what that check carries. A licence covers a fixed number of machines at a time: up to three on the personal licence, up to ten on the commercial one. We count activations against that allowance, which is why a one-way machine fingerprint is part of the check at all. If the licence has expired, or its allowance is already taken, the software declines to start and tells you which it was.

The data controller is Laxtic Software Services, at the address in 01, and the regime that governs its processing is the Nigeria Data Protection Act 2023, supervised by the Nigeria Data Protection Commission. Under it you have the right to ask for access to the personal data we hold about you, to have it rectified where it is wrong, to have it erased, to have our processing of it restricted, to receive it in a portable form, to object to our processing of it, to withdraw a consent you have given, and to lodge a complaint with the Commission.

If the law where you live applies to you independently of ours the EU or UK GDPR, for instance nothing in this policy limits the rights it gives you. Ask in the same way, and we will handle the request under whichever regime gives you more.

In practice the answer to most such requests is short, because there is very little to answer about. The only personal data the software gives us is what the licence check carries the email you bought with, and the installation records tied to it together with the purchase record behind it. Your settings, your tracked pairs, your credentials, your conversations and your analysis never reach us at all. They are files and browser storage on your own machine, and you can inspect or delete them directly; there is nothing there for us to access, export, correct or delete on your behalf.

The website adds one thing to that answer, and it is worth being exact about: the analytics in 08. Those measurements sit in Google’s system against an identifier your browser holds, and nothing on our side joins that identifier to your name, your email or your licence so a request to show you “your” analytics is one we cannot honestly match to you, and we will say so rather than guess. What you can do works immediately and needs no request at all: block the script, or clear this site’s data to drop the cookies. 08 says how.

One consequence is worth naming rather than burying: erasing the licence record erases the licence. A copy that cannot be verified does not run, so a request to delete that record is in effect a request to end the licence, and we will say so before acting on it rather than after.

For data held by a model, search or exchange provider you chose, exercise your rights with that provider we have no access to it and cannot act on your behalf.

To exercise any of these rights, or for anything else relating to this policy or this website, write to support@pricesylo.com, or by post to Laxtic Software Services, 1 Adekunle Owobiyi Close, off Oladele Kadiri Close, Ogba, Lagos State, Nigeria. If you are not satisfied with how we handle it, you may complain to the Nigeria Data Protection Commission.

This policy changes when the product changes or when the law does. Substantive changes are dated and summarised here, and the version history kept, so that what the policy said on the day you bought is recoverable rather than a matter of memory.

This version is in force from 28 August 2026 and replaces every earlier one.