Rafiq keeps chats and settings in this browser. It does not use advertising cookies, and it does not follow you across other websites.
This page lists what Rafiq stores in the browser on rafiqai.app, and the one cookie used when you sign in. It was last updated on 9 October 2026.
Most of what Rafiq remembers on the device is local storage, not a cookie. Local storage stays in this browser and is not attached to requests you make to other sites. A cookie is a small file the browser sends back to the site that set it.
The sidebar is rebuilt from a list kept in this browser: the titles, the order, and enough of each chat to show it again. A copy of those chats is also stored on the server, which is described on the Privacy page. Clearing only this browser removes the list from the device. It does not, by itself, delete the server copy.
Display choices are kept in this browser so the next visit opens the way you left it. That includes theme, type size, font, high contrast, accent colour, reading width, and line spacing.
The General profile, when you have saved it, is also remembered here: name, background, answer language, and the city, country, and calculation method for prayer times. Saving the profile sends those to your profile on the server as well.
Text still sitting in the question box is kept for that chat, in this browser, so a draft is still there if you leave and come back. It is removed when you send the question or clear it.
If you are not signed in, this browser keeps a random id. New chats are stored against it. The id is created on the device. It is not your name, and it is not shared with other websites.
Signing in sets a session cookie from the Nizam account service. Rafiq reads that cookie to know the visit is signed in, and to receive the account id, name, email, and picture the account provides.
The cookie is sent only to the sign-in flow and to Rafiq. It is not an advertising cookie. Signing out clears the session. When the session ends, the cookie stops identifying you, and the next visit is signed out until you sign in again.
The page loads a Cloudflare analytics beacon. The beacon counts visits to Rafiq. It does not build an advertising profile, and it is not used to follow you from site to site.
The question you send is handled on the server. DeepSeek does not set a cookie in your browser for that. The network address used to limit how many questions one connection can send in a minute is stored on the server as a short counter. It is not a cookie, and it is described on the Privacy page.
Use the browser's controls for cookies and site data. Clearing them signs you out, removes the local chat list, removes display settings, and removes the random id. The next visit starts blank on this device.
A chat already stored on the server stays until you delete it from the sidebar, while you still have the id or the account it was saved under. Clear the device only after deleting anything you want gone from the server as well.
What happens to a question after you send it is on the Privacy page. What an answer is, and what it is not, is on the Terms page. Both are linked under the question box.