Privacy Policy

Effective Date: [Insert Date]

Introduction

Welcome to SendUnlimitedEmail.com (“we,” “us,” or “our”). We are committed to protecting your privacy and ensuring the security of your personal information. This Privacy Policy outlines how we collect, use, store, and safeguard your information when you interact with our website (www.sendunlimitedemail.com) and our browser extensions, including BulkSMTP and any future extensions developed for platforms such as Google, Microsoft, and Google Pay.

By using our website and extensions, you consent to the practices described in this Privacy Policy.

Contact Information

• Postal Address:

  SENDUNLIMITEDEMAIL
  182-21 150th Avenue
  Springfield Gardens, NY 11413

• Email Address: [email protected]
• Support Email: [email protected]

Information Collection and Use

1. Information You Provide

When you use our browser extensions, particularly BulkSMTP, we may collect the following information:

• SMTP Configuration Details:
  • Host: The SMTP server address (e.g., smtp.gmail.com).
  • Port: The SMTP server port (e.g., 587 for TLS, 465 for SSL).
  • Username: Your SMTP username (typically your full email address).
  • Password: Your SMTP password or app-specific password.
  • Encryption Method: The type of encryption used (None, SSL, TLS).
• Test Email Details:
  • Recipient Email: The email address to which test emails are sent.
• Bulk Email Details:
  • Recipients: A list of email addresses to send bulk emails to.
  • Subject: The subject line of the email.
  • Body: The content of the email.

2. Information Automatically Collected

Our website may automatically collect certain information when you visit, such as:

• IP Address: For security and analytics purposes.
• Browser Type and Version: To ensure compatibility.
• Access Times: To analyze usage patterns.
• Pages Viewed: To improve website functionality and user experience.

Data Storage and Security

1. Storage

• Browser Extensions:
  • All SMTP configuration details are stored locally using Chrome’s chrome.storage.sync API. This ensures that your credentials are not transmitted to our servers and remain accessible only to you across your Chrome browsers.
• Website Data:
  • Information collected through your interactions with our website is stored securely on our servers and used solely for enhancing user experience and improving our services.

2. Security Measures

We implement robust security measures to protect your information:

• Encryption:
  • SMTP passwords are stored using secure encryption methods to prevent unauthorized access.
• Access Controls:
  • Only authorized personnel have access to sensitive information, and all employees are trained to handle data responsibly.
• Regular Audits:
  • We conduct regular security audits to identify and rectify potential vulnerabilities.

3. Data Retention

We retain your SMTP configuration details and bulk email logs as long as you continue to use our extensions. If you choose to uninstall the extension or delete your settings, all associated data will be permanently removed.

Data Sharing and Disclosure

We do not sell, trade, or otherwise transfer your personally identifiable information to outside parties. This does not include trusted third parties who assist us in operating our website or extensions, conducting our business, or servicing you, so long as those parties agree to keep this information confidential.

Exceptions:

• Legal Requirements:
  • We may disclose your information if required by law or in response to valid requests by public authorities.
• Protection of Rights:
  • To protect the rights, property, or safety of SendUnlimitedEmail.com, our users, or others.

User Rights

You have the right to:

• Access:
  • Request access to the personal information we hold about you.
• Correction:
  • Request correction of any inaccurate or incomplete information.
• Deletion:
  • Request deletion of your personal information, subject to certain exceptions.
• Objection:
  • Object to the processing of your personal information for specific purposes.

To exercise these rights, please contact us at [email protected].

Third-Party Services and Extensions

Our browser extensions, including BulkSMTP, may integrate with third-party services (e.g., SMTP providers). We are not responsible for the privacy practices of these third parties. We encourage you to review the privacy policies of any third-party services you use in conjunction with our extensions.

Children’s Privacy

Our services are not intended for use by individuals under the age of 13. We do not knowingly collect personal information from children under 13. If you believe we have inadvertently collected such information, please contact us to have it removed.

Changes to This Privacy Policy

We reserve the right to update or change our Privacy Policy at any time. Any changes will be effective immediately upon posting the revised policy on our website. Your continued use of our website and extensions after such changes constitutes your acceptance of the new Privacy Policy.

Additional Developer Information

As an individual developer, I am committed to maintaining transparency and ensuring the security and privacy of my users. Should you have any questions or concerns regarding this Privacy Policy or our data practices, please do not hesitate to contact me at [email protected].

Links to This Privacy Policy

