Legal
Privacy policy
Last updated September 2026.
Who we are
MedTech Signal is operated by Rubicon Microproducts Inc. (info@rubiconmp.com). It is a regulatory intelligence workspace for medical-device teams. The service collects published records from medical-device regulators, organizes them, and links every statement back to the original regulator source.
For questions about this policy, contact us at info@rubiconmp.com.
Information we hold
Regulator records: licence, authorization, recall, standards and enforcement records published by Health Canada and the U.S. Food and Drug Administration. These are public records, not personal data supplied by you.
Workspace content: the watchlists, review decisions and notes your team creates inside the platform.
Notification settings: the email addresses your team enters to receive regulatory updates, plus a record of which updates were sent, so the same update is not emailed twice.
Operational records: timestamps, counts and error summaries for each data refresh, used to show whether each source is healthy.
Usage statistics (only with your consent): anonymous counts of the pages viewed, collected by Google Analytics, with no name, email or account linked to them.
How we use it
To run the service: organize regulator records, detect changes relevant to your watchlists, and show them to your team.
To send the notifications you asked for: immediate alerts or daily or weekly digests, based on your own settings. You can switch any category off at any time.
To keep the platform working: monitor refresh jobs and investigate failures.
We do not sell your data, and we do not use it for advertising or profiling.
Cookies and tracking
Rubicon Microproducts Inc. uses a small number of essential cookies to keep you signed in and keep your workspace secure. These do not require consent and are always used.
With your consent we also use Google Analytics to count visits and page views, so we can understand which parts of the platform are used. Google Analytics sets cookies in your browser and collects the pages you view, how long you stay, your approximate region and your browser and device type. We never use it for advertising, and this data is not sold or used for profiling.
Analytics runs only after you accept it in the consent banner, and you can change your choice at any time using the Cookies link in the footer of any page. Declining analytics does not limit any feature of the platform. Your choice is stored in your browser and is not linked to your account.
We do not use advertising or cross-site tracking cookies, and we do not embed third-party trackers.
Billing and payment information
Paid plans are paid through Stripe, our payment provider. When you buy or renew a subscription, Stripe collects the details needed to take payment and meet tax rules — name, billing email, billing address and country, payment card or wallet details, and the tax identifiers you choose to enter.
Card and payment details are entered with Stripe and are never held by us. From Stripe we receive the information needed to run your subscription: the plan bought, its status and renewal dates, the billing email, country and a receipt or invoice reference.
Stripe acts as a controller of the payment data it collects and applies its own privacy notice, available at https://stripe.com/privacy. Stripe also handles tax calculation and collection, transaction receipts, disputes and refunds.
Legal basis for using your information
Rubicon Microproducts Inc. relies on performance of our contract with you to create and run your account, provide the platform, and manage your subscription and billing through Stripe; on our legitimate interests to keep the platform secure and reliable, investigate faults and prevent misuse or fraud; on your consent for optional notification categories you switch on and for analytics cookies; and on legal obligation where tax, accounting or other law requires us to keep or disclose records.
Where we rely on consent you can withdraw it at any time, without affecting anything done before you withdrew it.
How we protect information
We apply technical and organizational measures appropriate to the data we hold: encryption in transit, encryption of data at rest with our hosting provider, access limited to the people who need it for their role, per-organization separation of workspace content enforced in the database, and logging of administrative actions.
No system is completely secure, so we also keep the amount of personal data we hold to the minimum the service needs.
Sharing and processors
We use service providers to host the application and its database, and — once outbound email is connected for your workspace — to deliver notification emails. They process data only to provide those services to us.
Where you consent to analytics, anonymous usage statistics are processed by Google (Google Analytics) on our behalf, under Google's own terms.
We share billing information with Stripe for the sale of the product, subscription management, payments, tax compliance and invoicing.
We may share information with our professional advisers, such as legal and accounting advisers, where they need it, and we may disclose information where the law requires it.
We do not sell your personal data.
Retention
Regulator records and their history are retained so change history stays auditable. Workspace content is retained while your account is active, and deleted or anonymized within a reasonable period after your account closes unless you ask us to export it first. Notification delivery records are retained to prevent duplicate emails.
Billing and subscription records are kept for as long as tax and accounting law requires, then deleted. When information is no longer needed for the purpose it was collected for, we delete or anonymize it.
Your choices
You can change or switch off notification categories in the platform, and you can ask us to correct or delete the workspace content and email addresses associated with your team.
Changes to this policy
We will update this page when our handling of information changes, and we will note the date of the change here.