Privacy Policy
Effective 13 November 2026. Aventi is operated by Ascension Technologies Inc., Victoria, British Columbia, Canada.
Aventi (aventi.app) helps people find things to do in Victoria, BC and share events they create. This policy explains what we collect, why, who we share it with, and the choices you have. Questions: carlosandromeda8@gmail.com.
1. What we collect
- Account details. When you sign in (Google, Facebook, Sign in with Apple, phone number or a guest session) we receive your user ID and, depending on the method, your name, email address, profile photo, language setting or phone number. With Google and Facebook we ask only for your basic profile and email: signing in doesn’t give Aventi your likes, friends, posts, YouTube or any other data. With Sign in with Apple you can hide your email; we then only see Apple’s relay address.
- Events you add. Title, date and time, venue, links, price, description and photo, plus the time you submitted it.
- Preferences and activity in Aventi. Saved events, interests you pick, and which ticket links you tap (to understand what people find useful).
- Quick picks and age (optional). One-tap answers in the deck (who you go out with, budget, energy, seated or active) and, if you give it, your birth year or date of birth, used only to fit events to you. You can skip both; nothing is stored for anyone under 13. Delete account removes them.
- Location, only if you allow it in your browser or the Aventi app, and only while you use it, to show events near you. We keep the city you’re browsing, not a location history.
- Approximate location from your IP address (website). When you open the website’s front page with no city chosen, and Aventi is open in more than one city, your browser sends your IP address to ipapi.co for an approximate location, only to open the nearest city. Aventi remembers the city it opened on your device. The city setting lasts one day (a city you pick or open from a link lasts longer), and the name and time of that move are kept so it does not move you again right away. When no open city is near, your browser keeps only the time of that answer on your device, so it does not ask again for a day. Aventi does not store the IP address or that location.
- Plans with friends. Plans you make or join: the plan, the first name you give, your RSVP and messages. People in the same plan see these.
- Ticket orders. If you buy a ticket sold through Aventi, Stripe processes the payment; we keep the order (event, ticket type, quantity, amount, email) to issue your ticket. We never see your card number.
- Bookings and waivers. When you book a day and time on Aventi, we keep the booking (the card, the date and time, how many people) with your ticket. If the business asks for a waiver, we store, for each person who signs: the name typed, whether they are under 19 and the parent or guardian who signed for them, the emergency contact if the business asks for one, the waiver version and a fingerprint of its text, the time, the device and browser type (user agent) and, when signed in, the account. Names of guests you enter are used only to send their personal sign links. The business that runs the activity sees the signed copies for its own bookings; nobody else does, and they are never public.
- Push notifications (Aventi app). If you allow notifications, we store your device’s push token so we can send plan reminders and updates. Signing out or deleting your account removes it.
- Connected accounts. If you choose to connect another platform so Aventi can post your events there, we store the access token and the account details listed in the table below. Nothing is collected from a platform you haven’t connected.
- Taste from your accounts (optional). If you turn on “Personalize from this account” for Spotify, YouTube, Eventbrite, Meetup, Strava or Facebook, or take the taste quiz, we store a short list of interests derived from it (see section 2b). Nothing is read from an account until you turn it on.
- Business claims and owner codes. When someone claims a business’s card, Aventi can send a one-time code by text message or phone call to the phone number on that business’s public listing (never to another number). We store only a keyed hash of the code, the last 4 digits of that number, when it was sent and used, and the claim it verified. Codes expire after 15 minutes (codes Aventi makes by hand after 30 days) and work once.
- Posted codes. An event organizer can verify a claim by posting a short Aventi code (AVENTI-XXXXXX) on the event’s own page or in their Instagram bio. Aventi fetches the page you give it, once per check and without cookies or your sign-in, to look for your code. We keep only a keyed hash of the code, plus the page link (without its query string) and the result with the claim. If you ask Aventi to check by hand, the code and link are kept with the claim so a person can look. Codes expire after 7 days and work once; you can remove the code from your page after.
- Technical data such as IP address, browser type and error logs, kept by our hosting provider for security and debugging.
- Guest daily limit counter. Without signing in you can see 40 cards a day. To keep that fair, our server counts how many cards a guest has seen today. It stores only one-way keyed hashes (HMAC) made from your guest session ID, a shortened form of your network address (the first three parts of an IPv4 address, or the first 56 bits of an IPv6 one), your browser family (for example “Chrome on Android”, no version) and a light device summary (screen size, time zone, language and platform). We never store your IP address, browser string or session ID in this counter, we don’t use canvas, audio or similar fingerprinting, and every counter is deleted automatically after 48 hours. The app keeps the same count on your device (browser storage and a first-party cookie). Signing in removes the limit.
- Ads (guests and signed-in free accounts). Guests and free accounts see an occasional card marked “Sponsored”. We record that a sponsored card was shown or tapped, with a keyed hash of your account ID (not the ID itself) or, for a guest without an account, a keyed hash of the same guest-counter device key described above, kept for 90 days to count views and cap how often you see the same one (see section 2c).
2. Connected accounts (cross-posting)
Connecting is always optional and always started by you. Aventi only asks for the permissions needed to publish the events you choose, and only acts when you tick a platform on an event you added (or turn on “Auto” for that platform). We do not read your feed, messages, followers, friends or contacts, and we do not post anything you didn’t choose.
| Platform | What Aventi stores | What Aventi does with it |
|---|---|---|
| Facebook Pages (Meta) | Page ID and name, a Page access token, your app-scoped user token, the linked Instagram account ID and username | Publishes one post per event you choose, to the Page you picked (and its Instagram if you opt in) |
| Instagram account ID, username, access token | Publishes the event photo and caption (and a Story if you opt in) | |
| Threads | Threads user ID, username, access token | Publishes one post with the event link |
| Google Business Profile | Refresh token, account and location IDs and name | Creates an “Event” post on the location you picked |
| Google Calendar | Refresh token, your Google email address | Adds events you choose to your primary calendar |
| Eventbrite, Meetup | Access token, organization or group ID and name | Creates the event (Meetup: as a draft) under the organization or group you picked |
| LinkedIn, X, TikTok | Access and refresh tokens, your member/user ID and display name | Publishes one post per event you choose (TikTok: a photo post) |
| Bluesky, Luma, Ticket Tailor | The app password or API key you paste, your handle or calendar name | Publishes one post or creates one event per event you choose |
Access tokens and keys are encrypted (AES-256-GCM) on our servers. They are never sent to your browser, never sold, and never shared except with the platform they belong to when publishing for you. Disconnecting in Profile → Connected accounts deletes them immediately and, where the platform allows, revokes Aventi’s access.
Personal Facebook profiles: Facebook doesn’t allow apps to post to personal profiles. The “Facebook” share button opens Facebook’s own share window; Aventi receives nothing from it.
Google user data. Aventi’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google Business Profile and Google Calendar access only to create the posts and calendar events you ask for. We do not use Google user data for advertising, do not sell it, do not let humans read it except with your consent, for security, or to comply with law, and do not use it to train AI models.
2b. Taste from your accounts (personalization)
This is optional and off until you turn it on for a specific account in Profile → Connected accounts → Taste from your accounts, separately from cross-posting. Each source uses read-only permission, and Aventi never posts, follows, likes or changes anything through it.
| Source | What Aventi reads (read-only) | What we keep |
|---|---|---|
| Spotify | Your top artists (about the last 4 weeks and 6 months) and artists you follow (user-top-read, user-follow-read) | A list of short interest phrases with a weight, the source and the date (for example “indie rock”, “Khruangbin”, “trail running”), plus a numeric “taste vector” computed from them |
| YouTube | Names of channels you subscribe to; topics and channel names of videos you liked (youtube.readonly) | |
| Eventbrite | Names and categories of events you ordered tickets for (no payment details) | |
| Meetup | Names and topics of groups you joined | |
| Strava | Only the sport types of your recent activities (no routes, locations, times or health data) (activity:read) | |
Names and categories of Pages you like (user_likes; only once Meta approves this permission) |
The raw lists (your likes, subscriptions, orders, activities) are processed in memory on our server and are never stored. We skip signals about health, sexuality, politics or religion. To turn interests into the taste vector, the short phrases (not your account data) are sent to Google Cloud Vertex AI’s embedding model, under Google Cloud’s terms, which don’t allow Google to use them to train its models. The interests and vector are stored in your private profile, which only you and our server can read, and are used only to order and explain suggestions in your own feed (“Because you follow Victoria Jazz Society on Meetup”). They are never shown to other people, sold, used for advertising or used to train AI models.
You can see every learned interest and remove any of them (See what Aventi learned), turn a source off (which deletes everything learned from it), or tap Delete everything learned from accounts. Disconnecting an account also deletes what was learned from it. Instagram doesn’t offer any way for apps to read a personal account’s interests, so it isn’t a source. If you don’t connect anything, the 30-second taste quiz stores only your picks and the events you swiped on.
Aventi’s use of information received from Google APIs (including YouTube) adheres to the Google API Services User Data Policy, including the Limited Use requirements. YouTube data is accessed through YouTube API Services; see the YouTube Terms of Service and Google Privacy Policy. You can also revoke Aventi’s access at Google security settings, Spotify apps or Strava My Apps.
2c. Ads
Aventi is free. Guests (not signed in) and signed-in free accounts see about one card marked Sponsored for every eight events. Premium members (and free trials and Day Passes) never see ads.
- Sponsored events are sold directly by Aventi to local venues and organizers. Choosing one uses only the categories of the feed you are looking at, never your learned interests or connected accounts. Advertisers get totals (views and taps), never who you are.
- Google AdSense (website only, when enabled) may show ads on Aventi’s public web pages, never in the swipe deck. See section 2d.
- The Aventi apps on the App Store and Google Play show only Aventi’s own sponsored cards.
Going Premium removes all ads.
2d. Advertising and cookies
Google AdSense may show ads on Aventi’s public web pages (event, venue and Victoria guide pages). Ads are not shown in the app’s swipe deck, and Premium members never see them. Google and its partners use cookies and other identifiers to serve and measure ads, including to limit how often you see the same ad and to prevent fraud.
Third-party vendors, including Google, use cookies to serve ads based on your prior visits to aventi.app or to other websites. Google’s use of advertising cookies enables it and its partners to serve ads to you based on your visits to aventi.app and/or other sites on the Internet. Aventi does not use other ad networks on its web pages.
For visitors in the European Economic Area, the United Kingdom and Switzerland, consent for ads is collected through Google’s certified consent message (the Google-certified consent message from AdSense Privacy & messaging, a certified consent management platform under the IAB Transparency and Consent Framework), shown before any ad is requested on our web pages. Until you consent, ads are non-personalized by default. To change or withdraw your choice at any time, use the “Privacy and cookie settings” link Google shows at the bottom of those pages, or clear the cookies for aventi.app and the message will ask again on your next visit.
The “Ad choices” option on a Sponsored card inside the app covers only Aventi’s own sponsored cards. It does not replace Google’s consent message for AdSense ads on our web pages.
Links to partners such as ticket sellers, hotels and restaurant booking sites may earn Aventi a commission. These links are labelled “Sponsored”.
To learn more or opt out of personalized ads:
- How Google uses information from sites that use its services
- Google Ad Settings
- Digital Advertising Alliance opt-out
- Your Online Choices (Europe)
2e. Analytics
On aventi.app only, Aventi uses Google Analytics 4 to count how the app is used: which screens are opened and for how long, which buttons are tapped (by their label, never by what you typed), swipes (right, left or up, with the card's category and type), and steps such as opening Premium or tickets. We never send your name, email, phone number, user ID, exact location, search words, messages or anything you type, and page addresses are cut back to their public part. Google signals and ad personalization are off, so this data is not used for advertising. In the European Economic Area, the United Kingdom and Switzerland analytics storage is denied by default. If your browser sends Global Privacy Control or Do Not Track, Google Analytics never loads. It never runs on our test sites, in the admin console or inside other sites. Google receives the request details any web request carries (such as your IP address and browser), under the Google Privacy Policy; you can also use Google's opt-out add-on.
3. How we use information
- To run Aventi: show events, keep your account signed in, review and publish events you add, and post them to platforms you connected.
- To personalize your own feed, only from the accounts you turned on for it or your quiz answers (section 2b).
- To keep Aventi safe: prevent spam and abuse, and fix problems.
- To improve Aventi using aggregated, non-identifying statistics.
- To contact you about your account or events you added, if needed.
We don’t sell personal information. Your account details, saved events, learned interests and connected-account data are never given to advertisers; ads work as described in section 2c.
4. Who we share it with
- Google AdSense (website only, when enabled): on Aventi’s public web pages (event, venue, place, movie and Victoria guide pages) Google receives the page address, your IP address and browser details that any web request carries, and its own cookies, under Google’s policies (section 2d). This applies to every visitor, guests and signed-in free accounts alike; Premium members (and free trials and Day Passes) are shown no ads there. Aventi’s own Sponsored cards (section 2c) are not Google ads and share nothing about you with Google or the advertiser.
- Google Analytics (aventi.app only): usage counts as described in section 2e, with no name, email, user ID or exact location.
- Service providers that host and run Aventi for us: Google Cloud and Firebase (hosting, database, authentication, file storage, push notifications through Firebase Cloud Messaging and Apple Push Notification service), Stripe (ticket payments), ipapi.co (an approximate location from your IP address on the website, section 1) and Twilio (one-time owner codes sent by text or call to a business’s listed phone). Data may be stored and processed in the United States and Canada.
- Affiliate partners (Amazon, Apple, Booking.com, Expedia, OpenTable, Resy, merchants reached through the Awin network, and ticket sellers): when you tap one of their links, the partner sees that you came from Aventi through the link’s referral code, so Aventi may earn a commission. We don’t send them your account details. As an Amazon Associate, Aventi earns from qualifying purchases.
- Platforms you connect, only the content you choose to publish there. Once published, that content is governed by the platform’s own privacy policy.
- Everyone, for events after they’re approved: event details you submit are public on aventi.app.
- Authorities, if required by law.
5. How long we keep it
- Connected-account tokens: until you disconnect, the platform tells us you removed Aventi, or the token expires and isn’t renewed.
- Learned interests and the taste vector: until you remove them, turn the source off, disconnect it, or delete your account. With weekly refresh on, they are replaced with fresh ones about once a week.
- Account data: while your account is active, and deleted within 30 days of a deletion request.
- Signed waivers and booking records: kept while the business may need them for a legal claim about the activity, then deleted. Unused guest sign links stop working 2 days after the booked date.
- Published events stay listed until they’re over or removed. Server logs are kept for up to 30 days.
- Guest daily limit counters: deleted automatically after 48 hours. Sponsored-card view and tap records: 90 days.
6. Your choices and rights
You can disconnect any platform at any time in Profile → Connected accounts. You can ask to see, correct or delete your personal information, or withdraw consent, by emailing carlosandromeda8@gmail.com. We’ll answer within 30 days. See how to delete your data. Under British Columbia’s Personal Information Protection Act (PIPA) and Canada’s PIPEDA you may also contact the Office of the Information and Privacy Commissioner for British Columbia.
7. Cookies and local storage
Aventi uses cookies and browser storage that are needed to sign you in, keep your preferences and protect connection flows (a short-lived, HttpOnly security cookie during sign-in to another platform). It also keeps the guest daily limit count (browser storage and a first-party cookie, section 1) and your ad choice. When you open someone’s invite link (aventi.app/i/…), we keep that invite on your device for 30 days (an HttpOnly first-party cookie and browser storage) so the right person is credited if you create an account; the inviter sees only totals, never your name or activity. If Google AdSense is enabled on the website, visitors to Aventi’s public web pages (event, venue, place, movie and Victoria guide pages), guests and signed-in free accounts alike, may receive Google’s ad cookies there, non-personalized unless you consented (section 2d). AdSense never runs in the app’s swipe deck or on the legal, About and Contact pages. Premium members (and free trials and Day Passes) are shown no ads; because those pages are the same for everyone, Google’s ad script can still load on them before Aventi hides the ad space, so Google may receive the request described in section 4. Aventi’s own Sponsored cards in the swipe deck set no Google cookies: a guest’s views are counted with a keyed hash of the guest-counter device key (section 1).
8. Children
Aventi isn’t directed to children under 16 and we don’t knowingly collect their information. If you think a child has given us information, contact us and we’ll delete it.
9. Security
We use encryption in transit (HTTPS) and at rest, least-privilege access and per-platform minimum permissions. No system is perfectly secure; if we learn of a breach affecting you, we’ll notify you as the law requires.
10. Changes
If we change this policy we’ll update the date above, and for material changes we’ll notify you in the app.
11. Contact
Ascension Technologies Inc., Victoria, British Columbia, Canada. Privacy contact: carlosandromeda8@gmail.com.