• Website:
  • Privacy Policy
• Browser Extensions:
  • Each of our extensions, including BulkSMTP, includes a link to this Privacy Policy within their settings or help sections.

Compliance with Chrome Web Store Policies

This Privacy Policy ensures compliance with the Chrome Web Store Program Policies, particularly regarding data collection, storage, and usage. All scripts used within our extensions are hosted locally to comply with Manifest V3 requirements, and permissions requested are limited to those necessary for the extension’s functionality.

2. Hosting the Privacy Policy on Your Website

To integrate this Privacy Policy effectively across your website and future extensions, follow these steps:

a. Create a Dedicated Privacy Policy Page

1. Page Name and URL:
   • Page Name: Privacy Policy
   • URL: www.sendunlimitedemail.com/privacy-policy/
2. Implementation Steps:
   • Add a New HTML Page:
     • Create a new file named privacy-policy.html in your website’s root directory.
   • Content Placement:
     • Paste the revised Privacy Policy content into this file.
   • Ensure Accessibility:
     • Make sure the page is accessible via your website’s footer or main navigation menu.
   • Disable Crawling (If Necessary):
     • If you prefer the Privacy Policy page not to be indexed by search engines, add a noindex meta tag.

b. Preventing Google Crawling (Optional)

While it’s generally recommended to allow search engines to index your Privacy Policy for transparency and compliance, if you still wish to prevent Google from crawling this page, you can implement the following:

1. Add a noindex Meta Tag:
   html

   Copy code

   <!-- Inside the <head> section of privacy-policy.html -->
<meta name="robots" content="noindex, nofollow">

2. Update robots.txt:
   • Location: Place robots.txt in the root directory of your website.
   • Disallow Crawling of Privacy Policy:
     makefile

     Copy code

     User-agent: *
Disallow: /privacy-policy.html


   Note: Using both methods provides an added layer of assurance, but the meta tag is more effective if the page is linked from elsewhere.

c. Link the Privacy Policy in Your Extensions

Ensure that each of your browser extensions includes a link to the Privacy Policy within their UI. Here’s how:

1. Within popup.html and bulk_send.html:
   • Include a Link:
     html

     Copy code

     <!-- Example Link in popup.html and bulk_send.html -->
<div class="section">
<h3>About SendUnlimitedEmail</h3>
<p>SendUnlimitedEmail allows you to send bulk emails seamlessly using third-party SMTP services.</p>
<p>For more information or to purchase additional SMTP services, visit our <a href="https://sendunlimitedemail.com" target="_blank">website</a>.</p>
<p>Read our <a href="https://sendunlimitedemail.com/privacy-policy/" target="_blank">Privacy Policy</a> for more details.</p>
</div>

2. Within Extension Settings or Help Sections:
   • Add a “Privacy Policy” Link:
     • Include a clearly visible link labeled “Privacy Policy” that directs users to the dedicated Privacy Policy page on your website.

3. Addressing the “ReferenceError: Email is not defined” Issue

The error ReferenceError: Email is not defined indicates that the Email object from smtp.js isn’t available in the context where it’s being used. Here’s how to resolve this:

a. Ensure Correct Inclusion Order of Scripts

1. In popup.html and bulk_send.html:
   • Load smtp.js Before Your Main Script:
     html

     Copy code

     <!-- Correct Order in popup.html and bulk_send.html -->
<script src="smtp.js"></script>
<script src="popup.js"></script> <!-- or bulk_send.js -->

   • Why: The Email object must be defined before your main scripts attempt to use it.
2. Sample popup.html Structure:
   html

   Copy code

   <!-- src/popup.html -->
<!DOCTYPE html>
<html>
<head>
<title>BulkSMTP Settings</title>
<style>
/* Your CSS Styles */
</style>
</head>
<body>
<!-- Your HTML Content -->
<script src="smtp.js"></script>
<script src="popup.js"></script>
</body>
</html>


b. Verify smtp.js is Properly Hosted and Not Corrupted

1. Ensure Presence:
   • Confirm that smtp.js exists in the src/ directory of your extension.
2. Content Verification:
   • Open smtp.js and ensure it contains the full SMTP.js library without any incomplete code or syntax errors.
3. Download the Latest Version:
   • If unsure, re-download smtp.js from the SMTP.js Official Website and replace the existing file.

c. Check for Correct Script Paths

