# Spacetime access

This page is the playbook for partners who are granted access to Spacetime data for customers that hold a direct subscription with Flip.to. It pulls together the contractual basis, the enablement workflow, and the templates so a partner can roll this out in one pass.

For the underlying contract terms, see the [Technology and Agency Partner Addendum](https://docs.flip.to/policies/legal/technology-and-agency-partner-addendum).

## Two scenarios

Partner access to Spacetime data falls into one of two patterns:

### <mark style="color:$primary;">Partner-deployed</mark>

The partner deploys Spacetime to their own customers as part of the partner's service offering. The partner is the processor; the customer is the controller; Flip.to is the sub-processor. This is the "Hosted Customer" model and is fully covered by the existing Addendum.

### <mark style="color:$primary;">Shared customer</mark>

The customer has a **direct** Spacetime subscription with Flip.to, and also engages the partner for services. The partner is granted access the customer's Spacetime data on the customer's behalf. This is the **shared customer** model and uses the workflow below.

## Shared customer workflow

Three light steps. The whole flow is designed to take a single email exchange per customer.

{% stepper %}
{% step %} <mark style="color:$primary;">**Already covered in the service agreement**</mark>

The partner's service agreement with the customer needs to authorize the partner to receive and process the customer's Spacetime data on their behalf. Most existing service agreements already have broad "authorized platform access" language that covers this.

If yours doesn't, add a clause like:

```
Authorized Platform Access

Customer authorizes [Partner] to access, receive, and process
Customer's data from third-party marketing and analytics platforms
used by Customer in connection with the Services, including without
limitation Flip.to / Spacetime. [Partner] will use such data solely
to provide the Services to Customer and in accordance with the data
processing terms of this Agreement. Customer may withdraw this
authorization at any time by written notice to [Partner].
```

This is the load-bearing piece—it backs the partner's representation to Flip.to in Step 3.
{% endstep %}

{% step %} <mark style="color:$primary;">**Light notification to the customer**</mark>

A day or two before enabling access, the partner sends the customer a short heads-up so the email Flip.to receives in Step 3 isn't out of context:

{% code overflow="wrap" %}

```
To: [Customer rep]
Subject: Heads-up: enabling Spacetime data access for [Property]

Hi [Name],

Quick note—we're getting set up on Flip.to's Spacetime platform to
support our work together for [Property]. Spacetime is Flip.to's
analytics platform built specifically for travel—first-party
behavioral data with channel-level insights across the traveler
journey.

In the next day or two you'll see an email from us to Flip.to with
you CC'd, formally enabling access on your account. 

For now, no action needed on your end. Excited to collectively improve 
our analytics and performance!

Thanks,
[Partner rep]
```

{% endcode %}
{% endstep %}

{% step %} <mark style="color:$primary;">**Enablement email to Flip.to**</mark>

The partner sends one email to Flip.to with the customer CC'd. Flip.to enables access within five business days unless the customer objects.

```
To: success@flip.to
CC: [Customer authorized rep]
Subject: Spacetime data access—[Customer Name]

Hi Flip.to team,

Enabling Spacetime access for our shared customer below under our
partner agreement.

  Customer:   [Legal entity name]
  Properties: [property names / Spacetime account IDs]

[Partner] confirms our service agreement with [Customer] authorizes
us to receive and process this data on their behalf.

[Customer rep]—copying you per our partner agreement with Flip.to.
Please let us know if you have any questions; otherwise Flip.to will
enable access in five business days.

Thanks,
[Partner rep]
```

{% endstep %}
{% endstepper %}

## What gets shared

By default, the partner gets read access to the relevant Spacetime data and/or interfaces. Access is granted at the customer account level for the properties named in the enablement email.

If the customer wants to limit access to specific properties only, they can specify that in their reply to the enablement email and Flip.to will configure access accordingly.

## Use restrictions

All data accessed under this workflow is subject to the confidentiality and use terms in the [Addendum](https://docs.flip.to/policies/legal/technology-and-agency-partner-addendum). Two restrictions worth calling out explicitly:

* Data may only be used to provide services to the customer it came from. It can't be aggregated across customers or used to develop products that compete with Flip.to.
* When data or insights from Spacetime are presented to the customer, they must be attributed accurately and not represented as the partner's proprietary analytics.

## Revocation

The customer may revoke access at any time by emailing `success@flip.to`. Flip.to will disable the partner's access within five business days of receipt and notify the partner. The partner's confidentiality obligations continue to apply to any data already accessed.

## Questions

Reach out to the Flip.to customer success team at `success@flip.to` for anything that doesn't fit the workflow above—onboarding many customers at once, narrower scopes, custom data pipelines, or joint-customer questions.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flip.to/partners/spacetime-access.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.