Privacy Policy | Springloop

Last updated: 28 September 2026

1. Introduction

This Privacy Policy explains how Motivoriginal Lda ("we", "us", or "our") collects, uses, stores, and protects personal data when you use Springloop (the "Platform").

Springloop is a platform that helps professionals manage their services, including scheduling, online sessions, payments, client interactions, and calendar integrations.

We are committed to protecting your privacy and processing personal data in accordance with the General Data Protection Regulation (GDPR), applicable Portuguese data protection laws, and the requirements applicable to third-party services integrated with Springloop.


2. Data Controller

For account, subscription, billing, authentication, and general platform-related data, the data controller is:

Motivoriginal Lda

Avenida Luisa Todi 135, 2º Piso

2900-461 Setúbal

Portugal

Email: support@springloop.io

For certain data processed by professionals using Springloop, such as client information, session information, recordings, or other content added by those professionals, the professional may act as the data controller and Motivoriginal Lda may act as a data processor on their behalf.


3. Personal Data We Collect

3.1 Account Information

When you create or use a Springloop account, we may collect:

  • Name
  • Email address
  • Account credentials
  • Profile information
  • Business or professional information
  • Account preferences and settings

3.2 Usage and Technical Data

We may collect information about how you use Springloop, including:

  • Sessions created or joined
  • Session duration and activity
  • Device and browser information
  • IP address
  • Log data
  • Authentication activity
  • Platform interactions and feature usage

This information is used to operate, secure, troubleshoot, and improve the Platform.

3.3 Payment Data

Payments may be processed through third-party payment providers such as Stripe.

Springloop does not store full payment card details.

We may store information such as:

  • Payment status
  • Transaction identifiers
  • Subscription details
  • Payment provider account identifiers
  • Billing-related metadata

3.4 Session and Recording Data

When enabled by the professional or account owner, Springloop may process information related to online sessions, including:

  • Audio and video streams
  • Session recordings
  • Chat messages
  • Session metadata
  • Session date and time
  • Participant information
  • Session duration

Recording functionality is only used when enabled for the relevant session or account.


4. Google Calendar Integration

Springloop allows users to optionally connect their Google Calendar account to the Platform.

Connecting Google Calendar is optional. Springloop only accesses Google Calendar data after the user explicitly authorizes access through Google's OAuth authorization process.

4.1 Google Data We Access

Depending on the features enabled by the user, Springloop may access:

  • The list of calendars available in the user's Google Calendar account
  • Calendar identifiers and calendar names
  • Event start and end times
  • Event availability or free/busy information
  • Event identifiers
  • Event titles, descriptions, and other event information where required to provide calendar synchronization functionality
  • Events created by Springloop
  • Information necessary to detect changes to relevant calendar events

Springloop may also create, update, or delete Google Calendar events when necessary to synchronize Springloop sessions with the user's selected Google Calendar.

Springloop does not access Google Calendar information unless the user has explicitly connected their Google account and granted the requested permissions.

4.2 How We Use Google Calendar Data

Google Calendar data is used exclusively to provide calendar-related functionality requested by the user, including:

  • Adding Springloop sessions to the user's selected Google Calendar
  • Updating calendar events when a Springloop session changes
  • Removing calendar events when a corresponding Springloop session is cancelled or deleted, where applicable
  • Checking calendar availability to prevent scheduling conflicts
  • Displaying available and unavailable time slots inside Springloop
  • Synchronizing scheduling information between Springloop and Google Calendar
  • Detecting relevant calendar changes in order to keep availability information up to date

Google Calendar data is not used for advertising purposes.

Google Calendar data is not sold.

Google Calendar data is not used to create advertising profiles.

4.3 Storage of Google Data

Springloop stores only the Google Calendar information reasonably necessary to provide the calendar integration.

This may include:

  • Google Calendar identifiers
  • Google event identifiers
  • Calendar synchronization metadata
  • OAuth authorization information, including access and refresh tokens where required to maintain the connection
  • Information necessary to associate a Springloop session with a Google Calendar event

OAuth credentials and tokens are stored using appropriate technical security measures and are only used to communicate with Google APIs on behalf of the authorized user.

Calendar information may be temporarily stored or cached when required to provide synchronization, availability, or scheduling functionality.

Springloop does not retain Google Calendar data for longer than reasonably necessary to provide these features or comply with applicable legal obligations.

4.4 Sharing of Google User Data

Springloop does not sell Google user data.

We do not share Google user data with advertisers, data brokers, or other third parties for advertising or marketing purposes.

Google user data may only be processed by infrastructure or service providers where this is necessary to operate Springloop, provide the requested functionality, maintain security, or comply with applicable law.

Where service providers process such information on our behalf, they are required to handle it only for the purposes necessary to provide their services to Springloop and subject to appropriate data protection safeguards.

4.5 Artificial Intelligence and Machine Learning

Data obtained from Google Workspace APIs, including Google Calendar data, is not used to develop, improve, or train generalized or non-personalized artificial intelligence or machine learning models.

Google Calendar data is only processed as necessary to provide user-facing Springloop functionality that the user has requested or enabled.

4.6 Revoking Google Calendar Access

Users can disconnect their Google Calendar integration from their Springloop account.

Users can also revoke Springloop's access to their Google Account through their Google Account permissions settings.

After access is revoked, Springloop will no longer access the user's Google Calendar through the revoked authorization.

We may retain limited synchronization metadata where necessary for security, auditing, legal compliance, or to maintain references to previously created Springloop sessions, subject to applicable retention requirements.

4.7 Google API Services User Data Policy

Springloop's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements.

Springloop only requests access to Google data that is necessary to provide the calendar functionality offered to the user.


5. How We Use Personal Data

We may use personal data to:

  • Provide and operate the Platform
  • Manage user accounts
  • Schedule and manage sessions
  • Synchronize calendars
  • Process payments and subscriptions
  • Deliver recordings and session assets
  • Send service notifications and reminders
  • Provide customer support
  • Detect and prevent fraud, abuse, and security incidents
  • Troubleshoot technical problems
  • Analyze Platform performance and usage
  • Improve the reliability and functionality of Springloop
  • Comply with legal and regulatory obligations

6. Legal Basis for Processing

Depending on the type of processing, we rely on one or more of the following legal bases under the GDPR:

Performance of a Contract

Processing necessary to provide Springloop and the services requested by the user.

Legitimate Interests

Processing necessary for legitimate interests such as:

  • Maintaining Platform security
  • Preventing fraud and abuse
  • Improving service reliability
  • Providing customer support
  • Diagnosing technical problems

Where we rely on legitimate interests, we consider the impact on users' privacy rights.

Consent

We may rely on consent for certain processing activities, including:

  • Connecting optional third-party integrations
  • Certain recording functionality
  • Marketing communications where required
  • Other optional functionality requiring explicit authorization

Users may withdraw consent where applicable.

Legal Obligations

We may process information where necessary to comply with legal, accounting, tax, regulatory, or other statutory obligations.


7. Data Sharing and Service Providers

We may share personal data with service providers necessary to operate Springloop, including providers of:

  • Cloud infrastructure and hosting
  • Payment processing
  • Email delivery
  • Video communication infrastructure
  • Monitoring and error reporting
  • Analytics
  • Customer support tools

These providers may only process personal data according to our instructions and for the purposes required to provide their services.

We may also disclose information:

  • To professional advisors such as accountants or legal advisors
  • Where required by law
  • To protect the rights, safety, or security of Springloop, our users, or others
  • In connection with a merger, acquisition, restructuring, or sale of the business, subject to applicable legal requirements

We do not sell personal data.


8. International Data Transfers

Some service providers may process personal data outside the European Economic Area (EEA).

Where personal data is transferred internationally, we use appropriate safeguards where required by law, which may include:

  • European Commission Standard Contractual Clauses
  • Adequacy decisions
  • Other legally recognized transfer mechanisms

9. Data Retention

We retain personal data only for as long as reasonably necessary for the purposes for which it was collected, including:

  • Providing the Platform
  • Maintaining user accounts
  • Providing synchronization and integration functionality
  • Meeting legal and accounting obligations
  • Resolving disputes
  • Preventing fraud and abuse
  • Enforcing agreements

Retention periods may vary depending on the type of information and applicable legal requirements.

Users may request deletion of eligible personal data by contacting us at support@springloop.io.

Professionals using Springloop may also be responsible for responding to requests concerning data they control, including participant or client information.


10. Your Data Protection Rights

Subject to applicable law, you may have the right to:

  • Access your personal data
  • Request correction of inaccurate personal data
  • Request deletion of your personal data
  • Request restriction of processing
  • Object to certain processing
  • Request data portability
  • Withdraw consent at any time where processing is based on consent
  • Lodge a complaint with a competent data protection authority

To exercise these rights, contact: support@springloop.io

We may need to verify your identity before processing certain requests.


11. Security Measures

We implement technical and organizational measures designed to protect personal data against:

  • Unauthorized access
  • Unauthorized disclosure
  • Loss
  • Misuse
  • Alteration
  • Destruction

These measures may include:

  • Encryption
  • Secure authentication
  • Access controls
  • Secure storage of authentication credentials and tokens
  • Network and infrastructure security controls
  • Logging and monitoring
  • Regular security reviews

No system can guarantee absolute security, but we continuously work to maintain appropriate safeguards for the information processed by Springloop.


12. Third-Party Services

Springloop may integrate with third-party services such as Google Calendar and Stripe.

When users connect or interact with third-party services, those services may process personal information according to their own privacy policies and terms.

Springloop only requests access to third-party data where necessary to provide functionality requested by the user.


13. Children's Privacy

Springloop is not intended for individuals under the age of 16 to create accounts independently.

If we become aware that personal data belonging to a minor has been collected in circumstances where appropriate consent or authorization was required but not obtained, we will take reasonable steps to delete it.

Professionals using Springloop are responsible for ensuring they have an appropriate legal basis when providing services involving minors.


14. Changes to this Privacy Policy

We may update this Privacy Policy from time to time to reflect:

  • Changes to Springloop
  • New integrations or functionality
  • Changes in legal requirements
  • Changes in our data processing practices

The date at the top of this page indicates when this Privacy Policy was last updated.

Where required, we will notify users of significant changes through the Platform or by email.


15. Contact

For questions about this Privacy Policy or the processing of personal data by Springloop, contact:

Motivoriginal Lda

Avenida Luisa Todi 135, 2º Piso

2900-461 Setúbal

Portugal

Email: support@springloop.io