Data flow

Overview

Redpoint Identity Studio (RIS) is a “data-in-place” application; your data is persisted only within your Snowflake environment. RIS uses a Hygiene service to standardize and validate postal addresses for 250+ countries to ensure they are complete, accurate, and deliverable according to postal standards.

This document delineates exactly what data leaves your Snowflake environment (to Redpoint’s external Hygiene service) and under what conditions.

What data leaves Snowflake?

Address data for hygiene is the only data that leaves your Snowflake account, as detailed below.

• Redpoint exchanges JSON via its Hygiene service’s REST API

  • The request payload:

    • correlationId (a Redpoint internal deduplication and join key containing no personal data and not linkable to an individual)

    • address

    • city

    • province

    • postcode

    • country

  • The response payload:

    • correlationId (a Redpoint internal deduplication and join key containing no personal data and not linkable to an individual)

    • addr_nbr

    • pre_dir

    • street

    • suffix

    • post_dir

    • unit

    • unit_nbr

    • city

    • province

    • postcode

    • country

    • status

• The Hygiene service exchanges JSON with Loqate (GBG), an ISO 27001:2022-certified address verification service, via REST API for addresses outside of the U.S. and Canada

  • The request payload:

    • Address1

    • Address2

    • Address3

    • Country

  • The response returns corrected, completed, parsed addresses

Data flow diagram

When does RIS send data to the Hygiene service?

RIS sends data to the Hygiene service as specified above only when you run a Production job (full or incremental) in RIS.

Where does the Hygiene service run?

The Redpoint Hygiene service runs in Azure East US 2 only.
(This only applies to the Redpoint Hygiene service, not Snowflake servers.)

What does Loqate do with my address data post-processing?

A: For addresses outside of the U.S. and Canada, Loqate has the following data retention strategies for the request: