and sends the data to the user at client 16 step 210 optionally server 10 may using conventional techniques embed a digital watermark or any other type of known marking into the data before it is sent to client 16 the embedded marking may be sent to server 10 as part of ticket 20 the digital watermark may be personalized for the specific user server 10 may also encrypt the data before it is sent to client 16 with the decryption key having been previously sent to client 16 by server 12 as part of the redirect message or otherwise alternatively to step 140 server 12 may send the ticket to client 16 in addition to or instead of sending the ticket to server 10 where the ticket is sent to client 16 client 16 provides the ticket to server 10 which then verifies the ticket with ticket server 18 as described hereinabove where server 12 does not provide redirection information to client 16 server 12 may provide other information to client 16 such as keywords identifying server 10 that client 16 may then use to search for server 10 which has the required content using conventional techniques such as by using publicly available search engines verification step 180 may include determining the validity of the ticket in accordance with a policy table 8 which typically includes distribution parameters preferably specified by the content owner examples of such distribution parameters may include approved times for providing content approved sources of specific content types.