Capacitor

Overview

Capacitor 0.2.x integration and privacy.

Capacitor plugin 0.2.0, wrapping Android SDK 1.4.0 and iOS SDK 1.4.0. The package bundles the iOS framework and resolves Android from Stay22's Maven repository. These pins determine the native behavior available to your app.

The plugin accepts travel context from your app and can schedule a local accommodation notification. Start with the quick start.

Requirements

Capacitor 6+, iOS 15+, and Android API 24+. Android and iOS are implemented; web and desktop calls are not supported.

On Android 7.0 with its standard certificate store, the wrapped SDK cannot verify Stay22's server certificate, so it cannot load partner settings or schedule notifications. API 24 remains the build minimum.

Notification behavior

Normal automatic scheduling is evaluated after your app leaves the foreground. Account settings control the delay, frequency limits and optional server distance check. The operating system may show a notification later than requested. A text destination that matches the IP-derived home city can be suppressed locally; coordinates-only context skips that text comparison. That city is never used as a travel destination.

Context updates keep earlier non-empty destination, hotel, coordinate and date fields when omitted. Clear before an unrelated trip. Updating only guest counts is ignored by the native context signature; clear and resend the full trip. See notifications.

The native consent-required keys keep startup requests and scheduling off until your app records an affirmative choice. Follow the quick start. The SDK starts enabled by default when those keys are absent.

What reaches Stay22

At startup: while enabled, the native SDK requests partner settings and sends a load event. Requests carry your partner ID (aid) and a Stay22-issued identifier (sid22), stored on the device and reused on later launches. Loads include native OS/SDK versions and installed-app answers for a set of travel booking apps. On iOS an undeclared URL scheme is reported as not installed. Stay22 receives the IP address and derives approximate location and timezone, even if your app submits no trip.

Before scheduling: the SDK sends your supplied destination, coordinates, dates and hotel name, together with the identifiers and installed-app answers above. The local home-city and cooldown gates can stop the trip before this decision request.

After display: the SDK reports shown notifications and failures. Stay22 stores destination and dates with its partner/session frequency-capping record. The server record expires automatically, by default after seven days; account settings can change that period. Tapping opens the saved booking URL carrying attribution and trip context. This plugin does not expose the newer native prepared-link and separate tap-report API.

Cookies: Stay22 responses set a session22 cookie carrying the session identifier. The bundled iOS HTTP client neither stores cookies nor sends stored cookies. Android installs no cookie handler of its own, but a process-wide handler added by your app or another dependency can store the response cookie. The SDK does not read it.

Store declarations: the native SDK requests no GPS permission and does not read device location. Its bundled Apple privacy manifest declares Device ID, product interaction, and precise/coarse location for the persistent identifier, trip coordinates and IP-derived location described above. Review your App Store privacy answers and Google Play Data Safety declaration against these behaviors.

These are client-version instructions. Account settings, retention and other server policies can change independently; an older package does not freeze those policies. Read the Capacitor changelog for release changes.

On this page