What this covers
Datasan Assistant is Hassan’s personal assistant, operated by Hassan for his own connected accounts. This notice covers that assistant and its connected productivity features. It is not a public assistant service for other users or their accounts.
This notice does not replace the privacy policies of Google, OpenAI, or another provider whose service may be used for a particular request.
Information the assistant may handle
The assistant may receive Hassan’s conversation text, files, and instructions. When Hassan connects Google services and asks for a task that needs them, the assistant may handle the Google information needed for that task.
For Gmail, this may include sender or From information and other message headers, subject lines, message content, and attachments Hassan asks the assistant to retrieve or use. For Google Calendar, this may include calendar event details needed to complete the request.
The precise Google permission scope has not been published or independently confirmed here. What the assistant can access or change depends on the permissions Hassan has granted through Google and on the task he requests. Google shows connection details during authorization and in Google Account connected-app settings.
How the assistant uses it
The assistant uses the information involved in a request to carry out Hassan’s requested task—for example, to find, read, summarize, or answer questions about relevant Gmail messages or Calendar events. It may also use the request information to operate and secure that task.
If a request would affect a connected Google account, the relevant Google-granted permissions determine what is technically possible. Hassan can review or remove Google authorization at any time.
Local and cloud AI processing
The assistant can use local Ollama with Qwen models. When Hassan selects that local processing route, the request is processed by the local Ollama/Qwen runtime.
Hassan may instead select OpenAI cloud processing for an interaction. When OpenAI is selected, relevant prompt content—including conversation content and task information needed to generate a response—may be sent to OpenAI. The model provider can therefore vary by request.
Important: this page does not make claims about a provider account’s retention settings, training settings, or contractual data controls. It does not promise “no training,” “zero retention,” or a fixed provider-retention period.
Storage, retention, and deletion
No fixed retention schedule has been published for assistant conversations, local working files, logs, OAuth credentials, or provider-side records. This policy does not promise that information is never stored, that it is automatically deleted after a set period, or that every deletion request can be completed.
To ask about or request deletion of information under Datasan’s control, email hassan@datasanlabs.ai. The request and the data that can be identified and acted on will be assessed. A request to Datasan cannot by itself erase records held by Google, OpenAI, or another independent provider; their processes apply to their records.
Revoke Google access
Hassan can review or remove an app’s Google Account access at any time from Google Account third-party connections or linked-app settings. Select the connected app, review its access, and choose Remove access. Removing access may stop future access, but it may not delete data the app already received; use the email above to ask about Datasan-controlled data.
Questions / provider-specific policies
For questions about this notice, a deletion request, or the assistant’s current setup, contact hassan@datasanlabs.ai.
For provider-specific retention, training, security, and account controls, consult the provider’s current policy: Google Account Help on third-party access and OpenAI data controls. Those documents govern their respective services and may change independently of this page.