Privacy Policy

1. Introduction

MonetizerEngine Portal ("Portal", "we", "our", "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our portal at portal.monetizerengine.com.

Please read this privacy policy carefully. If you do not agree with the terms of this privacy policy, please do not access the Portal.

2. Information We Collect

Personal Information

We may collect personal information that you voluntarily provide when using our Portal, including:

• Name and contact information (email, phone number)
• Business information (company name, website, address)
• Account credentials
• Payment information (processed securely through Stripe)

Third-Party Platform Data

When you connect third-party accounts, we access data from these platforms based on the permissions you grant:

• Social media profiles and posts
• Analytics and performance metrics
• Comments, messages, and engagement data
• Business profile information

Automatically Collected Information

We automatically collect certain information when you visit the Portal:

• Device and browser information
• IP address and location data
• Usage patterns and interactions
• Cookies and similar tracking technologies

3. YouTube API Services

Our Portal uses YouTube API Services. By using our YouTube integration features, you are also agreeing to be bound by the YouTube Terms of Service.

YouTube Data We Access

• Channel information (name, description, subscriber count)
• Video details (titles, descriptions, thumbnails, view counts)
• Comments on your videos
• Analytics data (views, watch time, audience demographics)

How We Use YouTube Data

• Display your channel performance metrics in our dashboard
• Manage and respond to comments on your behalf
• Generate analytics reports and insights
• Publish content to your channel (with your authorization)

YouTube Data Storage & Refresh

We store YouTube API data to provide our services. This data is:

• Refreshed: At least every 30 days to ensure accuracy
• Deleted: Upon your request or account termination
• Secured: Using industry-standard encryption

Revoking YouTube Access

You can revoke our access to your YouTube data at any time by:

• Disconnecting YouTube in your Portal Settings
• Visiting your Google Security Settings to manage third-party app access
• Contacting us at info@monetizerengine.com

4. Meta (Facebook & Instagram) Services

4.1 Which app this covers

This section covers the Meta app monetizerengine, owned and operated by Monetizer Engine Inc. and used by the MonetizerEngine Portal at portal.monetizerengine.com. It connects accounts two ways: Facebook Login for Business (for Facebook Pages and the Instagram Professional accounts linked to them) and Instagram Business Login (for Instagram Professional accounts connected directly).

You connect your own Facebook Page or Instagram Business account to the Portal. We act on your behalf and only within the permissions you grant. We never connect an account you do not administer, and we do not access any Meta account that has not been explicitly connected through the Portal.

4.2 Permissions we request, and why

Requested when you connect through Facebook Login for Business:

• email: identify the Portal user who linked the account.
• pages_show_list: show the Pages you administer so you can choose which to connect.
• pages_manage_posts: publish and schedule posts to the connected Page when you instruct us to.
• pages_read_engagement: read likes, shares and reach for your dashboard and reports.
• pages_manage_engagement: reply to, hide and delete comments on the connected Page's posts.
• pages_manage_metadata: subscribe the Page to our webhooks so new comments and messages arrive in near real time.
• pages_messaging: read and send Messenger messages for the connected Page.
• pages_messaging_subscriptions: receive Messenger events outside the standard messaging window.
• pages_read_user_content: read comments and posts that other people leave on the connected Page.
• business_management: list Pages owned through a Meta Business Manager. Without this, an agency or multi-location user only sees Pages where they are a direct admin, and Pages held in a Business Manager are invisible to them. We use it solely to enumerate the Pages you already administer so you can pick one to connect.
• instagram_basic: read the connected Instagram Business account profile: username, profile picture and follower counts.
• instagram_content_publish: publish images, videos and reels to the connected Instagram Business account.
• instagram_manage_insights: read reach, impressions and audience insights for reporting.
• instagram_manage_comments: read, reply to, hide and delete comments on the account's media.
• instagram_manage_messages: read and send Instagram Direct messages for the connected account.

Requested when you connect through Instagram Business Login:

• instagram_business_basic: read the connected account profile.
• instagram_business_content_publish: publish content you schedule in the Portal.
• instagram_business_manage_comments: read, reply to, hide and delete comments.
• instagram_business_manage_messages: read and send Instagram Direct messages.
• instagram_business_manage_insights: read reach, impressions and audience insights.

4.3 Meta data we store

• Connected account record: platform user ID, Instagram Business account ID, username, display name, profile picture URL, follower / following / post counts, the OAuth access token and its expiry, and the time we last synced.
• Comments: comment text, author ID, author name, author username, author profile picture URL, like count, hidden and deleted flags, any reply we sent and when, and the post permalink and thumbnail URL.
• Direct messages: participant ID, participant name, participant profile picture URL, message text, direction, Meta's message ID and timestamps.
• Post performance: views, likes, comments, shares, saves, clicks, reach and impressions for content published through the Portal.

We do not receive or store payment details, government identifiers, precise location, or any special-category personal data from Meta.

4.4 How we use Meta data

• Display your social media performance in your dashboard and reports.
• Show comments and direct messages in one inbox so you can respond.
• Schedule and publish posts on your behalf.
• Automatically hide or delete comments that match moderation rules you configure.
• Draft or send automated replies to comments and direct messages, when you enable that feature.

4.5 AI processing of comments and messages

To classify intent and sentiment and to draft suggested replies, the text of comments and direct messages is sent to the Claude API operated by Anthropic PBC. Anthropic processes this text as our service provider under its commercial terms and does not use it to train its models. See Anthropic's Privacy Policy.

Our other processors for this data are infrastructure providers: Amazon Web Services (hosting, United States) and Cloudflare (content delivery and security). Payment processing is handled by Stripe, which never receives Meta data. We do not sell Meta data and we do not share it with advertising networks or data brokers.

4.6 How long we keep it

• Access tokens: kept while the account is connected. Deleted when you disconnect, when Meta calls our deauthorize callback, or when your account is closed.
• Comments and direct messages: kept while your account is active so the inbox and reporting work. Deleted within 30 days of a deletion request, a deauthorize callback, or account closure.
• Insights and metrics: refreshed at least every 30 days. Data that can no longer be refreshed is removed.

4.7 How to revoke our access

• Disconnect the account in the Portal under Social Media settings.
• Remove the app in Facebook Settings → Apps and Websites.
• Remove the app in Instagram Settings → Apps and Websites.
• Email us at info@monetizerengine.com.

4.8 Deleting your Meta data

When you remove our app from your Facebook or Instagram account, Meta automatically notifies us and we delete the data described in section 4.3. You can also request deletion directly. Our endpoints are:

• Deauthorize callback: https://portal.monetizerengine.com/api/social-media/auth/deauthorize
• Data deletion request callback: https://portal.monetizerengine.com/api/social-media/auth/data-deletion
• Instructions and status lookup: https://portal.monetizerengine.com/data-deletion

A deletion request returns a confirmation code. You can check the status of that request at any time by entering the code on our data deletion page.

4.9 Meta's own terms

Your use of Facebook and Instagram remains governed by Facebook's Terms of Service, Instagram's Terms of Use, and Meta's Privacy Policy.

5. TikTok Services

Our Portal integrates with TikTok to provide video publishing and analytics features. By using our TikTok integration, you agree to TikTok's Terms of Service.

TikTok Data We Access

• Profile information (username, display name)
• Video posting capabilities
• Engagement metrics

TikTok Content Disclosure

When posting to TikTok through our Portal, you must comply with TikTok's content guidelines and properly disclose any branded or commercial content as required by TikTok's policies.

6. Google Calendar, Business Profile, Analytics, Search Console and Other Google Services

This section covers the Google data the Portal can access when you sign in with Google and choose to connect a Google account. It applies in addition to section 3 (YouTube). We only access a Google service after you connect it and grant the permission on Google's own consent screen, and we only use it for the feature you connected it for.

6.1 Google Calendar

The Portal hosts online booking pages for local service businesses (for example salons, spas, clinics and fitness studios). A staff member at one of these businesses can connect their own Google Calendar so that customer bookings and their personal schedule stay in sync. We request two Calendar permissions:

• calendar.freebusy (view your availability in your calendars): before a booking page offers a time, we ask Google whether the staff member is busy at that time on their primary calendar, or on the calendars they choose, so a customer cannot book over an existing commitment. Google returns only the start and end time of each busy period. We never receive event titles, descriptions, locations or attendees.
• calendar.events.owned (see, create, change and delete events on Google calendars you own): when a customer books, reschedules or cancels an appointment with that staff member, we create, update or delete that one appointment event on their calendar so it appears on their phone. The event we write contains the service name, the customer's first name and last initial, and the start and end time. We only change events that the Portal itself created. We do not read, change or delete any other event on the calendar.

What we store: the Google account email address, the encrypted access and refresh tokens and their expiry, which calendars to check for busy time and which calendar to write bookings to, the connection status and the time of the last sync. Busy periods are held in server memory for a few minutes to show available times and are not written to our database. We do not store the contents of any calendar event.

6.2 Google Business Profile

With the business.manage permission we read and manage the Business Profile listings you connect: business information (name, address, phone, hours, categories, services, website), reviews and your replies to them, posts, photos, and performance insights. We use it to show your listing's health and performance, to publish posts and photos you approve or schedule, to reply to reviews when you approve a reply or turn on automatic replies, and to update listing details when you ask us to.

6.3 Google Analytics and Google Search Console

With analytics.readonly we read traffic, engagement and conversion reports for the website properties you connect. With webmasters and webmasters.readonly we read search performance (search queries, clicks, impressions, position) and indexing status for the sites you have verified, and submit your website's sitemap. We use this data to show your website and search performance in your dashboard and reports, and to choose blog topics that match what people search for.

6.4 Google Drive and Google sign-in

• drive.file: when you choose files from Google Drive to upload to your media library, we receive only the files you pick in Google's file picker. We copy those files into your media library and do not keep the Drive token.
• Email address and basic profile (userinfo.email, userinfo.profile): used to show which Google account is connected and to link the connection to your Portal account.

6.5 How we use Google user data, and what we never do

• We use Google user data only to provide and improve the user-facing features described above, which you can see in the Portal.
• We do not sell Google user data.
• We do not use or transfer Google user data for advertising, including retargeting, personalized or interest-based advertising.
• We do not use Google user data to determine creditworthiness or for lending purposes.
• We do not use Google user data, including data from Google Workspace APIs such as Google Calendar, to develop, improve or train generalized artificial intelligence or machine learning models.
• Our staff do not read your Google user data unless you ask us to (for example in a support request), it is needed for security purposes such as investigating abuse, it is required by law, or the data has been aggregated and anonymized for internal operations.

6.6 AI features

Some features use AI to draft content for you to review or to send on your behalf when you turn that on: a reply to a Google review, a Business Profile post, or blog topics based on your Search Console and Business Profile search terms. For these features the relevant text is sent to our AI service providers (Anthropic, OpenAI and Google Gemini). They process it only to return the result to us, under API terms that do not allow them to use it to train their models. Google Calendar data is never sent to an AI provider. When a business uses our AI text assistant to offer a customer appointment times, the open times are calculated after busy times are removed; the busy times themselves are not shared.

6.7 Who we share Google user data with

We share Google user data only with the service providers that run the Portal for us: Amazon Web Services (hosting and database, United States), Cloudflare (network security and content delivery) and the AI providers named in section 6.6. They process it on our behalf under contract. The appointment details we write to a staff member's calendar are visible to that staff member and anyone they share their calendar with. We may also disclose data when required by law, or as part of a merger or acquisition with notice to you. We do not share Google user data with anyone else.

6.8 How we protect it

Google access and refresh tokens are encrypted at rest with AES-256-GCM and are never shown in the Portal. All data is encrypted in transit with TLS. Access to production systems is limited to authorized staff, and each business can only see its own data.

6.9 How long we keep it and how to delete it

• Google Calendar: tokens are kept while the calendar is connected and are deleted as soon as you click Disconnect, or when the staff member is removed from the business's team. Busy periods are never stored. Appointment events we created stay on your calendar until you delete them.
• Business Profile, Analytics and Search Console: tokens are kept while the account is connected. Reports and metrics are refreshed regularly and kept while your Portal account is active so your history and reports keep working.
• All Google user data is deleted within 30 days of your request, including a request to close your Portal account.

To revoke our access at any time, disconnect the account in the Portal, or remove MonetizerEngine from your Google Account connections. To ask us to delete your data, email info@monetizerengine.com.

6.10 Google API Services User Data Policy (Limited Use)

Monetizer Engine's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

7. Cookies and Tracking Technologies

We use cookies and similar tracking technologies to track activity on our Portal and store certain information. Cookies are files with a small amount of data which may include an anonymous unique identifier.

Types of Cookies We Use

• Essential Cookies: Required for the Portal to function properly
• Authentication Cookies: To keep you logged in
• Analytics Cookies: To understand how you use our Portal
• Preference Cookies: To remember your settings

You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use some portions of our Portal.

8. How We Use Your Information

We use the information we collect to:

• Provide, operate, and maintain our Portal
• Improve, personalize, and expand our services
• Understand and analyze how you use our Portal
• Develop new products, services, features, and functionality
• Communicate with you for customer service and support
• Send you updates, marketing communications, and promotional information
• Process your transactions and manage your account
• Find and prevent fraud and abuse

Data we receive from Google APIs is used only as described in sections 3 and 6. It is never used for marketing, promotional messages or advertising.

9. How We Share Your Information

We may share your information in the following situations:

• With Service Providers: To help us provide our services (hosting, analytics, payment processing)
• With Third-Party Platforms: When you authorize us to post or manage content on your connected accounts
• For Legal Compliance: If required by law or to protect our rights
• Business Transfers: In connection with any merger, acquisition, or sale of assets

We do NOT sell your personal information to third parties.

10. Data Security

We implement appropriate technical and organizational security measures to protect your personal information, including:

• Encryption of data in transit and at rest
• Secure access controls and authentication
• Regular security assessments and updates
• Employee training on data protection

11. Data Retention

We retain your personal information for as long as necessary to provide our services and fulfill the purposes described in this policy, unless a longer retention period is required or permitted by law.

For third-party API data (YouTube, Facebook, etc.), we:

• Refresh data at least every 30 days
• Delete data upon your request
• Remove stale data that can no longer be refreshed

12. Your Privacy Rights

Depending on your location, you may have the following rights:

• Access: Request a copy of your personal data
• Correction: Request correction of inaccurate data
• Deletion: Request deletion of your personal data
• Portability: Request transfer of your data to another service
• Objection: Object to certain processing of your data
• Withdrawal: Withdraw consent at any time

To exercise these rights, contact us at info@monetizerengine.com.

13. Children's Privacy

Our Portal is not intended for individuals under the age of 18. We do not knowingly collect personal information from children. If you become aware that a child has provided us with personal information, please contact us immediately.

14. International Data Transfers

Your information may be transferred to and processed in countries other than your country of residence. These countries may have data protection laws that are different from the laws of your country. We take steps to ensure your data receives adequate protection in accordance with applicable law.

15. Changes to This Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date at the top of this policy.

You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.

16. Contact Us

If you have any questions about this Privacy Policy, please contact us: