Product documents
Privacy policy
A summary of the data required to operate Fursara and the choices available to you.
Updated draft — requires legal review before public release.
Version: 2026-10-private-answers-1 · Proposed effective date: 2026-10-01
Data we process
We process account, contact, CV, preference, job, application, and payment data to provide requested features and protect the service.
Why we use data
Data supports accounts, CV extraction, job discovery, analysis, alerts, payment processing, and fraud or abuse prevention.
Service providers
Required data may be processed by hosting, database, email, payment, notification, and AI providers. We do not sell CV or application data to advertisers.
Browser extension
The extension reads the content of a job page only when you press a button in it, and sends that job text together with your profile fields to Fursara servers to fill the application or analyse your fit. It does not read other pages, does not run in the background, never presses submit, never bypasses a CAPTCHA, and sells nothing. Your sign-in session and settings are kept in browser storage and are removed when you uninstall it.
What we send to an employer
When you approve an application to be sent on your behalf, we send that employer only what was shown to you at approval: your name, contact details, CV file and your answers to its questions. Some employers ask sensitive questions (such as nationality, expected salary or disability); we send an answer to one only if you wrote it yourself for that application, and only keep a reusable copy with your separate choice and consent, as described under “Saved private answers”. Sending is done from a device operated by the Fursara team through an ordinary browser, and we keep the outcome, its date and any note the form returned. Once received, your data is subject to the employer's own privacy policy.
Artificial intelligence
Audit and matching send only required content to the AI provider with response storage disabled. CV and job text are excluded from operational logs.
Account deactivation
You can deactivate your account in settings. Under the current product decision, data remains retained and the account is flagged as disabled; we do not claim permanent deletion. This must change before app-store account-deletion requirements can be approved.
Employers' replies from your mailbox
Connecting your mailbox is optional and happens with your explicit consent through Google. Once connected, we search your mail for messages that look like a reply to a job application and read only their sender, subject and first line, to update your request's status (an interview invitation or a rejection). We never read message bodies or attachments, send nothing from your mailbox and delete nothing in it. We keep the reply's kind, its subject and the sender's domain; of any other message we keep only its identifier, so it is not examined twice. Your mailbox data is not sent to the AI provider, is not used for advertising and is not sold. The access permission is stored encrypted, and one press in your requests page disconnects it — we then delete the permission and everything we noted. Fursara's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Saved private answers
An employer may ask about health, disability, beliefs or criminal history, or other private information such as nationality and salary. Only you type or select these answers; we do not infer them from your CV or generate them with AI. An answer you save remains in that application record. Only when you choose to keep a private answer and give separate explicit consent do we also store a reusable copy: the answer, question wording, confirmation time and a question-derived identifier linked to your account. We use it to show your answer when the question recurs. These private answers are never sent to the AI provider or used to rank jobs or target advertising. A later application offers the answer for review; it is not confirmed or sent without your saving it and approving that application. Accepting the terms is not consent to keep answers. You may decline storage and answer each application separately. Withdraw storage consent by deleting the answer in Auto-apply settings, or unticking its keep option and saving the application. This removes the reusable copy from active data and stops later suggestions. It does not erase answers already saved in application records or revoke an approved submission; edit the application or separately withdraw submission approval before sending begins. A reusable copy remains until you remove it, or is deleted automatically 180 days after you last confirmed it (saved it again unchanged). This period is a proposal awaiting legal approval. The activity log records keeping or forgetting and the question identifier, not the answer text. This action does not claim to erase employer copies or backups. Contact us for broader withdrawal or destruction requests under your applicable rights. Application-record, audit-log and backup retention periods and destruction procedures require legal approval and implementation before launch. Your answers that are not private (years of experience, degree, city) are kept to fill your next requests while «Keep my answers that are not private» is ticked on the review page; they are listed in the auto-apply setup, where you can delete them. What we fill automatically comes only from your setup, your CV or your earlier answers, and none of it is sent until you review and approve that request. This wording is a draft for legal review.
Sharing and transfers
We share the minimum necessary data with hosting, email, AI, payment, and notification providers. Processing outside Saudi Arabia requires the approved legal safeguards.
Retention
Operational and backup retention periods are not approved yet and must be fixed legally and operationally before launch.
Your rights
Depending on applicable law, you may request access, a copy, correction, destruction, consent withdrawal, or submit a complaint after proportionate identity verification.
Security
Controls include encrypted transport, password hashing, access control, and server-side payment verification. No service can eliminate all risk.
Cookies and analytics
We use technologies necessary for sessions, security, and preferences. We also record each browser's first visit on our own servers: a random identifier your browser generates and keeps, your device type, browser and operating system in general terms, and the channel the visit came from. We do not record your IP address or any device fingerprint, the identifier means nothing outside Fursara, and clearing this site's data in your browser ends it. We may use Google Analytics to measure our campaigns — with IP anonymization and no ad personalization — and it runs only after you accept the choice notice; you can decline, or change your mind by clearing this site's data in your browser.