├── .env.example
├── .github
├── FUNDING.yml
├── ISSUE_TEMPLATE
│ └── ISSUE_TEMPLATE
│ │ ├── bug_report.md
│ │ └── enhancement-request.md
├── PULL_REQUEST_TEMPLATE.md
└── workflows
│ └── workflows
│ └── greetings.yml
├── .gitignore
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── Faqs.html
├── Hero Section.jpg
├── Li.gif
├── RateMyResume.css
├── RateMyResume.html
├── RateMyResume.js
├── RateMyResumeData
└── mohitresume.pdf
├── Resume.css
├── Resume.js
├── about.html
├── assets
├── emily_johnson.jpg
├── instant resume.jpg
├── joao-ferrao-4YzrcDNcRVg-unsplash.jpg
├── john_smith.jpg
├── jondoe.jpg
├── securedata.jpg
└── support.jpg
├── ats_score_finder.html
├── backend
├── app.js
├── config
│ └── databaseConfig.js
├── controller
│ └── authController.js
├── index.js
├── middleware
│ └── jwtAuth.js
├── model
│ └── userSchema.js
├── package-lock.json
├── package.json
└── router
│ └── authRoute.js
├── boy.png
├── chatbot.gif
├── chatbot.html
├── colorChoice.html
├── comment.html
├── contact.html
├── contributing.md
├── cv.html
├── feedback.html
├── feedbackformimg.jpeg
├── global.css
├── images
├── Gemini_Generated_Image_52rg8r52rg8r52rg.jpg
├── Gemini_Generated_Image_fx9dejfx9dejfx9d.jpg
├── Gemini_Generated_Image_ootrdvootrdvootr.jpg
├── background-home.png
├── favicon-removebg-preview.png
├── hero.jpg
├── logo.png
├── logo.png.jpeg
├── sample-color1.png
├── sample-color2.png
├── sample-color3.png
├── sample-color4.png
├── sample-color5.png
├── sample-color6.png
├── sample-color7.png
├── sample-resume1.jpg
├── sample-resume2.jpg
├── sample-resume3.jpg
├── sample-resume4.jpg
├── sample-resume5.jpg
├── sample-resume6.jpg
├── sample-resume7.jpg
└── sample-resume8.jpg
├── index.html
├── login.css
├── login.html
├── login.js
├── package-lock.json
├── package.json
├── privacy-policy.css
├── privacy-policy.html
├── privacypolicy.html
├── readme.md
├── resume.html
├── resume2.js
├── resume_tips.html
├── script.js
├── signup.html
├── style.css
├── styles.css
└── templates
├── basic.html
├── basic.jpg
├── classic.html
├── classic.jpg
├── developer.html
├── developer.jpg
├── modern.html
├── modern.jpg
└── templates.css
/.env.example:
--------------------------------------------------------------------------------
1 | YOUR API KEY =
--------------------------------------------------------------------------------
/.github/FUNDING.yml:
--------------------------------------------------------------------------------
1 | # These are supported funding model platforms
2 |
3 | github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
4 | patreon: # Replace with a single Patreon username
5 | open_collective: # Replace with a single Open Collective username
6 | ko_fi: # Replace with a single Ko-fi username
7 | tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
8 | community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
9 | liberapay: # Replace with a single Liberapay username
10 | issuehunt: # Replace with a single IssueHunt username
11 | lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
12 | polar: # Replace with a single Polar username
13 | buy_me_a_coffee: # Replace with a single Buy Me a Coffee username
14 | thanks_dev: # Replace with a single thanks.dev username
15 | custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']
16 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/ISSUE_TEMPLATE/bug_report.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Bug Report 🐞
3 | about: Reporting for any bug in the project.
4 | title: '🐛: '
5 | labels: ["Up-for-Grabs ✋", "bug 🐛"]
6 | assignees:
7 | - ''
8 |
9 | ---
10 |
11 | :red_circle: **Title** :
12 | :red_circle: **Bug** :
13 | :red_circle: **Changes** :
14 |
15 |
16 | ### Screenshots 📷
17 |
18 |
19 |
20 | ***********************************************************************
21 | :white_check_mark: **To be Mentioned while taking the issue :**
22 | - Full name :
23 | - What is your participant role? (Mention the Open Source Program name. Eg. GSOC, GSSOC, SSOC, JWOC, etc.)
24 |
25 | ***********************************************************************
26 | Happy Contributing 🚀
27 |
28 | All the best. Enjoy your open source journey ahead. 😎
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/ISSUE_TEMPLATE/enhancement-request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Enhancement Request 🧑💻
3 | about: Improving any styling or documentation of the project.
4 | title: '🧑💻: '
5 | labels: ["Up-for-Grabs ✋", "enhancement 🧑💻"]
6 | assignees:
7 | - ''
8 |
9 | ---
10 |
11 | :red_circle: **Title** :
12 | :red_circle: **Enhancement Aim** :
13 | :red_circle: **Changes** :
14 |
15 |
16 | ### Screenshots 📷
17 |
18 |
19 |
20 | ***********************************************************************
21 | :white_check_mark: **To be Mentioned while taking the issue :**
22 | - Full name :
23 | - What is your participant role? (Mention the Open Source Program name. Eg. GSOC, GSSOC, SSOC, JWOC, etc.)
24 |
25 | ***********************************************************************
26 | Happy Contributing 🚀
27 |
28 | All the best. Enjoy your open source journey ahead. 😎
--------------------------------------------------------------------------------
/.github/PULL_REQUEST_TEMPLATE.md:
--------------------------------------------------------------------------------
1 | # Pull Request for Resum-Resume 💡
2 |
3 |
4 | ## Issue Title :
5 |
6 | - **Info about the related issue (Aim of the project)** :
7 | - **Name:**
8 | - **GitHub ID:**
9 | - **Email ID:**
10 |
11 |
12 |
13 |
14 | Closes: #issue number that will be closed through this PR
15 |
16 | ### Describe the add-ons or changes you've made 📃
17 |
18 | Give a clear description of what have you added or modifications made
19 |
20 | ## Type of change ☑️
21 |
22 | What sort of change have you made:
23 |
27 | - [ ] Bug fix (non-breaking change which fixes an issue)
28 | - [ ] New feature (non-breaking change which adds functionality)
29 | - [ ] Code style update (formatting, local variables)
30 | - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
31 | - [ ] This change requires a documentation update
32 |
33 | ## How Has This Been Tested? ⚙️
34 |
35 | Describe how it has been tested
36 | Describe how have you verified the changes made
37 |
38 | ## Checklist: ☑️
39 |
43 | - [ ] My code follows the guidelines of this project.
44 | - [ ] I have performed a self-review of my own code.
45 | - [ ] I have commented my code, particularly wherever it was hard to understand.
46 | - [ ] I have made corresponding changes to the documentation.
47 | - [ ] My changes generate no new warnings.
48 | - [ ] I have added things that prove my fix is effective or that my feature works.
49 | - [ ] Any dependent changes have been merged and published in downstream modules.
--------------------------------------------------------------------------------
/.github/workflows/workflows/greetings.yml:
--------------------------------------------------------------------------------
1 | name: Greetings 🐦🔥
2 | on: [pull_request_target, issues]
3 |
4 | jobs:
5 | greeting:
6 | runs-on: ubuntu-latest
7 | permissions:
8 | issues: write
9 | pull-requests: write
10 | steps:
11 | - uses: actions/first-interaction@v1
12 | with:
13 | repo-token: ${{ secrets.GITHUB_TOKEN }}
14 | issue-message: "Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible."
15 | pr-message: "Thank you, ${{ github.actor }}, for creating this pull request and contributing to Resum-Resume! 💗\n\n The maintainers will review this Pull Request and provide feedback as soon as possible! 😇\nWe appreciate your patience and contribution, Keep up the great work! 😀"
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # Ignore node_modules directory
2 | node_modules/
3 |
4 | # Ignore build directories
5 | dist/
6 | build/
7 |
8 | # Ignore log files
9 | *.log
10 |
11 | # Ignore environment variables
12 | .env
13 | .env.local
14 | .env.*.local
15 |
16 | # Ignore OS-specific files
17 | .DS_Store
18 | Thumbs.db
19 |
20 | # Ignore IDE/editor settings
21 | .vscode/
22 | .idea/
23 |
24 | # Ignore package lock files
25 |
26 | yarn.lock
27 |
28 | # Ignore coverage reports
29 | coverage/
30 |
31 | # Ignore compiled files
32 | *.out
33 | *.exe
34 | *.dll
35 |
36 | # Ignore temporary files
37 | *.tmp
38 | *.temp
39 | *.swp
40 |
41 | # Ignore dependency directories for Python
42 | __pycache__/
43 | *.py[cod]
44 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | We, as contributors and maintainers of this project, pledge to make participation in our community a respectful, harassment-free, and inclusive experience for everyone. We commit to fostering a collaborative environment regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6 |
7 | ## Our Standards
8 |
9 | Examples of behavior that contributes to a positive environment include:
10 |
11 | - Using welcoming and inclusive language
12 | - Respecting differing viewpoints and experiences
13 | - Giving and gracefully accepting constructive feedback
14 | - Focusing on what is best for the community
15 | - Showing empathy and kindness toward other community members
16 |
17 | Examples of unacceptable behavior include:
18 |
19 | - The use of sexualized language or imagery and unwelcome sexual attention or advances
20 | - Trolling, insulting or derogatory comments, and personal or political attacks
21 | - Public or private harassment
22 | - Publishing others’ private information, such as a physical or electronic address, without explicit permission
23 | - Any other conduct which could reasonably be considered inappropriate in a professional setting
24 |
25 | ## Our Responsibilities
26 |
27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28 |
29 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that do not align with this Code of Conduct. They may also temporarily or permanently ban any contributor for behaviors they deem inappropriate, threatening, offensive, or harmful.
30 |
31 | ## Scope
32 |
33 | This Code of Conduct applies to all project spaces, including but not limited to the repository, issue trackers, social media, and any other platform used by the project. It also applies to interactions both within project spaces and in public spaces when an individual is representing the project or its community.
34 |
35 | ## Enforcement
36 |
37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at garimasingh11203@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
38 |
39 | All project team members are obligated to maintain confidentiality regarding the reporter of an incident. Further details of specific enforcement policies may be posted separately.
40 |
41 | ## Enforcement Guidelines
42 |
43 | Project maintainers will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
44 |
45 | ### 1. Correction
46 | **Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome.
47 | **Consequence**: A private, written warning from project maintainers. Further violations may result in more severe consequences.
48 |
49 | ### 2. Warning
50 | **Impact**: A violation through a single serious incident or a pattern of inappropriate behavior.
51 | **Consequence**: A warning with consequences for continued behavior, including temporary or permanent removal from interactions with the community.
52 |
53 | ### 3. Temporary Ban
54 | **Impact**: A serious violation of community standards, including sustained inappropriate behavior.
55 | **Consequence**: A temporary ban from any form of interaction or public communication with the community.
56 |
57 | ### 4. Permanent Ban
58 | **Impact**: Demonstrating a pattern of sustained inappropriate behavior or harassment.
59 | **Consequence**: A permanent ban from the community.
60 |
61 | ## Attribution
62 |
63 | This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
64 |
65 | For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq.
66 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | Here's the revised `CONTRIBUTING.md` file with your additional instructions:
2 |
3 | ---
4 |
5 | # Contributing to LinkedIn Resume Builder 🤝
6 |
7 | Thank you for your interest in contributing to the LinkedIn Resume Builder project! We appreciate your help in making this project better. Please follow the guidelines below to ensure a smooth contribution process.
8 |
9 | ## Table of Contents 📚
10 |
11 | - [Forking the Repository](#forking-the-repository)
12 | - [Setting Up the Development Environment](#setting-up-the-development-environment)
13 | - [Submitting Issues](#submitting-issues)
14 | - [Submitting Pull Requests](#submitting-pull-requests)
15 | - [Coding Style and Best Practices](#coding-style-and-best-practices)
16 | - [Running Tests](#running-tests)
17 | - [Code of Conduct](#code-of-conduct)
18 |
19 | ## Forking the Repository 🍴
20 |
21 | 1. Click on the **Fork** button at the top right corner of the repository page.
22 | 2. Clone your forked repository to your local machine:
23 |
24 | ```bash
25 | git clone https://github.com/your-username/linkedin-resume-builder.git
26 | ```
27 |
28 | 3. Navigate to the project directory:
29 |
30 | ```bash
31 | cd linkedin-resume-builder
32 | ```
33 |
34 |
35 | ## Submitting Issues 🐛
36 |
37 | If you find a bug or have a feature request, please submit an issue by following these steps:
38 |
39 | 1. Navigate to the **Issues** tab of the repository.
40 | 2. Click on the **New Issue** button.
41 | 3. Fill out the issue template with the necessary details. Please include:
42 | - A brief description of the issue.
43 | - Screenshots (if applicable) to illustrate the problem.
44 |
45 | ## Submitting Pull Requests 🔄
46 |
47 | To submit a pull request:
48 |
49 | 1. **Star the Repository** ⭐: If you find this project helpful, please star the repository to show your support!
50 |
51 | 2. Ensure your fork is up to date with the main repository:
52 |
53 | ```bash
54 | git checkout main
55 | git pull upstream main
56 | ```
57 |
58 | 3. Create a new branch for your feature or fix:
59 |
60 | ```bash
61 | git checkout -b your-branch-name
62 | ```
63 |
64 | 4. Make your changes and commit them:
65 |
66 | ```bash
67 | git add .
68 | git commit -m "Add a brief description of your changes"
69 | ```
70 |
71 | 5. Push your branch to your forked repository:
72 |
73 | ```bash
74 | git push origin your-branch-name
75 | ```
76 |
77 | 6. Go to the original repository and create a pull request. In your pull request:
78 | - Write a brief description of the changes.
79 | - Include before and after screenshots (if applicable).
80 | - Mention the issue number that your pull request addresses.
81 |
82 | 7. After your pull request is merged, please delete your forked repository and fork it again to avoid clashes when merging other issues.
83 |
84 | ## Coding Style and Best Practices 💻
85 |
86 | - Follow the [JavaScript Standard Style](https://standardjs.com/) for coding conventions.
87 | - Write clear and concise commit messages.
88 | - Ensure your code is well-documented and easy to understand.
89 | - Add screenshot in issue and pr description.
90 |
91 |
92 |
93 |
94 | ## Code of Conduct 📜
95 |
96 | By participating in this project, you agree to abide by the [Code of Conduct](CODE_OF_CONDUCT.md). Please treat everyone with respect and kindness.
97 |
98 | ---
99 |
100 | Thank you for contributing to the LinkedIn Resume Builder project! We appreciate your help in making it a better resource for everyone. If you have any questions, feel free to reach out!
101 |
102 |
--------------------------------------------------------------------------------
/Faqs.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
LinkedIn Resume Builder is a tool that allows users to create professional resumes quickly by importing their LinkedIn profile data and formatting it into a polished, job-ready document.
144 |
145 |
146 |
147 |
How can I use this tool?
148 |
You can use LinkedIn Resume Builder by signing in with your LinkedIn account, selecting the data you want to include in your resume, and choosing one of our pre-designed templates to generate your resume.
149 |
150 |
151 |
152 |
Is LinkedIn Resume Builder free to use?
153 |
Yes, LinkedIn Resume Builder offers free templates and tools to create your resume. However, premium templates and features may require a subscription.
154 |
155 |
156 |
157 |
Can I customize my resume?
158 |
Yes, you can customize your resume by editing the sections, changing the layout, and selecting different templates to fit your style and professional needs.
159 |
160 |
161 |
162 |
How do I download my resume?
163 |
Once you’ve completed your resume, you can download it in PDF format directly from the platform.
24 |
37 |
38 |
39 |
--------------------------------------------------------------------------------
/contributing.md:
--------------------------------------------------------------------------------
1 |
2 | # LinkedIn Resume Builder ✨
3 |
4 | This project is a LinkedIn Resume Builder that allows users to generate professional resumes from their LinkedIn profiles in just a few clicks. The website is designed with a clean and responsive UI using Bootstrap, focusing on simplicity and ease of use.
5 |
6 | ## Features 🚀
7 |
8 | - **Easy-to-Use Interface:** A user-friendly interface allows users to effortlessly create a resume.
9 | - **Instant Resume Generation:** Quickly build a resume by entering your LinkedIn profile URL.
10 | - **Secure Data:** Personal information is protected through encrypted communication 🔒.
11 | - **Responsive Design:** The website is mobile-first and adjusts seamlessly to different screen sizes 📱.
12 | - **24/7 Support:** Support is available around the clock to assist users 💬.
13 |
14 | ## Project Structure 📁
15 |
16 | The website consists of the following key sections:
17 |
18 | - **Navbar:** A top navigation bar with links to the homepage, resume builder, sign-up, and login pages.
19 | - **Hero Section:** A CTA section encouraging users to start building their resume.
20 | - **Features Section:** Highlights core features of the platform.
21 | - **Testimonials Section:** Displays user feedback and testimonials to boost credibility.
22 | - **Footer:** A simple footer providing basic information about the website.
23 |
24 | ## Technologies Used 💻
25 |
26 | - **HTML5:** Structure of the webpage.
27 | - **CSS3:** Styling and layout, using Google Font Roboto for typography.
28 | - **Bootstrap 4.5:** Ensures responsiveness and aesthetic appeal.
29 | - **JavaScript/jQuery:** Handles dynamic behavior.
30 |
31 | ## Screenshots 📸
32 |
33 | - **Desktop and Mobile View:** Available to preview on both desktop and mobile screens.
34 |
35 | ## Getting Started 🏁
36 |
37 | ### Prerequisites
38 |
39 | - A modern web browser (Chrome, Firefox, Safari, etc.)
40 | - Internet connection to load external resources (Bootstrap, fonts)
41 |
42 | ### Installation
43 |
44 | 1. **Clone the repository:**
45 | ```bash
46 | git clone https://github.com/your-username/linkedin-resume-builder.git
47 | cd linkedin-resume-builder
48 | ```
49 |
50 | 2. **Open the index.html file:**
51 | ```bash
52 | open index.html
53 | ```
54 |
55 | ### File Structure 📂
56 |
57 | ```plaintext
58 | ├── index.html # Main homepage
59 | ├── resume.html # Resume builder page
60 | ├── signup.html # Sign-up page
61 | ├── login.html # Log-in page
62 | ├── about.html # About page
63 | ├── Hero Section.jpg # Image displayed in the hero section
64 | ├── styles.css # Custom CSS styles (inlined in HTML)
65 | ```
66 |
67 | ## Developer Setup 🛠️
68 |
69 | For developers who want to contribute:
70 |
71 | 1. Clone the repository:
72 | ```bash
73 | git clone https://github.com/your-username/linkedin-resume-builder.git
74 | cd linkedin-resume-builder
75 | ```
76 |
77 | 2. Install necessary dependencies if applicable (e.g., Node.js, Python).
78 | 3. Run the development server:
79 | ```bash
80 | npm start
81 | ```
82 |
83 | ## Contributing 🤝
84 |
85 | We welcome contributions in various forms, including code, documentation, and feedback. Here’s how you can get started:
86 |
87 | ### How to Contribute
88 |
89 | 1. **Fork the Repository**
90 |
91 | Navigate to the [GitHub repository](https://github.com/your-username/linkedin-resume-builder) and click **Fork** to create your copy.
92 |
93 | 2. **Clone Your Fork**
94 |
95 | ```bash
96 | git clone https://github.com/your-username/linkedin-resume-builder.git
97 | cd linkedin-resume-builder
98 | ```
99 |
100 | 3. **Create a Branch**
101 |
102 | ```bash
103 | git checkout -b feature/your-feature-name
104 | ```
105 |
106 | 4. **Make Changes**
107 |
108 | Implement changes or new features following the project's coding style.
109 |
110 | 5. **Commit Your Changes**
111 |
112 | ```bash
113 | git add .
114 | git commit -m "Add description of your changes"
115 | ```
116 |
117 | 6. **Push to Your Branch**
118 |
119 | ```bash
120 | git push origin feature/your-feature-name
121 | ```
122 |
123 | 7. **Open a Pull Request**
124 |
125 | In the original repository, click **Pull Requests** and submit a pull request with a detailed description of your changes.
126 |
127 | ### Reporting Issues
128 |
129 | If you encounter issues, please report them in the [Issues section](https://github.com/your-username/linkedin-resume-builder/issues) with a detailed description.
130 |
131 | ### Code of Conduct
132 |
133 | By participating in this project, you agree to adhere to a respectful and inclusive code of conduct.
134 |
135 | ## Usage 📄
136 |
137 | - **Home Page:** Introduces users to the service with a description and CTA button.
138 | - **Build Resume:** Users enter their LinkedIn URL to create a resume.
139 | - **Sign-Up/Login:** Users can create an account or log in to manage their resume.
140 | - **Features & Testimonials:** Displays platform features and user feedback.
141 |
142 | ## Responsive Design 📏
143 |
144 | This project uses Bootstrap’s grid system to ensure full responsiveness across screen sizes, with additional media queries for layout fine-tuning on mobile devices.
145 |
146 | ## Thank You!
147 |
148 | Thank you for contributing to the LinkedIn Resume Builder! Your contributions help us build a better tool for users. Happy coding!
149 |
150 | ---
151 |
152 | **Screenshot Discord Link:** [Join Discord](https://discord.gg/GJ5BfwVd)
153 | ```
154 |
155 | Replace `your-username` in the GitHub links with the actual username if this will be published in your repository. This combined format keeps everything accessible in a single file for simplicity and easy access for contributors.
156 |
--------------------------------------------------------------------------------
/cv.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
100 |
101 |
102 |
We at Resum-Resume value your privacy and are committed to protecting your personal information. This privacy policy outlines how we collect, use, store, and share your information when you use our resume generation service.
16 |
17 |
Information We Collect
18 |
When you use our service, we may collect the following types of information:
19 |
20 |
Personal Information: This includes your name, email address, LinkedIn profile URL, and any other data you provide when using our service to generate a resume.
21 |
Usage Data: We may collect information about how you use our website, such as your IP address, browser type, pages visited, and the time spent on each page to help improve our service.
22 |
23 |
24 |
How We Use Your Information
25 |
We use the information collected in the following ways:
26 |
27 |
Resume Generation: Your LinkedIn profile data is used solely to create your customized resume. This information is not stored or shared with any third-party services.
28 |
Service Improvement: Usage data helps us understand how users interact with our website, allowing us to enhance the user experience and make improvements to our service.
29 |
Communication: We may use your email address to communicate with you about updates, new features, or changes to our terms and privacy policy.
30 |
31 |
32 |
Data Storage and Security
33 |
Your data is processed in real-time for the sole purpose of generating a downloadable resume. We do not store your LinkedIn profile information or any data entered in the resume generation process on our servers.
34 |
We implement industry-standard security measures to protect your information from unauthorized access, disclosure, alteration, or destruction. However, please note that no method of transmission over the internet is 100% secure, and we cannot guarantee absolute security.
35 |
36 |
Sharing Your Information
37 |
We do not sell, trade, or rent your personal information to third parties. Your data is used exclusively for generating the resume as requested. We may share non-personal, aggregated information with third-party analytics providers to help us understand how users engage with our website.
38 |
39 |
Your Rights
40 |
You have the following rights regarding your personal information:
41 |
42 |
Access: You have the right to request access to the personal information we hold about you.
43 |
Correction: If you believe that any of the information we hold about you is incorrect or incomplete, you can request corrections.
44 |
Deletion: You may request the deletion of your personal information that we process if it is no longer necessary for the purpose for which it was collected.
45 |
46 |
47 |
Cookies and Tracking Technologies
48 |
We may use cookies and similar tracking technologies to collect and store information about your usage of our website. Cookies help us provide a better user experience by remembering your preferences and analyzing how our service is used. You can adjust your browser settings to disable cookies, but this may affect the functionality of our website.
49 |
50 |
Third-Party Links
51 |
Our website may contain links to third-party websites. Please be aware that we are not responsible for the privacy practices of these external sites. We encourage you to read the privacy policies of any third-party websites you visit.
52 |
53 |
Changes to This Policy
54 |
We reserve the right to update or modify this privacy policy at any time. Any changes will be effective immediately upon posting the revised policy on this page. We encourage you to review this privacy policy periodically to stay informed about how we are protecting your information.
55 |
56 |
Contact Us
57 |
If you have any questions, concerns, or feedback regarding this privacy policy or our practices, please contact us at support@resume.com. We are here to help and will do our best to address your inquiries promptly.
336 | Welcome to Resum Resume. We are committed to protecting your privacy and ensuring that your personal information is handled responsibly. This Privacy Policy outlines how we collect, use, and protect your information when you visit our website and use our services.
337 |
338 |
339 |
340 |
Information We Collect
341 |
Personal Information
342 |
343 |
344 |
Name
345 |
Email address
346 |
Phone number
347 |
Address
348 |
Work history
349 |
Education details
350 |
Other information you choose to provide
351 |
352 |
353 |
Non-Personal Information
354 |
355 |
356 |
Browser type
357 |
IP address
358 |
Device information
359 |
Pages visited
360 |
Time spent on our site
361 |
Referral source
362 |
363 |
364 |
How We Use Your Information
365 |
366 | We may use your information for the following purposes:
367 |
368 |
369 |
To provide and maintain our services.
370 |
To communicate with you, including responding to inquiries and providing customer support.
371 |
To send you updates, newsletters, and marketing materials (you can opt-out at any time).
372 |
To analyze usage and trends to enhance user experience
373 |
374 |
Third-Party Links
375 |
Our website may contain links to third-party websites. We do not control these sites and are not responsible for their content or privacy practices. We encourage you to review the privacy policies of any third-party sites you visit.
376 |
377 |
Data Security
378 |
We take reasonable measures to protect your information from unauthorized access, disclosure, alteration, and destruction. However, no method of transmission over the internet or electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your personal information, we cannot guarantee its absolute security.
379 |
Changes to This Privacy Policy
380 |
381 | We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on our website with a new effective date. We encourage you to review this Privacy Policy periodically for any updates.
382 |
Comments
12 | 13 | 17 | 18 |