Alternative to TripIt = TripWaffle

[tripwaffle]

@tripwaffle, I will cancel my account with you. While it works for me brilliantly on a desktop, to use Tripwaffle I'll need to have multiple profiles on my device and that isn't happening.

This has been forced on me, emails I have currently been receiving from tripwaffle while on a trip have links that links fail as I am unable to go further as it will not work on an android web browser since I use a different account. This for me is a security issue as will not use trip waffle (or any other app) with the account I use to access the PlayStore.

Good news! There's now an option to sign in via 'magic link' to the email account of your choice:

Sign in to TripWaffle

Otherwise, feel free to shoot an email to tripwaffle AT fastmail DOT com and we'll be happy to assist with the deletion of your account.

 

[serfty]

Good news! There's now an option to sign in via 'magic link' to the email account of your choice:

Sign in to TripWaffle

...

Brilliant! Works fine ... happy camper ...

(Tested with an embedded link from a T-W email )

 

[tripwaffle]

Question for the community, please:

At present, we retain original booking emails for 7 days, then delete them.
The exception is when we detect a ticket QR code or similar; in that case, it's stored indefinitely as an attachment on the event.
We've had requests for *all* source emails and PDFs to be stored indefinitely as attachments on the event.

What would you prefer?

 

[kpc]

Question for the community, please:

At present, we retain original booking emails for 7 days, then delete them.
The exception is when we detect a ticket QR code or similar; in that case, it's stored indefinitely as an attachment on the event.
We've had requests for *all* source emails and PDFs to be stored indefinitely as attachments on the event.

What would you prefer?

I would prefer them to be deleted. After all I still have the original etickets etc

 

[V1213]

Question for the community, please:

At present, we retain original booking emails for 7 days, then delete them.
The exception is when we detect a ticket QR code or similar; in that case, it's stored indefinitely as an attachment on the event.
We've had requests for *all* source emails and PDFs to be stored indefinitely as attachments on the event.

What would you prefer?

I think having all source emails be attachments would be quite tiresome and clunky.

I find trip attachments useful for tickets, so there's an easy place to find them if/when needed. To my mind, other source emails (e.g. hotel bookings and the like) are superfluous as they're replaced by TW - all I need is my name and my booking reference, and they're in TW (in a much more copy-friendly way).