Privacy

Privacy Policy

This policy explains what Reszu collects, why it is collected, how profile visibility works, and how users can raise privacy or data requests.

Information We Collect

  • Account details such as name, email, password hash, role, and plan.
  • Profile details such as headline, brief, city, skills, tools, projects, work experience, education, certifications, achievements, languages, links, hobbies, and availability preferences.
  • Private details such as phone, WhatsApp, date of birth, gender, and contact email when provided.
  • Uploaded or linked content such as profile photos, portfolio links, GitHub links, LinkedIn links, websites, and YouTube intro links when provided.
  • Recruiter details such as recruiter type, company, work email, city, hiring sectors, and approval status.
  • Usage data such as applications, bulk applications, saves, contact requests, profile views, support requests, authentication events, and rate-limit/security events.
  • Payment and plan-related references when payments are enabled, such as payment status, plan activation, receipt or invoice references, and support details. Full payment instruments are handled by payment providers and are not intended to be stored by Reszu.

How We Use Information

  • To create and display candidate profiles and resumes.
  • To match candidates with curated jobs and application tools.
  • To allow approved recruiters to search published profiles and request contact access.
  • To process payments, plan access, support calls, mock interview scheduling, profile reviews, moderation, and security checks.
  • To improve taxonomy, job matching, profile generation, and product quality.
  • To detect abuse, spam, fake profiles, suspicious recruiters, inappropriate uploads, duplicate accounts, or other misuse.

Public Profile Privacy

Public HTML profiles are designed not to expose direct phone, WhatsApp, private email, date of birth, full address, or hidden legal details. Approved recruiters can see private contact details only after the candidate accepts a contact request.

When a candidate publishes a Public Profile, professional details such as display name, headline, brief, city if visible, skills, tools, projects, experience, education, certifications, achievements, links, hobbies, and other selected profile blocks may be visible to anyone with the profile URL.

Visibility Controls

Candidate privacy settings may allow certain fields to be private, visible to accepted contacts, visible to recruiters, or public. Fields such as phone, WhatsApp, contact email, date of birth, complete address, and legal-name details are private by default or protected by visibility controls.

Visibility settings affect Reszu screens and public pages, but candidates should still review any resume export, copied text, screenshot, or externally shared profile content before sending it outside Reszu.

Resume Export

Resume/PDF export may include contact details because it is intended to work like a traditional CV. Candidates should review the export before sharing it.

Recruiter Access and Contact Requests

Approved recruiters may search published candidate profiles and request contact access for genuine hiring or recruitment activity. Private contact details are not intended to be shown to recruiters unless the candidate accepts the contact request or otherwise chooses to reveal those details.

Recruiters must not scrape, resell, spam, or misuse candidate information. Candidate reports about recruiter misuse can be submitted through the Support page.

Job Applications and Job Leads

When a candidate applies to a Reszu Exclusive Job or uses Apply Through Reszu for a Curated Job Lead, Reszu stores the application or interest record. Reszu may show or share relevant profile/application information with the recruiter, company, source, or internal staff handling the application workflow.

If a candidate follows an external source link, that external website may collect information under its own privacy policy and terms.

Security

Reszu uses session protection, CSRF protection, rate limits, password hashing, and encrypted storage for sensitive private details where implemented. No online service can guarantee absolute security.

Security and abuse-prevention records may include hashed or fingerprinted request information such as IP and user-agent context. These records help investigate fraud, spam, account abuse, and security incidents.

Data Sharing

Reszu does not sell candidate private contact details. Public profile information may be visible to anyone with the profile URL when the profile is published. Approved recruiters may access additional contact details only through candidate-approved contact requests.

Reszu may use service providers for hosting, database infrastructure, payment processing, security, analytics, support, or communication. These providers should be used only for operating and improving the service.

User Rights and Data Requests

Users may request access to their account/profile data, correction of inaccurate information, profile unpublishing, account deletion, or removal of private details through the Support page. Candidates can also update many profile fields directly from their dashboard.

Some transaction, security, support, consent, payment, or legal records may be retained where required for fraud prevention, billing, compliance, dispute handling, or legitimate service operations.

Data Retention

Reszu keeps account and profile data while the account is active or as needed to provide the service. Deleted or removed profile content may be removed from public display, but limited backend records may remain for security, audit, payment, legal, or operational reasons.

Support and Grievance Route

Privacy questions, data removal requests, recruiter misuse reports, payment-plan concerns, support issues, or other grievances can be submitted through the Support page. Support and grievance access is available to free and paid users.

Reszu aims to respond to support requests within 2 business days. Privacy or legal grievances will be reviewed and responded to within the applicable legal timeline.