Current configuration. Aptex AI does not currently operate an advertising or analytics platform and does not intentionally set non-essential tracking cookies in the current app. It does use localStorage and third-party web resources necessary to load parts of the interface.
1. Cookies vs. local storage
Cookies are browser values that can be attached to HTTP requests. Aptex AI currently relies primarily on localStorage for local app state rather than login cookies or an account-session system.
2. What Aptex AI stores locally
History
Recent prompts and generated replies can remain in the browser. Screenshot generations store the [Screenshot] prompt marker and generated reply, not the screenshot image.
Favorites
Saved replies and related metadata can remain locally.
Preferences
Mode, sound, and related settings may remain locally.
Streak data
The app's streak value can remain locally.
Screenshot image data is held temporarily in page memory during the screenshot workflow rather than being written to localStorage. Local storage is separate from cloud account storage and is controlled by your browser.
3. No account/session cookies in the current app
The current experience does not require login or an account, so Aptex AI does not currently rely on authentication/session cookies to provide the generator.
4. No connected analytics or advertising platform
The current code includes local browser event hooks for product behavior, but no Google Analytics, Meta Pixel, PostHog, Plausible, Mixpanel, advertising tag, or similar analytics vendor is connected in this release. Those browser events remain local and do not by themselves send visitor analytics to a vendor.
5. Third-party resources
The site loads some interface dependencies from external services, including Google Fonts, cdnjs, jsDelivr, and related public libraries such as html2canvas. These requests may expose standard network information to the provider serving the resource, including IP address, browser/user-agent information, requested URL/resource, and timing.
Aptex AI does not intentionally place your chat message into those asset requests as a tracking payload.
6. Share-card rendering and download
The Share Card feature uses browser-side rendering to turn the current message/reply into a downloadable image. The current download operation creates the image in the user's browser and saves a PNG to the device. The card can include the user's message and generated reply.
Downloading the card is not an advertising or analytics cookie operation. Sharing the downloaded image through another service can cause that service to process the image under its own policies.
7. AI requests are separate from cookies
When you generate a reply in Text mode, the browser sends the submitted message and selected generation context to the Aptex AI server function, which sends the request to Groq for inference. In Screenshot mode, the browser also sends the selected screenshot image in the application request; the server function validates it and sends it to Groq for vision inference. These are application-processing requests, not cookie-based tracking operations.
8. Netlify and infrastructure requests
Aptex AI is hosted by Netlify. Netlify states that it may automatically collect device identifiers such as IP address and browser type and that its services maintain operational logs. Netlify Privacy Statement.
9. Managing cookies and local storage
You can delete or restrict cookies and site storage using your browser's privacy controls. You can also clear Aptex AI's locally stored history and favorites from the Privacy Policy page.
10. Future changes
If Aptex AI adds analytics, advertising, authentication, optional cookies, or other tracking technologies, this notice will be updated to describe the relevant technology, purpose, provider, and applicable consent choices.
11. Contact
Operator: Arpit Pathak, Nepal
Website: https://aptexai.netlify.app
Privacy contact: vibegenaii@gmail.com