SE Ranking procurement policy evidence
Only topics backed by verified findings appear below. Each row preserves the platform's exact policy words and capture provenance.
| Topic | Plan or tier | Risk | Their words | Source |
|---|---|---|---|---|
| Subprocessors & data sharing | All applicable tiers | medium | “ We use Stripe for payments, analytics, and other business services. Stripe collects and processes personal data, including identifying information about the devices that connect to its services via cookies and similar technologies. The personal data Stripe collects and processes may include transactional data. Stripe uses this information to operate and improve the services it provides to us, including for fraud detection, loss prevention, authentication, and analytics related to the performance of its services. For the full list of our sub-processors as well as applicable legal mechanisms in the case of international data transfers we kindly refer to the “ Processors ” section on our Website. As part of our affiliation within a shared corporate group, we may share certain personal data between Seranking Ltd. / SER Acquisition Inc. and Planable Inc. (and its subsidiaries) to support harmonized operations, IT infrastructure, financial operations and internal processes. Each company remains an independent data controller and maintains its own privacy policies, legal responsibilities, and customer-facing products and services. Data is shared only to the extent necessary to ensure the consistency, security, and efficiency of our joint infrastructure and internal workflows. This sharing is conducted in accordance with applicable data protection laws and with appropriate safeguards in place.” | Captured 2026-06-08Open source →Finding permalink → |
| Subprocessors & data sharing | All applicable tiers | medium | “ Below, we describe the categories of personal information we have disclosed in the past 12 months and the categories of third parties with whom that information may be shared. Categories of personal data that might have been disclosed: Identifiers (e.g., name, email address, IP address;);” | Captured 2026-06-08Open source →Finding permalink → |
| Subprocessors & data sharing | All applicable tiers | medium | “ To fulfill the purpose for which you provide it; For any other purpose disclosed by us when you provide the information; With your consent; To comply with any court order, law, or legal process, including to respond to any government or regulatory request; If we believe disclosure is necessary or appropriate to protect the rights, property, or safety of Seranking Ltd., SER Acquisition Inc., our customers, or others. ” | Captured 2026-06-08Open source →Finding permalink → |
| Subprocessors & data sharing | All applicable tiers | medium | “ Recipients-wise, we disclose your personal data to relevant third parties as described in this Privacy Statement: To our subsidiaries and affiliates; To a buyer or other successor in the event of a merger, divestiture, restructuring, reorganization, dissolution, or other sale or transfer of some or all of Seranking Ltd.’s / SER Acquisition Inc.’s assets, whether as a going concern or as part of bankruptcy, liquidation, or similar proceeding, in which personal information held by Seranking Ltd. and SER Acquisition Inc. about our Website users is among the assets transferred; To our sub-processors – contractors, service providers, and other third parties we use to support our business and who are bound by contractual obligations to keep personal information confidential and use it only for the purposes for which we disclose it to them. ” | Captured 2026-06-08Open source →Finding permalink → |
Informational only, not legal advice. Terms can change; verify every cited source and capture date during procurement review.
📢 POLICY UPDATES ALERT
AIRIN Brief
Built for compliance officers, legal counsel, and SaaS founders. Subscribe to the email digest — one short brief when a tracked vendor materially changes its terms, training policy, or risk rating. Prefer in-app? Watch platforms in your alerts inbox instead.