Privacy Policy
Effective date: 2026-11-17
This Privacy Policy explains how Asora Technologies Limited ("Asora", "we", "us", "our") collects, uses, shares and protects personal data when you use Asora Succession Planner, the web app at succession.asora.com (the "Service").
The short version: your work lives in your own Google Drive. We do not store its content. We keep only what we need to sign you in, find your files and send the emails you ask for: your account, the private links you make and a few technical records, in the EU. The tool sends emails to the people you add to a plan. They contain only the plan’s family name, an action, its date and your name. If you tick the box on the sign-in page, we also add you to our mailing list.
This policy covers the Service only. Asora’s main Privacy Policy covers asora.com and the Asora platform.
1. Who we are
The controller of your personal data is:
- Service: Asora Succession Planner
- Controller: Asora Technologies Limited, trading as Asora, a company registered in Ireland under company number 706300
- Registered office: 20 Hatch Street Lower, Dublin 2, D02 XH02, Ireland
- VAT: IE3845828BH
- Email: privacy@asora.com
Please send any privacy question to the email address above.
2. What this policy covers
This policy covers personal data we process through:
- the web app at succession.asora.com;
- signing in with Google;
- creating, reading and editing your work in your Google Drive;
- the private links and the emails the Service sends to the people you add to a plan, and what those people do with their links;
- the optional sign-up to our mailing list on the sign-in page;
- emails you send us for support.
This policy does not cover how Google processes your data in its own products. Google’s own privacy policy applies to that.
3. How the Service works, in brief
You sign in with a Google account. Your work is kept in your own Google Drive, in the folder Asora / Succession Plans. Only you work on it in the Service: it gives nobody else access.
When you view or change your work, our servers read or write your files on your behalf. The content passes through our servers but is not saved in our database.
4. Personal data in our database
Our database is hosted in the EU (section 11). It holds:
4.1 Account data
When you sign in, we receive and store:
- your name and email address;
- your Google account ID;
- the URL of your Google profile picture, if Google provides one;
- whether Google says your email is verified;
- the permissions you granted (see section 6);
- the dates your account was created and last updated.
4.2 Connection data
To work with your files, we store the access token and refresh token that Google issues to the Service. These two tokens are encrypted at rest. The encryption key is kept separately from the database. Tokens are never sent to your browser.
When you sign in with Google, Google also gives the Service an ID token: a signed note from Google with your name, email address, profile picture URL and Google account ID. Our sign-in software stores it as Google sent it, not encrypted. It expires after about an hour, and it cannot open your Google Drive.
4.3 Sign-in sessions
For each sign-in session we store a session token, its expiry date, and the IP address and browser user agent from which you signed in. We use these to keep you signed in and to protect your account. A session expires 30 days after you last use it. Expired sessions are deleted the next time anyone signs in to the Service.
4.4 Where your work is
We store the ID of your "Asora / Succession Plans" folder, so the Service finds it again without searching. We also store the ID of each plan, so the Service can find your plans and send reminders without you being signed in.
4.5 Private links, email settings and the send log
For each person you add to a plan and give a private link, we store:
- their email address, as you typed it into the plan, so the Service can send the link and match a request for a new link;
- the ID of the plan and of the person in it, and a hash of the link’s secret, so the link can be checked and switched off (the link itself is not stored);
- when the link was made, last used and switched off;
- for each browser opened from a link, a session record with a hash of its cookie and its expiry date.
For each plan we store your email settings (how many days before a date to remind, which of your own emails are on, and whether the plan’s emails are paused), a log of what the Service did with the plan’s actions (the action’s ID, what kind of change, who and when, never the action’s words), and a send log with the kind of email, the plan’s ID, the time and the sending provider’s ID for the email, and a short hash of the address inside the log’s key. We also keep, for each plan, the position of your daily email (which changes it has covered) and the time your Google access ended, if it did, and short-lived counters under hashed keys that limit how often links can be sent and asked for. We store your time zone, so reminders arrive at 8:00 in your morning. When someone stops a kind of reminder, we store a hash of their email address and the kind, so we do not send it again.
4.6 Technical records
Our hosting provider keeps technical request logs (such as IP address, time and requested page) for up to 30 days, to run and secure the Service. We design our own server logs to hold only IDs and error codes, not your content, names or email addresses.
4.7 Data we do not collect
- Our database holds no plan content: no family names, action names, dates, notes, figures or names of people. We design our logs to leave them out.
- We do not use analytics, advertising or tracking tools.
- We do not use AI or machine-learning services to process your data.
- We do not process payment data. The Service is free.
5. Your content
Your content lives in your Google Drive. When you use the Service, our servers read it, show it in the app and write changes back. While this happens, the content is held in server memory, only for as long as your request runs. It is never written to our database, and we design our logs to leave it out.
5.1 People you add to a plan
A plan holds the names and email addresses of other people: family members, successors, managers, board members and advisers. They are other people’s personal data that you add, and you decide what to enter. The Service uses an address only to send the emails described below, to match a person to their private link and to let them ask for a new one. It does not use it for anything else. You should tell the people you add that you have added them and why.
5.2 Emails the Service sends
The Service sends these emails, only for plans you make:
- to a person you add, with their private link, when you choose Send link;
- to that person, reminders before and after the date of an action they own, and a confirmation page for Mark done;
- to you, a daily email about changes people made, a monthly summary and a reminder before the plan’s review date, each of which you can switch off;
- to you, a notice if your Google access has ended and the Service can no longer update your plan.
The Service sends no email to a person before you have sent or copied their private link. You can pause all emails for a plan at any time.
An email contains only the plan’s family name, the action, its date and your name as the plan owner. It never contains ownership, figures, notes written by other people or other parts of the plan. A note written by a person is named in your daily email but its words are not. Replies go to you.
We send these emails through Resend, in its EU region (section 10). Open and click tracking are switched off. The emails are sent on your behalf, at your instruction.
5.3 Stopping reminders
Every reminder and summary has a link to stop that kind of reminder with one click, and an unsubscribe header that mail programs show. The email with the private link and the notice about your Google access are sent once, when needed, and have no such link. Anyone who gets a reminder has the right to stop it, whether or not they have an account. Stopping a kind of reminder does not switch off their private link. A person can also ask you, or us at the address in section 20, to stop emails to them.
Emails from our mailing list (section 7) come from Asora, only if you joined it.
6. Google user data
6.1 What we access
When you sign in, Google asks you to grant these permissions:
- openid, email, profile: your name, email address, profile picture URL and Google account ID. We use these to create your account and sign you in.
- Google Drive, files used with this app (
https://www.googleapis.com/auth/drive.file): access only to files that the Service created. The Service cannot see, list, open or change any other file in your Drive.
With that access, the Service uses the Google Drive API to:
- create a "Asora / Succession Plans" folder for your work;
- create, read and update the files the Service keeps there;
- check that its folder and files still exist and are not in your Drive trash.
6.2 How we use it
We use Google user data only to provide and improve the features you see in the Service.
6.3 How we store it
We store your name, email address, profile picture URL, Google account ID, the granted permissions, your encrypted access and refresh tokens and Google’s ID token (sections 4.1 and 4.2), and the ID of your folder (section 4.4). We do not store the content of your files (section 5).
6.4 How we share it
We do not sell Google user data. We share it only:
- with the service providers in section 10, so they can host the Service, store our records and send the emails you asked for;
- when the law requires it (section 14).
6.5 Limited Use
Asora Succession Planner’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In particular:
- We do not use Google user data for advertising, including retargeting or personalised ads.
- We do not use Google user data to train or improve artificial intelligence or machine-learning models, ours or anyone else’s.
- We do not sell Google user data or pass it to data brokers.
- No person at Asora reads your Google user data, unless you give us explicit consent for specific data (for example, when you ask for help), it is needed for security reasons (for example, to investigate abuse), it is needed to comply with the law, or the data has been aggregated and anonymised for internal operations.
6.6 How to revoke access
You can remove Asora’s access at any time on Google’s Third-party connections page. After that, the Service cannot read or write your files until you sign in again. Deleting your account in the Service does not remove this access, because the same Google sign-in is shared with other Asora tools. To delete the data we store, see section 13.
7. Our mailing list (optional)
The sign-in page has a box, unticked: "Send me news about Asora tools and the Family Office Roundup newsletter." Only if you tick it and your sign-in creates a new account, we send your name, email address, the address of this tool and the wording you agreed to to our mailing list in HubSpot. Signing in again later sends nothing.
You can leave the list at any time with the unsubscribe link in every email, or by writing to us. Leaving the list does not affect your account in the Service.
What we do with the mailing list is described in Asora’s main Privacy Policy.
8. Purposes and legal bases
| Purpose | Legal basis (GDPR) |
|---|---|
| Create and run your account, sign you in, connect your Google Drive, read and write your files | Art. 6(1)(b), performance of a contract |
| Send the private link, the reminders and the summaries you ask for to you and to the people you add | Art. 6(1)(b) for you, performance of a contract. Art. 6(1)(f) for the people you add, legitimate interests in reminding them of actions they own |
| Add you to our mailing list and send you news about Asora tools and the Family Office Roundup, if you tick the box | Art. 6(1)(a), consent |
| Keep sessions, IP addresses and user agents to protect accounts and prevent abuse | Art. 6(1)(f), legitimate interests: security of the Service |
| Answer support requests | Art. 6(1)(b) for users; Art. 6(1)(f) for others |
| Comply with legal obligations and valid legal requests | Art. 6(1)(c), legal obligation |
Where we rely on legitimate interests, you can object at any time (section 15).
9. Cookies and browser storage
The Service uses only what is strictly necessary to run it or what you ask for. We do not use analytics, advertising or tracking cookies, so we do not show a cookie banner (Regulation 5(5) of the Irish ePrivacy Regulations, S.I. No. 336 of 2011).
| Name | Type | Purpose | Duration |
|---|---|---|---|
__Secure-better-auth.session_token | Cookie | Keeps you signed in | 30 days, extended when you use the app |
__Secure-better-auth.state | Cookie | Protects the Google sign-in step against forgery | 5 minutes |
asora_opt_in | Cookie | Set only while you tick the mailing-list box on the sign-in page, so the Service knows your choice when your account is created. It holds no personal data | 10 minutes |
asora-theme | Local storage | Remembers your light, dark or system theme choice. It never leaves your browser | Until you clear it |
The sign-in cookies are HTTP-only. All cookies are sent only over secure connections and limited to succession.asora.com.
When you sign in, you are taken to Google’s sign-in page. Google may set its own cookies there under its own policies.
10. Service providers
We use these providers to run the Service. They process personal data on our behalf.
| Provider | Role and purpose | Location of processing |
|---|---|---|
| Vercel Inc. (USA) | Processor: hosting and server functions | Server functions in an EU region (Ireland) |
| ChiselStrike Inc., trading as Turso (USA) | Processor: database for the records described in section 4 | Ireland (EU) |
| Resend, Inc. (USA) | Processor: sending the emails in section 5.2 | Sending region in the EU |
| HubSpot Ireland Limited (Ireland), part of HubSpot, Inc. (USA) | Processor: our mailing list, only if you tick the box (section 7) | EU data centre |
Google is not our service provider. It is the sign-in and storage service you choose to connect, and it processes your data under your own agreement with it.
11. International transfers
Our database is in the EU, and our server functions run in an EU region. Our providers are US companies and may access data from outside the European Economic Area (EEA), for example for support or security. These transfers are covered as follows:
- Vercel Inc.: certified under the EU-U.S. Data Privacy Framework. Vercel’s data processing addendum also includes the EU Standard Contractual Clauses.
- HubSpot, Inc.: certified under the EU-U.S. Data Privacy Framework. HubSpot’s data processing agreement also includes the EU Standard Contractual Clauses.
You can ask us for a copy of the safeguards at privacy@asora.com.
12. How long we keep data
| Data | How long |
|---|---|
| Account, connection data and folder ID | While your account exists. Deleted when you delete your account |
| Sign-in sessions | Expire 30 days after your last use, and are deleted once expired (at the next sign-in to the Service by anyone) and when you delete your account |
| Sign-in state | 10 minutes |
| Private links and their browser sessions | A link is kept, switched off or not, until you delete the plan or your account. A browser session expires 30 days after its last use, and is deleted by our scheduled job once expired. A link not used for 90 days stops working, and its person can ask for a new one |
| Email settings, the log of changes by people and your time zone | Until you delete the plan or your account |
| Send log | A claim for an email that was not sent: one day. The record of a sent email: 90 days. Both are also deleted when you delete the plan or your account |
| Hash of an address that stopped a kind of reminder | Until you ask us to delete it, so that the reminder does not start again |
| Mailing list (name, email address, the tool you signed up in, your consent) | Until you unsubscribe or ask us to delete it |
| Hosting request logs | Up to 30 days, set by our hosting provider’s plan |
| Support emails | As long as needed to answer you, and no longer than 3 years |
Your files are not ours to keep or delete. They stay in your Google Drive until you delete them.
13. Deleting your account
You can delete your account in the app’s settings, or by emailing privacy@asora.com. When you delete your account, we delete:
- your account, sign-in sessions and Google tokens;
- the ID of your folder and of each plan;
- the private links of your plans, their browser sessions, your email settings, the log of changes and the send log.
You can delete a single plan in the same way: its private links stop working and its records are deleted, and its folder goes to your Google Drive trash.
Your files stay in your Google Drive. They remain yours.
Deleting your account does not remove Asora’s access to your Google account. To remove it entirely, use Google’s Third-party connections page (section 6.6). Deleting your account does not take you off our mailing list either: use the unsubscribe link in any email (section 7).
14. Disclosure in response to legal process
We may disclose personal data if the law requires it or in response to valid legal process, including:
- court orders or judicial proceedings;
- subpoenas or regulatory investigations;
- requests from law-enforcement authorities;
- legal claims, where disclosure is needed to establish, exercise or defend legal rights.
We check each request for validity and scope. Where the law allows, we tell the affected users before we disclose their data. We disclose only the minimum needed. Because we do not store the content of your work, we usually cannot provide it.
15. Your rights
Under the GDPR you have the right to:
- Access: get a copy of your personal data.
- Rectification: correct inaccurate data.
- Erasure: ask us to delete your data.
- Restriction: limit how we use your data in certain cases.
- Portability: receive your data in a structured, machine-readable format. Your work is already in your own files.
- Object: object to processing based on legitimate interests.
- Withdraw consent: where we rely on consent, at any time.
If you were added to a plan by someone else, these rights apply to you too. The person who made the plan decides what the plan says about you, so ask them first to correct or remove it. You can also write to us. You can stop reminders at any time with the link in every email (section 5.3).
16. How to exercise your rights
Email us at privacy@asora.com. We may ask you to confirm your identity. We answer verified requests within 30 days.
You can also complain to the Data Protection Commission in Ireland at dataprotection.ie, or to the data protection authority where you live or work.
17. Security
We protect your data with:
- encryption in transit (HTTPS) for all traffic;
- encryption at rest for Google access and refresh tokens, with the key kept apart from the database;
- permission checks on our servers for every read and every change;
- browser security headers that stop other websites from showing the Service in a frame;
- logs designed to hold only IDs and error codes.
No system is perfectly secure. If a personal data breach affects you, we act as the GDPR requires: we tell the supervisory authority and, where required, you.
18. Children
The Service is a business tool. It is not meant for anyone under 18, and we do not knowingly collect children’s data.
19. Changes to this policy
We may update this policy. We publish every update on this page with a new date. The effective date at the top shows the latest version.
20. Contact
- Email: privacy@asora.com
- Mail: Asora Technologies Limited, 20 Hatch Street Lower, Dublin 2, D02 XH02, Ireland