1. Relative Paths:
   • Ensure that the src attributes in your <script> tags correctly point to smtp.js.
2. Example:
   html

   Copy code

   <!-- Correct Script Paths -->
<script src="smtp.js"></script>
<script src="popup.js"></script>


d. Inspect Developer Console for Loading Errors

1. Open DevTools:
   • Popup:
     • Right-click on the BulkSMTP popup and select “Inspect”.
   • Bulk Send Interface:
     • Open the Bulk Send window and right-click inside it to select “Inspect”.
2. Check Console for Errors:
   • Look for errors related to loading smtp.js, such as:
     • Failed to load resource: net::ERR_FILE_NOT_FOUND
     • Syntax errors within smtp.js
3. Verify Email Object Availability:
   • In the Console, type Email and press Enter.
   • It should return the Email object, not undefined.

e. Test SMTP Functionality Independently

1. Create a Test HTML Page:
   html

   Copy code

   <!-- src/test_smtp.html -->
<!DOCTYPE html>
<html>
<head>
<title>SMTP Test</title>
<script src="smtp.js"></script>
<script>
function sendTestEmail() {
Email.send({
Host: "smtp.your-email.com",
Port: 587,
Username: "[email protected]",
Password: "yourpassword",
To: "[email protected]",
From: "[email protected]",
Subject: "Test Email",
Body: "This is a test email."
})
.then(message => alert(message))
.catch(error => alert(error));
}
</script>
</head>
<body>
<h1>SMTP Test</h1>
<button onclick="sendTestEmail()">Send Test Email</button>
</body>
</html>

2. Add test_smtp.html to manifest.json (if necessary):
   json

   Copy code

   "web_accessible_resources": [{
"resources": ["src/bulk_send.html", "src/test_smtp.html"],
"matches": ["https://mail.google.com/*"]
}],

3. Load and Test:
   • Load the Extension Unpacked:
     • Navigate to chrome://extensions/.
     • Enable Developer mode.
     • Click “Load unpacked” and select your BulkSMTP/ directory.
   • Access test_smtp.html:
     • Open a new tab and enter:
       perl

       Copy code

       chrome-extension://<your-extension-id>/src/test_smtp.html

     • Replace <your-extension-id> with your actual extension ID.
   • Send a Test Email:
     • Click “Send Test Email” and observe the alert for success ("OK") or error messages.
4. Analyze Results:
   • Success: If you receive the test email, smtp.js is functioning correctly.
   • Failure: Check the console for errors and verify SMTP credentials and network settings.

4. Integrating the Privacy Policy Across Extensions

To ensure consistency and compliance across all your current and future extensions, implement the following strategies:

a. Centralize the Privacy Policy

1. Single Source of Truth:
   • Maintain one comprehensive Privacy Policy that covers all your extensions and services.
   • This avoids redundancy and ensures consistency in information.
2. Accessible via Website:
   • Host the Privacy Policy on your website (www.sendunlimitedemail.com/privacy-policy/).
3. Linking from Extensions:
   • Within Extension UI:
     • Include a clearly visible link labeled “Privacy Policy” within the settings or help sections of each extension.
     • Example:
       html

       Copy code

       <p>Read our <a href="https://sendunlimitedemail.com/privacy-policy/" target="_blank">Privacy Policy</a> for more details.</p>

   • Within Extension Descriptions:
     • In the Chrome Web Store listing for each extension, include a link to the Privacy Policy.

b. Naming Conventions for Privacy Policy Pages

1. Unified Page Name:
   • Use a consistent naming convention for your Privacy Policy page to simplify linking.
   • Example: privacy-policy.html
2. URL Structure:
   • Example URL: www.sendunlimitedemail.com/privacy-policy/
3. Future Extensions:
   • Since all extensions share the same Privacy Policy, there’s no need for separate pages for each extension.

c. Ensuring the Privacy Policy Is Not Crawled (If Desired)

While it’s recommended to allow search engines to index your Privacy Policy for transparency and compliance, if you still prefer to prevent Google from crawling this page, follow these steps:

1. Add a noindex Meta Tag:
   html

   Copy code

   <!-- Inside the <head> section of privacy-policy.html -->
<meta name="robots" content="noindex, nofollow">


   Explanation: This instructs search engine crawlers not to index the page or follow any links on it.

2. Update robots.txt:
   • Location: Place robots.txt in the root directory of your website.
   • Disallow Crawling of Privacy Policy:
     makefile

     Copy code

     User-agent: *
