Who we are and how to contact us
MSP Service Index is an early-stage independent initiative operated by Steve Wilson, based in Auckland, New Zealand. This is not a representation that MSP Service Index is an incorporated legal entity or has a registered office.
For general enquiries, privacy questions or requests about your application, email hello@mspserviceindex.com.
Information collected in a Founding 100 application
- First name, last name, business email address and role.
- MSP company name and country.
- PSA platform, its name if you select “Other”, and approximate number of service desk engineers.
- Your stated willingness to consider contributing limited monthly operational data, subject to acceptable arrangements.
- Optional free-text benchmarking interests. Please do not include customer details or sensitive operational information.
- The privacy notice version accepted, the acceptance timestamp, and a separate optional marketing choice and timestamp when opted in.
- Available campaign parameters (UTM source, medium, campaign, content and term) and referral or landing-page information.
We also assign an application identifier and creation time. Authorized administrators can record a recruitment status and private follow-up notes. A hidden spam-check field and elapsed form-completion time are checked during submission; these are not saved as application fields.
No PSA credentials, API tokens, customer lists, tickets, ticket exports or operational datasets are collected through this application. Applying is not a commitment to share operational data.
Purpose and separate consent choices
We use application information to assess and contact you about Founding 100 participation, understand demand, plan the proposed methodology and prioritize possible PSA integrations. We require the application-processing checkbox before submission and record its acceptance with the notice version and a server timestamp. Declining means the application cannot be submitted; you may still contact us by email.
The optional marketing checkbox is separate and unselected by default. If selected, we record the opt-in and its timestamp for occasional MSP Service Index research and programme updates. Otherwise we record no marketing opt-in timestamp. You can withdraw this opt-in by emailing us, or using an unsubscribe option where provided. Recruitment follow-up about your application is distinct from optional marketing.
Neither application consent nor marketing opt-in gives permission for advertising tracking, PSA access or future data licensing. The legal basis and any additional notices required under the laws applicable to individual applicants remain subject to owner review.
Service providers and third-party processing
Lovable supplies our website platform and Lovable Cloud supplies application storage and administrator authentication. Application details and access information are processed by these services to operate the site. Google Workspace is used for the contact mailbox: if you email us, Google processes the message, your sender details and any attachments for email delivery and storage.
After an application is stored, a receipt is sent through Lovable's managed email service from noreply@notify.mspserviceindex.com, with replies directed to hello@mspserviceindex.com. That provider renders and delivers the message, checks its own bounce, complaint and unsubscribe suppression before sending, and appends its unsubscribe footer to every message it sends. The receipt contains no answers you typed into the application form.
Google Tag Manager is installed to manage optional Google Analytics 4 and LinkedIn Insight tags. These vendor tags may process visit and event information if and when activated in the external container, under the applicable consent settings. The website does not install separate Google Analytics or LinkedIn scripts. Their actual published tag configuration must also respect the consent signals; that configuration is managed separately from this website.
Google Fonts supplies the Inter font through requests from your browser to Google. Those requests expose connection information, including your IP address and browser request details, to Google. Hosting, email, authentication and other providers may also process IP addresses or service logs. The cookie-free visit-counting statements below apply only to Lovable's visitor analytics, not to every provider or every hosting log.
See Lovable's privacy policy, Google's privacy policy and LinkedIn's privacy policy for their processing information. Provider locations, contractual safeguards and any international transfer mechanisms have not been verified for this notice. Processing may involve countries outside New Zealand or your country; we do not claim a particular storage region, transfer mechanism or data-residency guarantee.
Retention and security
Applications are retained while Founding 100 recruitment runs, with periodic review of whether they are still needed. Deletion and withdrawal requests are handled by the operator. There is no automated application-deletion schedule, and no fixed deletion deadline is promised here. When recruitment ends, the operator should review remaining applications and remove those no longer needed; any further retention reason should be explained to the applicant.
Public visitors cannot read or edit stored applications. Administrator access requires an authorized account and two-step verification. Server-side validation and submission rate limiting help protect the form. These controls do not guarantee absolute security, and no security certification is claimed.
Practical privacy requests
Email hello@mspserviceindex.com to ask for a copy of your application, correct it, request deletion, withdraw your application or stop optional updates. Identify the email used to apply; do not send a password or PSA credentials. We may need to verify that the request concerns your information before disclosing or changing it.
Rights, response deadlines and complaint options vary by jurisdiction. If a request cannot be fulfilled in full, we will explain the reason and any information that must be retained. You may also raise concerns with the privacy authority applicable to you.
Cookies, browser storage and measurement
Lovable visitor analytics
Lovable's visitor analytics uses no cookies, stores nothing on your device, does not keep IP addresses and does not identify visitors. It records the pages visited, where visitors came from, country, browser, operating system and device type, time on site, page-load speed, errors, and clicks on buttons and links. Lovable collects this data for us. Lovable's privacy policy explains how it handles it. Detailed data is kept for 90 days and daily summaries for a year.
For visitors in the EU/EEA, the UK, Switzerland, Canada and where location cannot be determined, clicks wait until analytics is accepted. Elsewhere clicks are recorded unless the visitor rejects analytics. Clicks are never recorded when the browser sends Global Privacy Control, even after acceptance. Page visits, time on page, page speed and errors are recorded for every visitor, without cookies and without identifying anyone.
Google and LinkedIn tags managed through Tag Manager
The website pushes public page details, approved non-personal campaign codes, form starts, Join clicks, submission failures and successful saved-application events to Tag Manager's dataLayer. Applicant names, emails, company names, phone numbers and free-text answers are not included in these events. A successful-application event is sent once after storage succeeds, never on a Join click or a failed submission. These events are separate from Lovable's visitor analytics.
When enabled and permitted, GA4 and LinkedIn tags may use cookies or other identifiers for analytics, conversion measurement, advertising attribution, audience insights or remarketing. These identifiers are not necessarily anonymous. LinkedIn's tag may receive page URLs, referrers, IP addresses and browser/device information; Google tags may process similar visit and connection information. No applicant details should be added to tags or used for enhanced conversions.
Consent Mode defaults run before Tag Manager. Google defaults deny analytics and advertising storage in the EU/EEA, UK, Switzerland and Quebec, and grant them elsewhere unless an explicit choice or Global Privacy Control overrides this. The website's subsequent location check denies unanswered analytics and advertising permissions throughout Canada and where location cannot be verified, as well as in the other opt-in regions. LinkedIn tags must gate every send on the website's advertising permission. Google Consent Mode can allow cookieless measurement signals while storage is denied; rejecting cookies does not mean no connection data reaches Google.
Advertising and analytics choices are separate. Explicit choices update signals without a reload; Global Privacy Control overrides acceptance. Cookie settings in the footer let you change your choices. Accepted choices expire after 365 days; refusals can prompt a new choice after 183 days but remain effective until changed. Application events blocked by correctly configured tags must not be replayed later.
Other browser storage and abuse prevention
The site saves consent choices in local storage, and campaign/referral attribution for application sourcing for up to 30 days. A new campaign link replaces earlier stored attribution. Expired attribution is ignored; this is not a promise of automatic erasure from your browser. Administrator authentication also stores session information in the browser.
For rate limiting, the submission service hashes the connection IP address with SHA-256 and stores the hash and attempt time separately from applications. This is pseudonymous abuse-prevention data, not fully anonymous data. Attempts older than 24 hours are pruned when subsequent valid submissions run the cleanup; without further submissions they may remain longer. No scheduled deletion job is claimed.
Future operational data programme
This notice covers applications and this website, not an active PSA data programme. Any future monthly snapshots, longitudinal analysis or licensed aggregated data products would require separate detailed disclosures, permissions and participation arrangements before operational data is collected. Read our Data Principles.