Disallow: /privacy-policy.html


   Explanation: This tells all web crawlers not to access the privacy-policy.html page.

   Note: Using both methods provides an added layer of assurance, but the meta tag is more effective if the page is linked from elsewhere.

d. Including Privacy Policy Links in Future Extensions

Ensure that as you develop new extensions for platforms like Microsoft and Google Pay, each includes a link to the centralized Privacy Policy:

1. Within Extension Settings or Help Sections:
   • Example:
     html

     Copy code

     <p>For more information about our data practices, please read our <a href="https://sendunlimitedemail.com/privacy-policy/" target="_blank">Privacy Policy</a>.</p>

2. Within Extension Descriptions:
   • Chrome Web Store Listing:
     • Include the Privacy Policy link in the “Privacy Practices” section.

5. Final Steps and Recommendations

a. Update and Verify All Required Files

Ensure that all your extension files are correctly updated and include necessary links:

1. manifest.json:
   • Permissions: Only include storage.
   • Content Security Policy: Ensure all scripts are hosted locally.
   • Icons: Verify that all icon files are present and correctly referenced.
2. popup.html and bulk_send.html:
   • Script Order: Load smtp.js before your main scripts (popup.js, bulk_send.js).
   • Privacy Policy Link: Include a link to the Privacy Policy.
3. popup.js and bulk_send.js:
   • Error Handling: Ensure proper error handling and that the Email object is defined.
   • SMTP Configuration: Verify that SMTP settings are correctly saved and retrieved.
4. content.js and content.css:
   • Bulk Send Button: Ensure the “Bulk Send” button is injected correctly with proper styling.
5. smtp.js:
   • Local Hosting: Confirm that smtp.js is present in the src/ directory and is not being loaded from an external source.
6. Icons:
   • Presence: Ensure icon16.png, icon48.png, and icon128.png are in the icons/ directory.
   • Correct Paths: Verify that manifest.json points to the correct icon paths.

b. Thoroughly Test the Extension Locally

1. Load the Unpacked Extension:
   • Navigate to chrome://extensions/ in Chrome.
   • Enable Developer mode.
   • Click “Load unpacked” and select your BulkSMTP/ directory.
2. Functionality Testing:
   • SMTP Settings:
     • Enter valid SMTP credentials.
     • Save settings and ensure they persist.
   • Send Test Email:
     • Enter a recipient email and send a test email.
     • Check for success notifications and verify receipt.
   • Send Bulk Emails:
     • Use the “Bulk Send” button in Gmail to compose and send bulk emails.
     • Verify notifications and email delivery.
   • Error Handling:
     • Enter invalid SMTP settings or recipient emails to test error notifications.
3. Console Inspection:
   • Open DevTools for both the popup and bulk send interfaces.
   • Check for any console errors and resolve them accordingly.

c. Obfuscate JavaScript Files (Recommended for Security)

1. Purpose:
   • Protect your SMTP logic and credentials from being easily readable or reverse-engineered.
2. Tools:
   • JavaScript Obfuscator
   • UglifyJS
3. Steps:
   • Obfuscate Each JS File:
     • Run popup.js, bulk_send.js, and content.js through the obfuscator.
   • Replace Original Files:
     • Replace the original JavaScript files in the src/ directory with the obfuscated versions.
   • Test Functionality:
     • Reload the extension and ensure all functionalities work as expected.

d. Final Compliance Check

1. Review Chrome Web Store Program Policies:
   • Ensure that your extension adheres to all Chrome Web Store Program Policies.
2. Manifest V3 Migration Checklist:
   • Follow the Manifest V3 Migration Checklist to ensure full compliance.
3. Privacy Policy Accessibility:
   • Confirm that the Privacy Policy is easily accessible within each extension and on your website.
4. Permissions Audit:
   • Double-check that only necessary permissions are requested in manifest.json.

e. Resubmit Your Extension

Once all updates are made and thoroughly tested:

1. Prepare for Submission:
   • Ensure all files are correctly packaged.
   • Verify that no external scripts are referenced.
   • Confirm that all policies are adhered to.
2. Submit for Review:
   • Navigate to the Chrome Web Store Developer Dashboard.
   • Upload the updated extension package.
   • Provide all necessary details, including screenshots and accurate descriptions.
3. Monitor Review Status:
   • Keep an eye on your email for any feedback or additional requests from the Chrome Web Store team.

6. Additional Developer Information Integration

To enhance user trust and provide comprehensive information about your services, integrate the following into your website and extensions:

a. Update popup.html and bulk_send.html with Developer Info

Include an “About” section that provides users with information about the extension and links to your website for additional services.

Example:

b. Create an “About” Page on Your Website

Provide users with detailed information about your services, commitment to privacy, and how they can obtain additional services.

Sample “About” Section:

c. Ensure Clear Privacy and Support Information

• Privacy Policy:
  • Ensure the Privacy Policy is easily accessible and clearly linked within all extensions and your website.
• Support Channels:
  • Provide clear and accessible support channels, such as a dedicated support email ([email protected]), to assist users with any issues or inquiries.

7. Summary of Actions Taken

1. Revised Privacy Policy:
   • Expanded to cover multiple extensions and future developments.
   • Included developer information and links to your website.
   • Ensured compliance with Chrome Web Store policies.
2. Hosted Privacy Policy Locally:
   • Created a dedicated privacy-policy.html page on your website.
   • Implemented noindex meta tag and robots.txt directives if you choose to prevent crawling.
3. Updated Extension Files:
   • manifest.json: Removed unused permissions and ensured CSP compliance.
   • popup.html and bulk_send.html: Removed external script references, included local smtp.js, and added Privacy Policy links.
   • popup.js and bulk_send.js: Ensured correct script loading order and handled the Email object definition.
   • content.js and content.css: Verified the injection of the “Bulk Send” button and its styling.
   • background.js: Managed extension background tasks and popup window creation.
4. Resolved “Email is not defined” Error:
   • Ensured smtp.js is correctly hosted and loaded before main scripts.
   • Verified script paths and loading order.
   • Tested SMTP functionality independently.
5. Integrated Privacy Policy Across Extensions:
   • Centralized Privacy Policy on your website.
   • Linked the Privacy Policy within each extension’s UI.
   • Implemented measures to prevent crawling if desired.
6. Recommended Obfuscation:
   • Suggested obfuscating JavaScript files to protect SMTP logic and credentials.
7. Final Compliance and Testing:
   • Advised thorough local testing.
   • Ensured all compliance measures are met before resubmission.

8. Final Recommendations

1. Prioritize Security:
   • Protect SMTP Credentials: Ensure that sensitive information like SMTP usernames and passwords are securely stored and never exposed.
   • Obfuscate Code: Use obfuscation tools to make your JavaScript code harder to reverse-engineer.
2. Enhance User Trust:
   • Transparent Privacy Practices: Clearly communicate how user data is handled through a comprehensive Privacy Policy.
   • Accessible Support: Provide reliable and easily accessible support channels.
3. Ensure Compliance:
   • Regular Policy Reviews: Stay updated with Chrome Web Store policies and adjust your extension accordingly.
   • Consistent Testing: Regularly test your extension to ensure all functionalities work seamlessly and securely.
4. Plan for Future Extensions:
   • Scalable Privacy Policy: Ensure that your Privacy Policy is adaptable to encompass future extensions without requiring significant overhauls.
   • Consistent User Experience: Maintain a consistent design and user experience across all extensions for brand cohesion.

Final Steps Before Resubmission

1. Implement All Updates:
   • Replace existing files with the updated code provided.
   • Ensure all new files (e.g., privacy-policy.html) are correctly placed and linked.
2. Thoroughly Test the Extension:
   • Load the unpacked extension in Chrome.
   • Test all functionalities, including SMTP settings, sending test emails, and sending bulk emails.
   • Verify that the Privacy Policy link is functional and accessible.
3. Verify Compliance:
   • Review all changes against the Chrome Web Store Program Policies.
   • Ensure that the Privacy Policy is accessible and accurately reflects your data practices.
4. Secure Your Credentials:
   • Double-check that SMTP credentials are securely stored and not exposed in any part of the extension or code repositories.
5. Prepare for Resubmission:
   • Package the extension with all updated files.
   • Ensure that no external scripts are referenced.
   • Provide accurate descriptions and screenshots in the Chrome Web Store listing.
6. Submit the Extension:
   • Navigate to the Chrome Web Store Developer Dashboard.
   • Upload the updated extension package.
   • Fill in all required fields, including the Privacy Policy link.
7. Monitor Submission:
   • Keep an eye on your email and the developer dashboard for any feedback or further instructions from the Chrome Web Store team.